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
20180425124249EW66880>APRS,TCPXX*,qAX,CWOP-2:@251242z0000.00N/00000.00E_294/000g002t059P000h97b10081ws31
20180425134249EW66880>APRS,TCPXX*,qAX,CWOP-4:@251342z0000.00N/00000.00E_301/003g004t062P000h93b10078ws31
20180425144249EW66880>APRS,TCPXX*,qAX,CWOP-3:@251442z0000.00N/00000.00E_305/002g008t065P000h83b10080ws31
20180425154250EW66880>APRS,TCPXX*,qAX,CWOP-3:@251542z0000.00N/00000.00E_255/001g010t069P000h70b10081ws31
20180425164249EW66880>APRS,TCPXX*,qAX,CWOP-4:@251642z0000.00N/00000.00E_297/008g010t071P000h63b10077ws31
20180425174250EW66880>APRS,TCPXX*,qAX,CWOP-6:@251742z0000.00N/00000.00E_275/000g010t073P000h61b10077ws31