APRS Packet Errors for 146.850MO (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
20260208152311W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208154141W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208155952W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208161732W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208163448W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208165344W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208171104W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208172920W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208174738W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208180706W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208182531W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208184407W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208190237W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208192023W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208193758W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208195624W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208201350W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208203050W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208204818W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260208210529W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC