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
20180124013840EW66880>APRS,TCPXX*,qAX,CWOP-3:@240138z0000.00N/00000.00E_263/000g002t052P127h50b10135ws31
20180124023840EW66880>APRS,TCPXX*,qAX,CWOP-6:@240238z0000.00N/00000.00E_278/000g001t049P127h57b10143ws31
20180124033840EW66880>APRS,TCPXX*,qAX,CWOP-1:@240338z0000.00N/00000.00E_289/000g003t048P127h51b10152ws31
20180124043840EW66880>APRS,TCPXX*,qAX,CWOP-6:@240438z0000.00N/00000.00E_304/000g000t042P127h64b10155ws31
20180124053840EW66880>APRS,TCPXX*,qAX,CWOP-4:@240538z0000.00N/00000.00E_303/000g000t040P000h71b10157ws31
20180124063840EW66880>APRS,TCPXX*,qAX,CWOP-3:@240638z0000.00N/00000.00E_303/000g000t039P000h72b10163ws31