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
20171022114617EW66880>APRS,TCPXX*,qAX,CWOP-3:@221146z0000.00N/00000.00E_348/000g000t048P001h97b10264ws31
20171022124640EW66880>APRS,TCPXX*,qAX,CWOP-2:@221246z0000.00N/00000.00E_348/000g000t052P001h98b10268ws31
20171022134640EW66880>APRS,TCPXX*,qAX,CWOP-3:@221346z0000.00N/00000.00E_003/001g002t060P001h96b10273ws31
20171022144650EW66880>APRS,TCPXX*,qAX,CWOP-4:@221446z0000.00N/00000.00E_008/001g002t065P001h91b10272ws31
20171022154642EW66880>APRS,TCPXX*,qAX,CWOP-1:@221546z0000.00N/00000.00E_325/002g004t073P001h69b10266ws31
20171022164645EW66880>APRS,TCPXX*,qAX,CWOP-5:@221646z0000.00N/00000.00E_104/002g006t076P001h64b10258ws31