APRS Packet Errors for HB9ZG-12 (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
20260209092550HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209095550HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209102550HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209105555HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209112555HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209115600HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209122600HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209125605HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209132610HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209135610HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209142610HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260209145615HB9ZG-12>APOTW1,TCPIP*,qAC,T2DENMARK:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg