APRS Packet Errors for HB9PKP-10 (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
20260209091428HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209092430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209093430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209094429HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209095430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209100430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209101429HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209102430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209103430HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209104429HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209111429HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209114430HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209115431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209120441HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209121430HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209122431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209123431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209124430HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209125431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209131430HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209132431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209133431HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209134431HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209135432HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209140432HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209141431HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209143432HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209144431HB9PKP-10>APGW1K,TCPIP*,qAC,NINTH:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209145432HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV
20260209150432HB9PKP-10>APGW1K,qAO,HB9HRL-4:!4654.11N/00711.33E&APRS iGate in Liebistorf JN36OV