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
20181017151035EW66880>APRS,TCPXX*,qAX,CWOP-7:@171510z0000.00N/00000.00E_342/002g004t057P001h94b10233ws31
20181017161035EW66880>APRS,TCPXX*,qAX,CWOP-5:@171610z0000.00N/00000.00E_335/001g003t059P001h91b10236ws31
20181017171035EW66880>APRS,TCPXX*,qAX,CWOP-6:@171710z0000.00N/00000.00E_353/000g002t060P001h91b10232ws31
20181017181035EW66880>APRS,TCPXX*,qAX,CWOP-7:@171810z0000.00N/00000.00E_295/000g004t060P001h91b10229ws31
20181017191035EW66880>APRS,TCPXX*,qAX,CWOP-4:@171910z0000.00N/00000.00E_352/001g003t060P001h91b10221ws31
20181017201035EW66880>APRS,TCPXX*,qAX,CWOP-5:@172010z0000.00N/00000.00E_330/002g002t060P001h93b10217ws31