APRS Packet Errors for GW0GTW-2 (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
20260208164026	GW0GTW-2>APLRG1,WIDE1-1,qAR,2E0JWA-10:!L3UslMRn!# GLoRa APRS Batt=4.09V
20260208171026	GW0GTW-2>APLRG1,WIDE1-1,qAR,2E0JWA-10:!L3UslMRn!# GLoRa APRS Batt=4.08V
20260208174027	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.08V
20260208181026	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.09V
20260208184026	GW0GTW-2>APLRG1,WIDE1-1,qAR,2E0JWA-10:!L3UslMRn!# GLoRa APRS Batt=4.08V
20260208191025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.07V
20260208194025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.09V
20260208201025	GW0GTW-2>APLRG1,WIDE1-1,qAR,2E0JWA-10:!L3UslMRn!# GLoRa APRS Batt=4.07V
20260208204025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.08V
20260208211025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.09V
20260208214025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.09V
20260208221025	GW0GTW-2>APLRG1,WIDE1-1,qAO,M0VAZ-11:!L3UslMRn!# GLoRa APRS Batt=4.09V