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
20180918132407EW66880>APRS,TCPXX*,qAX,CWOP-1:@181324z0000.00N/00000.00E_321/000g000t073P000h97b10150ws31
20180918144659EW66880>APRS,TCPXX*,qAX,CWOP-6:@181446z0000.00N/00000.00E_326/000g003t082P000h82b10154ws31
20180918154659EW66880>APRS,TCPXX*,qAX,CWOP-6:@181546z0000.00N/00000.00E_306/002g002t087P000h73b10154ws31
20180918164659EW66880>APRS,TCPXX*,qAX,CWOP-1:@181646z0000.00N/00000.00E_299/000g004t090P000h63b10150ws31
20180918174659EW66880>APRS,TCPXX*,qAX,CWOP-4:@181746z0000.00N/00000.00E_304/000g003t094P000h57b10142ws31
20180918184659EW66880>APRS,TCPXX*,qAX,CWOP-4:@181846z0000.00N/00000.00E_321/000g001t096P000h51b10132ws31