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
20190717050719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170507z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717052719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170527z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717054719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170547z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717060719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170607z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717062719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170627z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717064719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170647z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717070719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170707z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717072719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170727z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717074719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170747z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717080719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170807z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717082719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170827z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717084719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170847z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717090720PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170907z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717092719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170927z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717094719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170947z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717100719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717102719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171027z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717104719PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171047z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz