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
20180426094252EW66880>APRS,TCPXX*,qAX,CWOP-1:@260942z0000.00N/00000.00E_290/000g000t057P000h94b10098ws31
20180426104252EW66880>APRS,TCPXX*,qAX,CWOP-4:@261042z0000.00N/00000.00E_290/000g000t057P000h93b10100ws31
20180426114252EW66880>APRS,TCPXX*,qAX,CWOP-4:@261142z0000.00N/00000.00E_343/000g001t058P000h86b10106ws31
20180426124252EW66880>APRS,TCPXX*,qAX,CWOP-1:@261242z0000.00N/00000.00E_348/001g006t062P000h78b10108ws31
20180426134252EW66880>APRS,TCPXX*,qAX,CWOP-6:@261342z0000.00N/00000.00E_102/003g006t065P000h66b10111ws31
20180426144252EW66880>APRS,TCPXX*,qAX,CWOP-1:@261442z0000.00N/00000.00E_351/001g006t067P000h64b10113ws31