APRS Packet Errors for EW6329 (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
20251013101005EW6329>APRS,TCPXX*,qAX,CWOP-4:@131010z0000.00N/00000.00E_309/000g000t056P000h90b10126l1041ws31
20251013121005EW6329>APRS,TCPXX*,qAX,CWOP-5:@131210z0000.00N/00000.00E_309/000g000t055P000h91b10140l1041ws31
20251013122005EW6329>APRS,TCPXX*,qAX,CWOP-5:@131220z0000.00N/00000.00E_309/000g000t055P000h91b10140l1041ws31
20251013123005EW6329>APRS,TCPXX*,qAX,CWOP-7:@131230z0000.00N/00000.00E_309/000g000t055P000h91b10141l1041ws31
20251013124006EW6329>APRS,TCPXX*,qAX,CWOP-3:@131240z0000.00N/00000.00E_309/000g000t055P000h92b10141l1041ws31
20251013125005EW6329>APRS,TCPXX*,qAX,CWOP-5:@131250z0000.00N/00000.00E_309/000g000t055P000h92b10141l1041ws31
20251013131005EW6329>APRS,TCPXX*,qAX,CWOP-7:@131310z0000.00N/00000.00E_309/000g000t055P000h92b10144l1041ws31
20251013151004EW6329>APRS,TCPXX*,qAX,CWOP-4:@131510z0000.00N/00000.00E_309/000g000t062P000h96b10157l1041ws31
20251013153005EW6329>APRS,TCPXX*,qAX,CWOP-6:@131530z0000.00N/00000.00E_309/000g000t063P000h96b10157l1041ws31
20251013154005EW6329>APRS,TCPXX*,qAX,CWOP-3:@131540z0000.00N/00000.00E_309/000g000t064P000h96b10156l1041ws31