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
20180225214020EW66880>APRS,TCPXX*,qAX,CWOP-1:@252140z0000.00N/00000.00E_246/000g002t067P000h73b10177ws31
20180225224020EW66880>APRS,TCPXX*,qAX,CWOP-6:@252240z0000.00N/00000.00E_227/004g005t067P000h70b10182ws31
20180225234020EW66880>APRS,TCPXX*,qAX,CWOP-7:@252340z0000.00N/00000.00E_237/000g003t066P000h75b10179ws31
20180226004020EW66880>APRS,TCPXX*,qAX,CWOP-4:@260040z0000.00N/00000.00E_235/001g005t065P000h81b10181ws31
20180226014020EW66880>APRS,TCPXX*,qAX,CWOP-6:@260140z0000.00N/00000.00E_237/001g004t065P000h82b10177ws31
20180226024020EW66880>APRS,TCPXX*,qAX,CWOP-6:@260240z0000.00N/00000.00E_259/000g001t065P000h79b10183ws31