APRS Packet Errors for HP2AT-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
20260209092043	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209095044	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209102044	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209105045	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209112046	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209115037	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209122038	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209125038	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209132039	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209135040	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209142350	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz
20260209145046	HP2AT-10>APLRG1,TCPIP*,qAC,T2PANAMA:=LIfH9:<@la !GLoRa APRS iGate Colon 433.775 Mhz