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
20260208135040HA9OZD-18>APLRG1,TCPIP*,qAC,T2SYDNEY:!L62uZS^0T_ G.../...g...t033h00b10076LoRa APRS Batt=4.04V
20260208135047HA9OZD-18>APLRG1,HA9OZD-20*,qAR,HA9OZD-17:!L62uZS^0T_ G.../...g...t :2h90E@276LoRa APRS Batt=4.04V
20260208145044HA9OZD-18>APLRG1,TCPIP*,qAC,T2SPAIN:!L62uZS^0T_ G.../...g...t033h00b10077LoRa APRS Batt=4.03V
20260208145056HA9OZD-18>APLRG1,HA9OZD-20*,qAR,HA9OZD-17:!L62uZS^0T_ G.../...g...t ӑl#=34LoRi aprSdBt403V
20260208155045HA9OZD-18>APLRG1,TCPIP*,qAC,T2SPAIN:!L62uZS^0T_ G.../...g...t033h00b10080LoRa APRS Batt=4.04V
20260208155056HA9OZD-18>APLRG1,HA9OZD-20*,qAR,HA9OZD-17:!L62uZS^0T_ G.../...g...t$MXjy3 e$ǻ
20260208165045HA9OZD-18>APLRG1,TCPIP*,qAC,T2SPAIN:!L62uZS^0T_ G.../...g...t033h00b10083LoRa APRS Batt=4.04V
20260208165056HA9OZD-18>APLRG1,HA9OZD-20*,qAR,HA9OZD-17:!L62uZS^0T_ G.../...g...t033h00b100C6{
20260208175045HA9OZD-18>APLRG1,TCPIP*,qAC,T2SPAIN:!L62uZS^0T_ G.../...g...t032h00b10086LoRa APRS Batt=4.04V
20260208175056HA9OZD-18>APLRG1,HA9OZD-20*,qAR,HA9OZD-17:!L62uZS^0T_+fhvM.fF f7i0؄/-r} ?³x
20260208185046HA9OZD-18>APLRG1,TCPIP*,qAC,T2SPAIN:!L62uZS^0T_ G.../...g...t031h00b10089LoRa APRS Batt=4.03V