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
20180620001600EW66880>APRS,TCPXX*,qAX,CWOP-1:@200016z0000.00N/00000.00E_304/000g000t090P000h57b10112ws31
20180620011600EW66880>APRS,TCPXX*,qAX,CWOP-6:@200116z0000.00N/00000.00E_310/000g004t086P000h65b10118ws31
20180620021600EW66880>APRS,TCPXX*,qAX,CWOP-6:@200216z0000.00N/00000.00E_288/000g001t084P000h70b10121ws31
20180620031600EW66880>APRS,TCPXX*,qAX,CWOP-6:@200316z0000.00N/00000.00E_288/000g000t080P000h79b10121ws31
20180620041600EW66880>APRS,TCPXX*,qAX,CWOP-6:@200416z0000.00N/00000.00E_288/000g000t078P000h83b10119ws31
20180620051600EW66880>APRS,TCPXX*,qAX,CWOP-6:@200516z0000.00N/00000.00E_288/000g000t077P000h85b10120ws31