APRS Packet Errors for HA2KAB-10 (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
20260209093924HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t043h75b10149LoRa APRS Batt=4.31V
20260209103824HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t043h75b10147LoRa APRS Batt=4.34V
20260209113724HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t044h74b10146LoRa APRS Batt=4.32V
20260209120120HA2KAB-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6ak(Rx*G_ G.../...g...t044h74b10144LoRa APRS Batt=4.29V
20260209130020HA2KAB-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6ak(Rx*G_ G.../...g...t044h75b10142LoRa APRS Batt=4.32V
20260209135920HA2KAB-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6ak(Rx*G_ G.../...g...t043h75b10143LoRa APRS Batt=4.30V
20260209145821HA2KAB-10>APLRG1,TCPIP*,qAC,T2PERTH:!L6ak(Rx*G_ G.../...g...t043h75b10143LoRa APRS Batt=4.30V