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
20180419094230EW66880>APRS,TCPXX*,qAX,CWOP-6:@190942z0000.00N/00000.00E_263/003g013t068P000h61b10065ws31
20180419104231EW66880>APRS,TCPXX*,qAX,CWOP-7:@191042z0000.00N/00000.00E_237/005g013t066P000h66b10069ws31
20180419114231EW66880>APRS,TCPXX*,qAX,CWOP-3:@191142z0000.00N/00000.00E_233/001g014t066P000h68b10077ws31
20180419124231EW66880>APRS,TCPXX*,qAX,CWOP-3:@191242z0000.00N/00000.00E_293/002g012t069P000h66b10082ws31
20180419134231EW66880>APRS,TCPXX*,qAX,CWOP-5:@191342z0000.00N/00000.00E_210/013g015t072P000h60b10088ws31
20180419144231EW66880>APRS,TCPXX*,qAX,CWOP-2:@191442z0000.00N/00000.00E_323/001g010t074P000h55b10093ws31