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
20181212153959EW66880>APRS,TCPXX*,qAX,CWOP-1:@121539z0000.00N/00000.00E_057/000g002t059P000h86b10184ws31
20181212163959EW66880>APRS,TCPXX*,qAX,CWOP-1:@121639z0000.00N/00000.00E_344/000g001t062P000h83b10174ws31
20181212174000EW66880>APRS,TCPXX*,qAX,CWOP-6:@121740z0000.00N/00000.00E_287/000g001t065P000h80b10166ws31
20181212184000EW66880>APRS,TCPXX*,qAX,CWOP-1:@121840z0000.00N/00000.00E_074/000g004t066P000h77b10157ws31
20181212194000EW66880>APRS,TCPXX*,qAX,CWOP-5:@121940z0000.00N/00000.00E_287/000g004t068P000h74b10141ws31
20181212204000EW66880>APRS,TCPXX*,qAX,CWOP-1:@122040z0000.00N/00000.00E_204/000g005t067P000h78b10137ws31