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
20180723073851EW66880>APRS,TCPXX*,qAX,CWOP-7:@230738z0000.00N/00000.00E_279/000g001t079P000h90b10103ws31
20180723083851EW66880>APRS,TCPXX*,qAX,CWOP-2:@230838z0000.00N/00000.00E_353/000g003t078P000h93b10100ws31
20180723093851EW66880>APRS,TCPXX*,qAX,CWOP-5:@230938z0000.00N/00000.00E_289/000g001t078P000h94b10106ws31
20180723103851EW66880>APRS,TCPXX*,qAX,CWOP-4:@231038z0000.00N/00000.00E_278/000g003t078P000h95b10109ws31
20180723113852EW66880>APRS,TCPXX*,qAX,CWOP-5:@231138z0000.00N/00000.00E_319/000g002t077P000h95b10114ws31
20180723123851EW66880>APRS,TCPXX*,qAX,CWOP-1:@231238z0000.00N/00000.00E_303/000g004t078P000h95b10118ws31