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
20191117085452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170854z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117091452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170914z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117093452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170934z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117095452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*170954z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117101452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171014z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117103452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171034z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117105452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171054z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117111452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171114z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117113452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171134z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117115452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171154z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117121452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171214z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117123452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171234z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117125452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171254z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117131452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171314z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117133452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171334z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117135452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171354z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117141452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171414z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191117143452PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171434z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz