APRS Packet Errors for FW0498 (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
20180716102108FW0498>APRS,TCPXX*,qAX,CWOP-7:@161021z3922.74N/10450.100W_023/000g000t058r000P001h91b10245mUtWX
20180716104706FW0498>APRS,TCPXX*,qAX,CWOP-3:@161046z3922.74N/10450.100W_270/000g000t056r000P001h92b10245mUtWX
20180716115413FW0498>APRS,TCPXX*,qAX,CWOP-7:@161154z3922.74N/10450.100W_270/000g000t055r000P001h93b10243mUtWX
20180716124617FW0498>APRS,TCPXX*,qAX,CWOP-5:@161246z3922.74N/10450.100W_045/000g000t054r000P001h93b10248mUtWX
20180716131208FW0498>APRS,TCPXX*,qAX,CWOP-4:@161312z3922.74N/10450.100W_338/000g000t055r000P001h93b10248mUtWX
20180716142431FW0498>APRS,TCPXX*,qAX,CWOP-5:@161424z3922.74N/10450.100W_270/000g000t066r000P001h78b10248mUtWX
20180716145023FW0498>APRS,TCPXX*,qAX,CWOP-4:@161450z3922.74N/10450.100W_270/000g000t068r000P001h76b10252mUtWX
20180716154713FW0498>APRS,TCPXX*,qAX,CWOP-7:@161547z3922.74N/10450.100W_248/000g000t075r000P001h59b10251mUtWX