APRS Packet Errors for GM7GRH-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
20260208171747	GM7GRH-10>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.22V
20260208174747	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.23V
20260208181747	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.23V
20260208184747	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.22V
20260208191748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.23V
20260208194748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.22V
20260208201748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.22V
20260208204748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.21V
20260208211748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.22V
20260208214748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.23V
20260208221748	GM7GRH-10>APLRG1,TCPIP*,qAC,T2PERTH:!L2FykMgoYa GSelkirk District LoRa APRS iGate Batt=4.24V