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
20181018021036EW66880>APRS,TCPXX*,qAX,CWOP-2:@180210z0000.00N/00000.00E_351/001g004t057P002h96b10239ws31
20181018031036EW66880>APRS,TCPXX*,qAX,CWOP-5:@180310z0000.00N/00000.00E_343/001g003t056P002h95b10245ws31
20181018041036EW66880>APRS,TCPXX*,qAX,CWOP-7:@180410z0000.00N/00000.00E_289/001g002t056P002h94b10244ws31
20181018051037EW66880>APRS,TCPXX*,qAX,CWOP-3:@180510z0000.00N/00000.00E_338/000g002t057P000h91b10244ws31
20181018061036EW66880>APRS,TCPXX*,qAX,CWOP-1:@180610z0000.00N/00000.00E_306/000g002t057P000h91b10241ws31
20181018071037EW66880>APRS,TCPXX*,qAX,CWOP-2:@180710z0000.00N/00000.00E_336/000g002t058P000h90b10238ws31