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
20190420131718EW66880>APRS,TCPXX*,qAX,CWOP-7:@201317z0000.00N/00000.00E_088/000g000t048P000h97b10190ws31
20190420141718EW66880>APRS,TCPXX*,qAX,CWOP-6:@201417z0000.00N/00000.00E_089/001g001t062P000h73b10195ws31
20190420151719EW66880>APRS,TCPXX*,qAX,CWOP-7:@201517z0000.00N/00000.00E_041/001g003t069P000h42b10197ws31
20190420161719EW66880>APRS,TCPXX*,qAX,CWOP-2:@201617z0000.00N/00000.00E_074/000g002t072P000h36b10199ws31
20190420171719EW66880>APRS,TCPXX*,qAX,CWOP-2:@201717z0000.00N/00000.00E_305/000g005t073P000h35b10193ws31
20190420181719EW66880>APRS,TCPXX*,qAX,CWOP-3:@201817z0000.00N/00000.00E_154/000g002t076P000h33b10187ws31