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
20190121105138EW66880>APRS,TCPXX*,qAX,CWOP-1:@211051z0000.00N/00000.00E_019/000g000t034P000h95b10234ws31
20190121115139EW66880>APRS,TCPXX*,qAX,CWOP-6:@211151z0000.00N/00000.00E_019/000g000t034P000h95b10231ws31
20190121125139EW66880>APRS,TCPXX*,qAX,CWOP-4:@211251z0000.00N/00000.00E_019/000g000t034P000h95b10237ws31
20190121135139EW66880>APRS,TCPXX*,qAX,CWOP-4:@211351z0000.00N/00000.00E_015/000g000t035P000h96b10240ws31
20190121145139EW66880>APRS,TCPXX*,qAX,CWOP-6:@211451z0000.00N/00000.00E_027/000g002t042P000h88b10235ws31
20190121155138EW66880>APRS,TCPXX*,qAX,CWOP-1:@211551z0000.00N/00000.00E_028/000g002t047P000h82b10237ws31