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
20260209162511W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209164352W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209170117W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209171905W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209173723W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209175538W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209181329W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209183030W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209184750W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209190447W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209192256W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209194038W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209195857W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209201703W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209203418W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209205218W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209210938W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209212755W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209214616W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC
20260209220426W0SRC-1>APRX29,TCPIP*,qAC,FOURTH:;146.850MO*111111z3840.38N/09023.26WrC141.3 R60m net 7:30PM Tu SLSRC