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
20181216064011EW66880>APRS,TCPXX*,qAX,CWOP-4:@160640z0000.00N/00000.00E_358/000g000t042P000h87b10231ws31
20181216074011EW66880>APRS,TCPXX*,qAX,CWOP-3:@160740z0000.00N/00000.00E_358/000g000t041P000h87b10231ws31
20181216084011EW66880>APRS,TCPXX*,qAX,CWOP-6:@160840z0000.00N/00000.00E_358/000g000t040P000h89b10234ws31
20181216094012EW66880>APRS,TCPXX*,qAX,CWOP-3:@160940z0000.00N/00000.00E_358/000g000t040P000h89b10233ws31
20181216104012EW66880>APRS,TCPXX*,qAX,CWOP-5:@161040z0000.00N/00000.00E_358/000g000t038P000h92b10235ws31
20181216114012EW66880>APRS,TCPXX*,qAX,CWOP-4:@161140z0000.00N/00000.00E_358/000g000t038P000h92b10239ws31