APRS Packet Errors for HB9XAR-4 (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
20260209120402HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209123012HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209125702HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209132306HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209134852HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209141727HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209144712HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209151317HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209154317HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209161307HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209163942HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209170612HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate
20260209173319HB9XAR-4>APRX29,TCPIP*,qAC,T2SWISS1:!4720.52NR00803.50E&Rx-only iGate