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
20260208131916F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.19V
20260208134917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.19V
20260208141917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.27V
20260208144917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.29V
20260208151917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.24V
20260208154917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.20V
20260208161917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.28V
20260208164917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.20V
20260208171917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.24V
20260208174917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.22V
20260208181917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.23V
20260208184917F4FEB-L>APLRG1,TCPIP*,qAC,T2BIO:!L6`;?O{M5a GLoRa APRS Igate Batt=4.26V