APRS Packet Errors for PA3BSG-S (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20190922080710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220807z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922082709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220827z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922084709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220847z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922090710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220907z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922092709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220927z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922094710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*220947z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922100709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922102710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221027z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922104710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221047z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922110710PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221107z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922112720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221127z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922114720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221147z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922120720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221207z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922122720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221227z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922124720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221247z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922130720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221307z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922132720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221327z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190922134720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*221347z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz