APRS Packet Errors for HB9ASF-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
20260208150209	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208153209	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208160214	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208163219	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208170219	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208173224	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208180224	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208183229	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208190229	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208193234	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208200239	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate
20260208203239	HB9ASF-10>APOTW1,TCPIP*,qAC,T2POLC:!4727.79NL00935.15E&PHG0000Lora iGate