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
20171124123320EW66880>APRS,TCPXX*,qAX,CWOP-4:@241233z0000.00N/00000.00E_346/000g000t027P000h96b10176ws31
20171124133322EW66880>APRS,TCPXX*,qAX,CWOP-6:@241333z0000.00N/00000.00E_346/000g000t036P000h95b10172ws31
20171124143333EW66880>APRS,TCPXX*,qAX,CWOP-7:@241433z0000.00N/00000.00E_350/000g001t044P000h78b10168ws31
20171124153335EW66880>APRS,TCPXX*,qAX,CWOP-5:@241533z0000.00N/00000.00E_358/000g002t050P000h58b10168ws31
20171124163334EW66880>APRS,TCPXX*,qAX,CWOP-4:@241633z0000.00N/00000.00E_031/002g005t053P000h50b10163ws31
20171124173336EW66880>APRS,TCPXX*,qAX,CWOP-5:@241733z0000.00N/00000.00E_315/000g004t056P000h44b10152ws31