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
20180921214710EW66880>APRS,TCPXX*,qAX,CWOP-6:@212147z0000.00N/00000.00E_297/000g000t078P016h94b10127ws31
20180921224710EW66880>APRS,TCPXX*,qAX,CWOP-3:@212247z0000.00N/00000.00E_299/000g000t077P030h95b10127ws31
20180921234710EW66880>APRS,TCPXX*,qAX,CWOP-5:@212347z0000.00N/00000.00E_299/000g000t077P033h96b10125ws31
20180922004710EW66880>APRS,TCPXX*,qAX,CWOP-2:@220047z0000.00N/00000.00E_299/000g000t077P035h97b10130ws31
20180922014710EW66880>APRS,TCPXX*,qAX,CWOP-7:@220147z0000.00N/00000.00E_299/000g000t077P035h97b10133ws31
20180922024710EW66880>APRS,TCPXX*,qAX,CWOP-3:@220247z0000.00N/00000.00E_304/000g000t078P035h97b10137ws31