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
20190222041842EW66880>APRS,TCPXX*,qAX,CWOP-7:@220418z0000.00N/00000.00E_346/000g001t049P041h97b10137ws31
20190222051842EW66880>APRS,TCPXX*,qAX,CWOP-3:@220518z0000.00N/00000.00E_318/000g002t048P041h98b10140ws31
20190222061842EW66880>APRS,TCPXX*,qAX,CWOP-5:@220618z0000.00N/00000.00E_314/000g002t048P000h97b10143ws31
20190222071842EW66880>APRS,TCPXX*,qAX,CWOP-1:@220718z0000.00N/00000.00E_323/000g001t048P000h98b10142ws31
20190222081842EW66880>APRS,TCPXX*,qAX,CWOP-7:@220818z0000.00N/00000.00E_326/002g004t048P000h98b10140ws31