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
20170625134452EW66880>APRS,TCPXX*,qAX,CWOP-7:@251344z0000.00N/00000.00E_339/002g005t078P000h73b10183ws31
20170625144438EW66880>APRS,TCPXX*,qAX,CWOP-3:@251444z0000.00N/00000.00E_346/002g005t080P000h67b10187ws31
20170625154453EW66880>APRS,TCPXX*,qAX,CWOP-6:@251544z0000.00N/00000.00E_351/002g009t082P000h63b10191ws31
20170625164453EW66880>APRS,TCPXX*,qAX,CWOP-1:@251644z0000.00N/00000.00E_038/003g009t084P000h62b10192ws31
20170625174437EW66880>APRS,TCPXX*,qAX,CWOP-3:@251744z0000.00N/00000.00E_031/005g008t083P000h58b10188ws31
20170625184453EW66880>APRS,TCPXX*,qAX,CWOP-3:@251844z0000.00N/00000.00E_320/000g003t084P000h56b10182ws31