APRS Packet Errors for EW66880 (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
20180223184016EW66880>APRS,TCPXX*,qAX,CWOP-5:@231840z0000.00N/00000.00E_124/006g006t076P000h59b10273ws31
20180223194017EW66880>APRS,TCPXX*,qAX,CWOP-3:@231940z0000.00N/00000.00E_243/002g007t076P000h59b10265ws31
20180223204016EW66880>APRS,TCPXX*,qAX,CWOP-6:@232040z0000.00N/00000.00E_205/005g008t078P000h51b10257ws31
20180223214017EW66880>APRS,TCPXX*,qAX,CWOP-6:@232140z0000.00N/00000.00E_134/001g007t076P000h54b10256ws31
20180223224016EW66880>APRS,TCPXX*,qAX,CWOP-7:@232240z0000.00N/00000.00E_235/000g005t076P000h53b10254ws31
20180223234017EW66880>APRS,TCPXX*,qAX,CWOP-3:@232340z0000.00N/00000.00E_268/000g000t070P000h67b10253ws31