APRS Packet Errors for EB4EYD-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
20260208145728	EB4EYD-10>APLRG1,WIDE1-1,qAR,EA4GSB-10:=L:+jbMS#*a !GLoRa APRS Batt=3.65V Ext=7.69V
20260208151228	EB4EYD-10>APLRG1,WIDE1-1,qAR,EA4GSB-10:=L:+jbMS#*a !GLoRa APRS Batt=3.61V Ext=16.08V
20260208152728	EB4EYD-10>APLRG1,WIDE1-1,qAO,EA1ARW-10:=L:+jbMS#*a !GLoRa APRS Batt=3.46V Ext=16.08V
20260208193754	EB4EYD-10>APLRG1,WIDE1-1,qAR,EA4GSB-10:=L:+jbMS#*a !GLoRa APRS Batt=3.03V Ext=16.08V
20260208195255	EB4EYD-10>APLRG1,WIDE1-1,qAO,EA4MZ-10:=L:+jbMS#*a !GLoRa APRS Batt=3.03V Ext=16.08V
20260208202255	EB4EYD-10>APLRG1,WIDE1-1,qAO,EA4MZ-10:=L:+jbMS#*a !GLoRa APRS Batt=3.05V Ext=16.08V