APRS Packet Errors for EA4FMI-11 (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
20260209131752EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.21V
20260209134752EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.23V
20260209141752EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.29V
20260209144752EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.27V
20260209151752EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.26V
20260209154753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.30V
20260209161753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.28V
20260209164753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.18V
20260209171753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.16V
20260209174753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.23V
20260209181753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.23V
20260209184753EA4FMI-11>APLRG1,TCPIP*,qAC,T2ROMANIA:!L:#NYM_sJa GLoRa APRS Batt=4.27V