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
20190717132425EW66880>APRS,TCPXX*,qAX,CWOP-2:@171324z0000.00N/00000.00E_314/001g003t082P000h93b10171ws31
20190717142425EW66880>APRS,TCPXX*,qAX,CWOP-5:@171424z0000.00N/00000.00E_265/001g004t084P000h86b10174ws31
20190717152425EW66880>APRS,TCPXX*,qAX,CWOP-2:@171524z0000.00N/00000.00E_315/001g004t088P000h75b10174ws31
20190717162425EW66880>APRS,TCPXX*,qAX,CWOP-5:@171624z0000.00N/00000.00E_327/000g003t091P000h70b10175ws31
20190717172425EW66880>APRS,TCPXX*,qAX,CWOP-2:@171724z0000.00N/00000.00E_304/002g008t091P000h68b10172ws31
20190717182425EW66880>APRS,TCPXX*,qAX,CWOP-2:@171824z0000.00N/00000.00E_027/000g005t094P000h58b10167ws31