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
20180423234244EW66880>APRS,TCPXX*,qAX,CWOP-3:@232342z0000.00N/00000.00E_086/001g010t058P092h95b10181ws31
20180424004245EW66880>APRS,TCPXX*,qAX,CWOP-5:@240042z0000.00N/00000.00E_113/002g005t057P110h95b10178ws31
20180424014245EW66880>APRS,TCPXX*,qAX,CWOP-1:@240142z0000.00N/00000.00E_304/000g006t057P121h96b10177ws31
20180424024245EW66880>APRS,TCPXX*,qAX,CWOP-2:@240242z0000.00N/00000.00E_031/001g007t057P128h96b10174ws31
20180424034245EW66880>APRS,TCPXX*,qAX,CWOP-6:@240342z0000.00N/00000.00E_146/000g007t058P134h96b10170ws31
20180424044245EW66880>APRS,TCPXX*,qAX,CWOP-3:@240442z0000.00N/00000.00E_034/004g009t058P002h96b10158ws31