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
20260209103626	NW0K-5>APMI06,COLBY,KD0ARW-7,WIDE2*,qAR,HOISNG:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209110624	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.0V
20260209113626	NW0K-5>APMI06,COLBY,N7JYS-2*,WIDE2,qAR,AA0HJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209120623	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.0V
20260209123623	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209130626	NW0K-5>APMI06,COLBY,KD0ARW-7,WIDE2*,qAR,HOISNG:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209133626	NW0K-5>APMI06,COLBY,PBURG,WIDE2*,qAR,AA0HJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209140626	NW0K-5>APMI06,COLBY,PBURG,WIDE2*,qAR,AA0HJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209143623	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.0V
20260209150623	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209153625	NW0K-5>APMI06,COLBY,KC0AUH-2,WIDE2*,qAR,KD0EZS-10:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V
20260209160623	NW0K-5>APMI06,TCPIP*,qAS,K0FJ:!3921.90NI10103.31W& NW0K IGate Colby U=14.1V