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
20171123203301EW66880>APRS,TCPXX*,qAX,CWOP-1:@232033z0000.00N/00000.00E_117/000g004t054P000h46b10163ws31
20171123213300EW66880>APRS,TCPXX*,qAX,CWOP-3:@232133z0000.00N/00000.00E_353/000g000t054P000h49b10160ws31
20171123223301EW66880>APRS,TCPXX*,qAX,CWOP-7:@232233z0000.00N/00000.00E_353/000g000t046P000h70b10158ws31
20171123233301EW66880>APRS,TCPXX*,qAX,CWOP-4:@232333z0000.00N/00000.00E_353/000g000t040P000h80b10163ws31
20171124003300EW66880>APRS,TCPXX*,qAX,CWOP-6:@240033z0000.00N/00000.00E_352/000g000t038P000h85b10166ws31
20171124013300EW66880>APRS,TCPXX*,qAX,CWOP-4:@240133z0000.00N/00000.00E_346/000g000t035P000h89b10167ws31