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
20260208165620HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t045h71b10131LoRa APRS Batt=4.32V
20260208175520HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t044h74b10133LoRa APRS Batt=4.29V
20260208185420HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t044h73b10136LoRa APRS Batt=4.26V
20260208195321HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t044h73b10139LoRa APRS Batt=4.35V
20260208205221HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t045h73b10141LoRa APRS Batt=4.26V
20260208215121HA2KAB-10>APLRG1,TCPIP*,qAC,T2UKRAINE:!L6ak(Rx*G_ G.../...g...t045h72b10141LoRa APRS Batt=4.26V