APRS Packet Errors for F1FFS-10 (last 24 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
20250913151916F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913153416F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913154916F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913161916F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913163417F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913180418F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913181919F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250913184919F1FFS-10>APLRG1,TCPIP*,qAC,T2SPAIN:!LoRa APRS Batt=4.15V
20250914091616F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914101617F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914103117F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914104618F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914110118F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914114619F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914123120F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914124620F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V
20250914150123F1FFS-10>APLRG1,TCPIP*,qAC,T2DENMARK:!LoRa APRS Batt=4.17V