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
20170920012832EW66880>APRS,TCPXX*,qAX,CWOP-3:@200128z0000.00N/00000.00E_008/000g000t070P001h94b10142ws31
20170920022813EW66880>APRS,TCPXX*,qAX,CWOP-2:@200228z0000.00N/00000.00E_008/000g000t069P001h96b10144ws31
20170920032825EW66880>APRS,TCPXX*,qAX,CWOP-2:@200328z0000.00N/00000.00E_008/000g000t068P001h96b10145ws31
20170920042832EW66880>APRS,TCPXX*,qAX,CWOP-2:@200428z0000.00N/00000.00E_008/000g000t067P000h96b10146ws31
20170920052828EW66880>APRS,TCPXX*,qAX,CWOP-7:@200528z0000.00N/00000.00E_008/000g000t066P000h97b10148ws31
20170920062829EW66880>APRS,TCPXX*,qAX,CWOP-5:@200628z0000.00N/00000.00E_008/000g000t065P000h97b10148ws31