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
20170722212748EW66880>APRS,TCPXX*,qAX,CWOP-6:@222127z0000.00N/00000.00E_230/002g006t096P000h54b10119ws31
20170722222748EW66880>APRS,TCPXX*,qAX,CWOP-1:@222227z0000.00N/00000.00E_315/001g001t095P000h57b10119ws31
20170722232749EW66880>APRS,TCPXX*,qAX,CWOP-6:@222327z0000.00N/00000.00E_323/000g001t093P000h60b10123ws31
20170723002749EW66880>APRS,TCPXX*,qAX,CWOP-4:@230027z0000.00N/00000.00E_310/000g000t086P000h72b10126ws31
20170723012749EW66880>APRS,TCPXX*,qAX,CWOP-7:@230127z0000.00N/00000.00E_301/000g001t082P000h80b10129ws31
20170723022749EW66880>APRS,TCPXX*,qAX,CWOP-6:@230227z0000.00N/00000.00E_299/000g001t082P000h80b10132ws31