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
20190717172730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171727z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717174730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171747z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717180730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171807z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717182730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171827z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717184730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171847z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717190730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171907z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717192730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171927z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717194730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*171947z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717200730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717202730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172027z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717204730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172047z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717210730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172107z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717212730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172127z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717214730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172147z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717220730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172207z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717222730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172227z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717224730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172247z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190717230730PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*172307z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz