APRS Packet Errors for WIR-42698 (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
20260208153248JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208160246JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208163246JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208170247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208173248JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208180247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208183247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208190248JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208193247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208200248JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208203247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz
20260208210247JA5YRY-10>APU25N,TCPIP*,qAC,T2PERTH:;WIR-42698*220217z3401.47NW13259.38E0JA5YRY 430.82MHz