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
20180721073845EW66880>APRS,TCPXX*,qAX,CWOP-2:@210738z0000.00N/00000.00E_286/000g001t078P000h94b10133ws31
20180721083845EW66880>APRS,TCPXX*,qAX,CWOP-4:@210838z0000.00N/00000.00E_294/000g001t079P000h94b10131ws31
20180721093845EW66880>APRS,TCPXX*,qAX,CWOP-1:@210938z0000.00N/00000.00E_274/000g004t080P000h93b10135ws31
20180721103845EW66880>APRS,TCPXX*,qAX,CWOP-1:@211038z0000.00N/00000.00E_264/001g003t079P000h93b10142ws31
20180721113846EW66880>APRS,TCPXX*,qAX,CWOP-6:@211138z0000.00N/00000.00E_318/000g004t079P000h92b10149ws31
20180721123845EW66880>APRS,TCPXX*,qAX,CWOP-5:@211238z0000.00N/00000.00E_322/000g003t079P000h91b10152ws31