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
20170922002825EW66880>APRS,TCPXX*,qAX,CWOP-4:@220028z0000.00N/00000.00E_336/000g000t073P000h86b10157ws31
20170922012837EW66880>APRS,TCPXX*,qAX,CWOP-3:@220128z0000.00N/00000.00E_336/000g000t072P000h90b10163ws31
20170922022824EW66880>APRS,TCPXX*,qAX,CWOP-3:@220228z0000.00N/00000.00E_336/000g000t070P000h93b10167ws31
20170922032820EW66880>APRS,TCPXX*,qAX,CWOP-1:@220328z0000.00N/00000.00E_306/000g001t070P000h88b10172ws31
20170922042835EW66880>APRS,TCPXX*,qAX,CWOP-2:@220428z0000.00N/00000.00E_306/000g000t068P000h91b10171ws31
20170922052819EW66880>APRS,TCPXX*,qAX,CWOP-5:@220528z0000.00N/00000.00E_306/000g000t067P000h93b10170ws31