APRS Packet Errors for F4FEB-L (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
20260209091916F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.23V
20260209094916F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.24V
20260209101916F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.31V
20260209104917F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.23V
20260209111917F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.25V
20260209114917F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.27V
20260209121917F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.26V
20260209124917F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.20V
20260209131918F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.21V
20260209134918F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.23V
20260209141918F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.28V
20260209144918F4FEB-L>APLRG1,TCPIP*,qAC,T2CSNGRAD:!L6`;?O{M5a GLoRa APRS Igate Batt=4.26V