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
20260208134552	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208141557	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208144557	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208151557	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208154602	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208161607	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208164607	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208171607	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208174612	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208181612	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208184612	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg
20260208191612	HB9ZG-12>APOTW1,TCPIP*,qAC,T2SPAIN:!4701.65NL00831.20E&PHG0000LoRa iGate Rigi-Scheidegg