APRS Packet Errors for N0CAK (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
20260615063746N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@063745h0000.00N/00000.00Ej
20260615070747N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@070746h0000.00N/00000.00Ej
20260615073747N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@073747h0000.00N/00000.00Ej
20260615080747N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@080747h0000.00N/00000.00Ej
20260615083748N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@083747h0000.00N/00000.00Ej
20260615090749N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@090748h0000.00N/00000.00Ej
20260615093749N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@093749h0000.00N/00000.00Ej
20260615100750N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@100750h0000.00N/00000.00Ej
20260615103751N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@103751h0000.00N/00000.00Ej
20260615110752N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@110751h0000.00N/00000.00Ej
20260615113752N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@113752h0000.00N/00000.00Ej
20260615120753N0CAK>APWW11,TCPIP*,qAC,T2CHILE:@120752h0000.00N/00000.00Ej