APRS Packet Errors for W9TNC-15 (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
20260209110115W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.31V
20260209112615W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.26V
20260209115116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.30V
20260209121616W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.22V
20260209124116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.29V
20260209130616W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.32V
20260209133116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.31V
20260209135616W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.26V
20260209142116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.29V
20260209144616W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.25V
20260209151116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.30V
20260209153617W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.27V
20260209160116W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.26V
20260209162616W9TNC-15>APLRG1,TCPIP*,qAC,T2RDU:!L9,lA9?=]& GLoRa APRS Batt=4.26V