APRS Packet Errors for 462.70MHC (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
20260209143723	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209150724	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209153726	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209160728	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209163730	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209170731	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209173733	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209180735	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209183736	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209190738	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209193740	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260209200741	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0