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
20191023082658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*230826z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023084658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*230846z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023090659PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*230906z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023092658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*230926z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023094658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*230946z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023100658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231006z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023102658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231026z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023104658PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231046z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023110708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231106z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023112708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231126z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023114708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231146z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023120708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231206z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023122709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231226z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023124708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231247z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023130708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231307z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023132708PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231327z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023134709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231347z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191023140709PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*231407z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz