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
20190918142753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181427z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918144753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181447z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918150753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181507z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918152753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181527z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918154753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181547z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918160753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181607z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918162753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181627z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918164753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181647z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918170753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181707z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918172753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181727z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918174753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181747z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918180753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181807z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918182753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181827z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918184753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181847z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918190753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181907z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918192753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181927z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918194753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*181947z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20190918200753PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*182007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz