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
20190418091712EW66880>APRS,TCPXX*,qAX,CWOP-5:@180917z0000.00N/00000.00E_219/001g004t062P093h96b10077ws31
20190418101711EW66880>APRS,TCPXX*,qAX,CWOP-1:@181017z0000.00N/00000.00E_100/000g003t062P106h96b10066ws31
20190418111712EW66880>APRS,TCPXX*,qAX,CWOP-5:@181117z0000.00N/00000.00E_045/000g001t062P119h97b10072ws31
20190418121712EW66880>APRS,TCPXX*,qAX,CWOP-5:@181217z0000.00N/00000.00E_052/000g003t062P135h98b10059ws31
20190418131712EW66880>APRS,TCPXX*,qAX,CWOP-3:@181317z0000.00N/00000.00E_073/000g002t062P143h98b10071ws31
20190418141712EW66880>APRS,TCPXX*,qAX,CWOP-6:@181417z0000.00N/00000.00E_154/001g002t061P164h98b10060ws31