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
20260208143601	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208150603	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208153605	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208160607	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208163608	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208170610	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208173612	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208180613	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208183615	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208190617	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208193618	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0
20260208200620	N2TEK-1>APMI04,TCPIP,qAS,N2TEK:;462.70MHC111111z3636.80N/07955.10Wr MHC 700 T-123.0 +5.0