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
20181021181048EW66880>APRS,TCPXX*,qAX,CWOP-6:@211810z0000.00N/00000.00E_347/005g005t072P000h47b10235ws31
20181021191048EW66880>APRS,TCPXX*,qAX,CWOP-7:@211910z0000.00N/00000.00E_177/003g005t072P000h47b10225ws31
20181021201048EW66880>APRS,TCPXX*,qAX,CWOP-3:@212010z0000.00N/00000.00E_005/006g006t072P000h45b10216ws31
20181021211048EW66880>APRS,TCPXX*,qAX,CWOP-3:@212110z0000.00N/00000.00E_350/002g004t071P000h48b10214ws31
20181021221048EW66880>APRS,TCPXX*,qAX,CWOP-2:@212210z0000.00N/00000.00E_004/003g004t070P000h48b10212ws31
20181021231048EW66880>APRS,TCPXX*,qAX,CWOP-1:@212310z0000.00N/00000.00E_313/001g002t067P000h56b10213ws31