APRS Packet Errors for F1FFS-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
20250917090915	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.11V
20250917093915	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.21V
20250917100916	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250917102416	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.16V
20250917103916	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.07V
20250917105417	F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.02V