APRS Packet Errors for AG2I-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
20260208163314	AG2I-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=L9pWB<$_%a !GLoRa APRS Batt=4.27V
20260208164814	AG2I-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=L9pWB<$_%a !GLoRa APRS Batt=4.27V
20260208200854	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.28V
20260208202354	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.27V
20260208203855	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.28V
20260208205356	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.26V
20260208210856	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.26V
20260208212356	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.27V
20260208213856	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.28V
20260208215356	AG2I-10>APLRG1,TCPIP*,qAC,T2PERTH:=L9pWB<$_%a !GLoRa APRS Batt=4.27V