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
20171217230826EW66880>APRS,TCPXX*,qAX,CWOP-1:@172308z0000.00N/00000.00E_262/000g000t051P000h57b10217ws31
20171218000825EW66880>APRS,TCPXX*,qAX,CWOP-4:@180008z0000.00N/00000.00E_262/000g001t050P000h62b10218ws31
20171218010832EW66880>APRS,TCPXX*,qAX,CWOP-6:@180108z0000.00N/00000.00E_256/000g002t051P000h56b10218ws31
20171218020829EW66880>APRS,TCPXX*,qAX,CWOP-4:@180208z0000.00N/00000.00E_267/000g003t052P000h58b10216ws31
20171218030828EW66880>APRS,TCPXX*,qAX,CWOP-7:@180308z0000.00N/00000.00E_261/000g001t051P000h64b10219ws31
20171218040832EW66880>APRS,TCPXX*,qAX,CWOP-3:@180408z0000.00N/00000.00E_261/000g000t050P000h68b10215ws31