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
20180218163957EW66880>APRS,TCPXX*,qAX,CWOP-2:@181639z0000.00N/00000.00E_034/005g011t056P000h59b10267ws31
20180218173957EW66880>APRS,TCPXX*,qAX,CWOP-2:@181739z0000.00N/00000.00E_090/001g006t059P000h51b10264ws31
20180218183957EW66880>APRS,TCPXX*,qAX,CWOP-6:@181839z0000.00N/00000.00E_349/003g008t061P000h45b10254ws31
20180218193958EW66880>APRS,TCPXX*,qAX,CWOP-5:@181939z0000.00N/00000.00E_003/002g007t063P000h44b10248ws31
20180218203958EW66880>APRS,TCPXX*,qAX,CWOP-4:@182039z0000.00N/00000.00E_214/000g004t064P000h41b10247ws31
20180218213958EW66880>APRS,TCPXX*,qAX,CWOP-2:@182139z0000.00N/00000.00E_108/003g007t065P000h45b10246ws31