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
20170922052819EW66880>APRS,TCPXX*,qAX,CWOP-5:@220528z0000.00N/00000.00E_306/000g000t067P000h93b10170ws31
20170922062822EW66880>APRS,TCPXX*,qAX,CWOP-6:@220628z0000.00N/00000.00E_307/000g000t066P000h95b10169ws31
20170922072836EW66880>APRS,TCPXX*,qAX,CWOP-4:@220728z0000.00N/00000.00E_307/000g000t066P000h96b10166ws31
20170922082839EW66880>APRS,TCPXX*,qAX,CWOP-4:@220828z0000.00N/00000.00E_307/000g000t065P000h96b10166ws31
20170922092825EW66880>APRS,TCPXX*,qAX,CWOP-7:@220928z0000.00N/00000.00E_307/000g000t065P000h97b10171ws31
20170922102823EW66880>APRS,TCPXX*,qAX,CWOP-2:@221028z0000.00N/00000.00E_307/000g000t065P000h97b10175ws31