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
20190720072709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200727z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720074709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200747z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720080709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200807z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720082709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200827z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720084709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200847z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720090709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200907z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720092709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200927z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720094709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*200947z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720100709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720102709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201027z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720104709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201047z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720110709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201107z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720112709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201127z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720114709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201147z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720120709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201207z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720122709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201227z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720124709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201247z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190720130709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*201307z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz