APRS Packet Errors for NW0K-5 (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
20260208200631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208203631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208210631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.0V
20260208213631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208220631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208223626	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208230631	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260208233626	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209000630	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209003625	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209010630	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209013630	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V