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
20190220081836EW66880>APRS,TCPXX*,qAX,CWOP-4:@200818z0000.00N/00000.00E_323/000g003t044P001h96b10116ws31
20190220091836EW66880>APRS,TCPXX*,qAX,CWOP-7:@200918z0000.00N/00000.00E_295/000g002t044P001h96b10120ws31
20190220101836EW66880>APRS,TCPXX*,qAX,CWOP-3:@201018z0000.00N/00000.00E_275/000g002t043P002h96b10124ws31
20190220111836EW66880>APRS,TCPXX*,qAX,CWOP-6:@201118z0000.00N/00000.00E_029/000g003t043P002h96b10122ws31
20190220121836EW66880>APRS,TCPXX*,qAX,CWOP-7:@201218z0000.00N/00000.00E_318/000g003t043P002h96b10131ws31
20190220131837EW66880>APRS,TCPXX*,qAX,CWOP-4:@201318z0000.00N/00000.00E_206/000g003t042P002h95b10140ws31