APRS Packet Errors for G4OXN-5 (last 168 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
20261026123611G4OXN-5>APLRG1,TCPIP*,qAC,T2CHILE:!LoRa APRS Experimental Batt=3.11V
20261026133612G4OXN-5>APLRG1,TCPIP*,qAC,T2CHILE:!LoRa APRS Experimental Batt=3.01V
20261028192540G4OXN-5>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Experimental Batt=4.18V
20261028221043G4OXN-5>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Experimental Batt=4.18V
20261029001046G4OXN-5>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS Experimental Batt=4.17V
20261029222718G4OXN-5>APLRG1,TCPIP*,qAC,T2ROMANIA:!LoRa APRS Experimental Batt=4.17V
20261030032737G4OXN-5>APLRG1,TCPIP*,qAC,T2SJC:!LoRa APRS Experimental Batt=4.17V
20261030162755G4OXN-5>APLRG1,TCPIP*,qAC,T2SJC:!LoRa APRS Experimental Batt=4.17V