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
20181015231030EW66880>APRS,TCPXX*,qAX,CWOP-3:@152310z0000.00N/00000.00E_272/000g006t052P063h96b10184ws31
20181016001031EW66880>APRS,TCPXX*,qAX,CWOP-2:@160010z0000.00N/00000.00E_358/002g008t051P065h96b10181ws31
20181016011029EW66880>APRS,TCPXX*,qAX,CWOP-4:@160110z0000.00N/00000.00E_317/000g004t052P065h96b10183ws31
20181016021030EW66880>APRS,TCPXX*,qAX,CWOP-5:@160210z0000.00N/00000.00E_356/002g004t053P073h97b10184ws31
20181016031030EW66880>APRS,TCPXX*,qAX,CWOP-1:@160310z0000.00N/00000.00E_317/000g003t053P078h97b10185ws31
20181016041030EW66880>APRS,TCPXX*,qAX,CWOP-3:@160410z0000.00N/00000.00E_349/000g003t053P078h97b10184ws31