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
20170626034455EW66880>APRS,TCPXX*,qAX,CWOP-5:@260344z0000.00N/00000.00E_351/000g000t068P000h80b10192ws31
20170626044455EW66880>APRS,TCPXX*,qAX,CWOP-5:@260444z0000.00N/00000.00E_351/000g000t064P000h90b10192ws31
20170626054454EW66880>APRS,TCPXX*,qAX,CWOP-6:@260544z0000.00N/00000.00E_349/000g002t068P000h82b10190ws31
20170626064439EW66880>APRS,TCPXX*,qAX,CWOP-4:@260644z0000.00N/00000.00E_350/000g000t064P000h90b10189ws31
20170626074455EW66880>APRS,TCPXX*,qAX,CWOP-1:@260744z0000.00N/00000.00E_350/000g000t062P000h94b10188ws31
20170626084455EW66880>APRS,TCPXX*,qAX,CWOP-1:@260844z0000.00N/00000.00E_350/000g000t062P000h96b10191ws31