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
20191014222703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*142227z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191014224703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*142247z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191014230703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*142307z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191014232703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*142327z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191014234703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*142347z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015000703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150007z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015002703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150027z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015004703PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150047z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015010713PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150107z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015012651PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150126z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015014651PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150146z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015020701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150206z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015022701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150226z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015024701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150246z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015030701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150306z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015032701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150326z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015034701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150346z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz
20191015040701PA3BSG-S>APDG01,TCPIP*,qAC,PA3BSG-GS:;PA3BSG - RON*150406z5129.40ND00507.20EaRNG0001 440 Data 432.47500MHz