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
20180419234232EW66880>APRS,TCPXX*,qAX,CWOP-7:@192342z0000.00N/00000.00E_306/005g014t058P000h38b10176ws31
20180420004233EW66880>APRS,TCPXX*,qAX,CWOP-5:@200042z0000.00N/00000.00E_311/001g007t055P000h43b10186ws31
20180420014232EW66880>APRS,TCPXX*,qAX,CWOP-2:@200142z0000.00N/00000.00E_330/001g006t053P000h45b10199ws31
20180420024233EW66880>APRS,TCPXX*,qAX,CWOP-4:@200242z0000.00N/00000.00E_032/003g011t051P000h47b10210ws31
20180420034233EW66880>APRS,TCPXX*,qAX,CWOP-6:@200342z0000.00N/00000.00E_044/003g008t048P000h52b10216ws31
20180420044233EW66880>APRS,TCPXX*,qAX,CWOP-6:@200442z0000.00N/00000.00E_027/003g005t046P000h55b10227ws31