APRS Packet Errors for HB9GFZ-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
20260209091618HB9GFZ-10>APOTW1,TCPIP*,qAC,T2LAUSITZ:!4741.18NL00837.82E&PHG0000Lora iGate
20260209094737HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209101740HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209104740HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209111744HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209114745HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209121745HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209124745HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209131750HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209134750HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209141750HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate
20260209144754HB9GFZ-10>APOTW1,TCPIP*,qAC,T2UK:!4741.18NL00837.82E&PHG0000Lora iGate