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
20190825025625EW66880>APRS,TCPXX*,qAX,CWOP-7:@250256z0000.00N/00000.00E_285/000g001t085P000h69b10113ws31
20190825035625EW66880>APRS,TCPXX*,qAX,CWOP-1:@250356z0000.00N/00000.00E_147/000g004t083P000h74b10120ws31
20190825045625EW66880>APRS,TCPXX*,qAX,CWOP-1:@250456z0000.00N/00000.00E_196/002g005t081P000h80b10123ws31
20190825055625EW66880>APRS,TCPXX*,qAX,CWOP-1:@250556z0000.00N/00000.00E_189/000g001t080P000h84b10116ws31
20190825065626EW66880>APRS,TCPXX*,qAX,CWOP-7:@250656z0000.00N/00000.00E_195/000g002t079P002h92b10111ws31
20190825075626EW66880>APRS,TCPXX*,qAX,CWOP-7:@250756z0000.00N/00000.00E_210/000g001t078P004h95b10106ws31