APRS Packet Errors for HA9OZD-18 (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
20260209105050HA9OZD-18>APLRG1,TCPIP*,qAC,T2CHILE:!L62uZS^0T_ G.../...g...t033h00b10111LoRa APRS Batt=4.04V
20260209115052HA9OZD-18>APLRG1,TCPIP*,qAC,T2CHILE:!L62uZS^0T_ G.../...g...t032h00b10110LoRa APRS Batt=4.04V
20260209125052HA9OZD-18>APLRG1,TCPIP*,qAC,T2CHILE:!L62uZS^0T_ G.../...g...t032h00b10107LoRa APRS Batt=4.03V
20260209125100HA9OZD-18>APLRG1,HA9OZD-20*,qAO,HA0HP-10:!L62uZS^0T_ G.¦&¯®&.g...t032h00b10107LoRa APRS Batt=4.03V
20260209135053HA9OZD-18>APLRG1,TCPIP*,qAC,T2CHILE:!L62uZS^0T_ G.../...g...t032h00b10108LoRa APRS Batt=4.04V
20260209145043HA9OZD-18>APLRG1,TCPIP*,qAC,T2ROMANIA:!L62uZS^0T_ G.../...g...t031h00b10111LoRa APRS Batt=4.02V
20260209155044HA9OZD-18>APLRG1,TCPIP*,qAC,T2ROMANIA:!L62uZS^0T_ G.../...g...t031h00b10113LoRa APRS Batt=4.04V