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
20171018142957EW66880>APRS,TCPXX*,qAX,CWOP-4:@181429z0000.00N/00000.00E_092/003g004t056P000h67b10284ws31
20171018153000EW66880>APRS,TCPXX*,qAX,CWOP-3:@181529z0000.00N/00000.00E_027/001g007t060P000h53b10285ws31
20171018162958EW66880>APRS,TCPXX*,qAX,CWOP-5:@181629z0000.00N/00000.00E_339/003g008t064P000h42b10282ws31
20171018173001EW66880>APRS,TCPXX*,qAX,CWOP-5:@181730z0000.00N/00000.00E_264/001g005t066P000h36b10271ws31
20171018182958EW66880>APRS,TCPXX*,qAX,CWOP-1:@181829z0000.00N/00000.00E_276/002g003t068P000h34b10262ws31
20171018192958EW66880>APRS,TCPXX*,qAX,CWOP-7:@181929z0000.00N/00000.00E_315/000g003t070P000h32b10256ws31