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
20170720192742EW66880>APRS,TCPXX*,qAX,CWOP-7:@201927z0000.00N/00000.00E_024/003g004t090P001h68b10167ws31
20170720202742EW66880>APRS,TCPXX*,qAX,CWOP-1:@202027z0000.00N/00000.00E_301/001g003t096P001h48b10156ws31
20170720212742EW66880>APRS,TCPXX*,qAX,CWOP-7:@202127z0000.00N/00000.00E_297/000g004t095P001h54b10150ws31
20170720222742EW66880>APRS,TCPXX*,qAX,CWOP-7:@202227z0000.00N/00000.00E_291/000g001t096P001h53b10148ws31
20170720232743EW66880>APRS,TCPXX*,qAX,CWOP-3:@202327z0000.00N/00000.00E_320/000g001t090P001h63b10150ws31
20170721002743EW66880>APRS,TCPXX*,qAX,CWOP-3:@210027z0000.00N/00000.00E_308/000g000t083P001h79b10153ws31