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
20260208163058HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208164559HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208170059HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208171600HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208173100HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208174601HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208181602HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208183102HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208184603HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208191604HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208193105HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208194605HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208200106HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208201606HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208203107HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208204608HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208210109HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208211610HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208213110HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208214610HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208220111HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK
20260208221611HB9FM-2>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6O#rPF[-& GLoRa iGate Pfeffingen JN37TK