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
20181217043912EW66880>APRS,TCPXX*,qAX,CWOP-2:@170439z0000.00N/00000.00E_330/000g000t049P000h95b10248ws31
20181217053912EW66880>APRS,TCPXX*,qAX,CWOP-2:@170539z0000.00N/00000.00E_330/000g000t049P000h95b10242ws31
20181217063913EW66880>APRS,TCPXX*,qAX,CWOP-2:@170639z0000.00N/00000.00E_330/000g000t049P000h95b10241ws31
20181217073913EW66880>APRS,TCPXX*,qAX,CWOP-6:@170739z0000.00N/00000.00E_330/000g001t049P000h95b10233ws31
20181217083913EW66880>APRS,TCPXX*,qAX,CWOP-3:@170839z0000.00N/00000.00E_330/000g000t048P000h95b10230ws31
20181217093913EW66880>APRS,TCPXX*,qAX,CWOP-1:@170939z0000.00N/00000.00E_330/000g000t048P000h96b10234ws31