APRS Packet Errors for HB9FM-2 (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
20260209114643HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209120144HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209121644HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209123144HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209124645HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209130146HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209131646HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209133147HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209134648HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209140148HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209141649HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209143149HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209144650HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209150150HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209151651HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209153152HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209154652HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209160153HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209161654HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209163155HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209164656HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209170157HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209171658HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260209173159HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK