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
20170626234457EW66880>APRS,TCPXX*,qAX,CWOP-6:@262344z0000.00N/00000.00E_289/000g000t080P000h55b10164ws31
20170627004441EW66880>APRS,TCPXX*,qAX,CWOP-6:@270044z0000.00N/00000.00E_289/000g000t073P000h72b10167ws31
20170627014457EW66880>APRS,TCPXX*,qAX,CWOP-5:@270144z0000.00N/00000.00E_289/000g000t070P000h81b10170ws31
20170627024457EW66880>APRS,TCPXX*,qAX,CWOP-1:@270244z0000.00N/00000.00E_289/000g000t068P000h86b10172ws31
20170627034458EW66880>APRS,TCPXX*,qAX,CWOP-3:@270344z0000.00N/00000.00E_289/000g000t067P000h85b10171ws31
20170627044457EW66880>APRS,TCPXX*,qAX,CWOP-7:@270444z0000.00N/00000.00E_289/000g000t065P000h91b10170ws31