APRS Packet Errors for OK2MNL-19 (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
20260127102914OK2MNL-19>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Batt=3.76V
20260127125924OK2MNL-19>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Batt=3.66V
20260127141427OK2MNL-19>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Batt=3.62V
20260127154435OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.64V
20260127155935OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.66V
20260127161435OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.66V
20260127162936OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.68V
20260127164436OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.69V
20260127165937OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.69V
20260127171437OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.70V
20260127172948OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.70V
20260127174438OK2MNL-19>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Batt=3.71V