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
20190117005125EW66880>APRS,TCPXX*,qAX,CWOP-5:@170051z0000.00N/00000.00E_252/000g004t057P004h96b10210ws31
20190117015125EW66880>APRS,TCPXX*,qAX,CWOP-3:@170151z0000.00N/00000.00E_275/000g003t057P004h96b10211ws31
20190117025125EW66880>APRS,TCPXX*,qAX,CWOP-6:@170251z0000.00N/00000.00E_243/001g001t057P005h96b10213ws31
20190117035124EW66880>APRS,TCPXX*,qAX,CWOP-3:@170351z0000.00N/00000.00E_164/000g003t058P006h97b10211ws31
20190117045126EW66880>APRS,TCPXX*,qAX,CWOP-3:@170451z0000.00N/00000.00E_210/000g002t058P007h97b10211ws31
20190117055126EW66880>APRS,TCPXX*,qAX,CWOP-4:@170551z0000.00N/00000.00E_152/000g001t058P008h97b10207ws31