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
20190420221720EW66880>APRS,TCPXX*,qAX,CWOP-3:@202217z0000.00N/00000.00E_327/000g006t079P000h35b10155ws31
20190420231720EW66880>APRS,TCPXX*,qAX,CWOP-4:@202317z0000.00N/00000.00E_346/001g004t078P000h34b10151ws31
20190421001720EW66880>APRS,TCPXX*,qAX,CWOP-1:@210017z0000.00N/00000.00E_349/000g001t072P000h44b10147ws31
20190421011720EW66880>APRS,TCPXX*,qAX,CWOP-7:@210117z0000.00N/00000.00E_349/000g000t065P000h61b10147ws31
20190421021720EW66880>APRS,TCPXX*,qAX,CWOP-6:@210217z0000.00N/00000.00E_349/000g000t060P000h73b10152ws31
20190421031720EW66880>APRS,TCPXX*,qAX,CWOP-3:@210317z0000.00N/00000.00E_349/000g000t059P000h80b10154ws31