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
20190824205624EW66880>APRS,TCPXX*,qAX,CWOP-2:@242056z0000.00N/00000.00E_077/000g003t094P000h49b10097ws31
20190824215624EW66880>APRS,TCPXX*,qAX,CWOP-3:@242156z0000.00N/00000.00E_004/000g002t093P000h49b10090ws31
20190824225624EW66880>APRS,TCPXX*,qAX,CWOP-1:@242256z0000.00N/00000.00E_138/001g002t094P000h46b10090ws31
20190824235625EW66880>APRS,TCPXX*,qAX,CWOP-3:@242356z0000.00N/00000.00E_022/000g000t092P000h49b10092ws31
20190825005625EW66880>APRS,TCPXX*,qAX,CWOP-4:@250056z0000.00N/00000.00E_015/000g000t087P000h59b10097ws31
20190825015625EW66880>APRS,TCPXX*,qAX,CWOP-5:@250156z0000.00N/00000.00E_015/000g000t084P000h66b10105ws31