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
20190219081833EW66880>APRS,TCPXX*,qAX,CWOP-3:@190818z0000.00N/00000.00E_339/000g006t048P000h54b10197ws31
20190219091833EW66880>APRS,TCPXX*,qAX,CWOP-6:@190918z0000.00N/00000.00E_325/004g005t048P000h59b10191ws31
20190219101833EW66880>APRS,TCPXX*,qAX,CWOP-4:@191018z0000.00N/00000.00E_334/000g004t048P000h62b10179ws31
20190219111833EW66880>APRS,TCPXX*,qAX,CWOP-3:@191118z0000.00N/00000.00E_343/002g008t048P000h62b10176ws31
20190219121833EW66880>APRS,TCPXX*,qAX,CWOP-7:@191218z0000.00N/00000.00E_050/004g006t048P000h67b10167ws31
20190219131834EW66880>APRS,TCPXX*,qAX,CWOP-3:@191318z0000.00N/00000.00E_339/000g005t047P000h73b10168ws31