APRS Packet Errors for XE2JHR-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
20260209133003XE2JHR-10>APLRG1,WIDE2-1,qAR,XE2AD-5:!LCHBr4ZYC_ xG.../...g...t...r...p...P...h..b.....LoRa APRS - Igate & Digipeater Batt=4.20V Ext=0.76V
20260209142003XE2JHR-10>APLRG1,WIDE2-1,qAR,XE2AD-5:!LCHBr4ZYC_ xG.../...g...t...r...p...P...h..b.....LoRa APRS - Igate & Digipeater Batt=4.24V Ext=0.75V
20260209151003XE2JHR-10>APLRG1,WIDE2-1,qAR,XE2AD-5:!LCHBr4ZYC_ xG.../...g...t...r...p...P...h..b.....LoRa APRS - Igate & Digipeater Batt=4.18V Ext=0.73V
20260209165003XE2JHR-10>APLRG1,WIDE2-1,qAR,XE2AD-5:!LCHBr4ZYC_ xG.../...g...t...r...p...P...h..b.....LoRa APRS - Igate & Digipeater Batt=4.28V Ext=0.71V
20260209183004XE2JHR-10>APLRG1,WIDE2-1,qAR,XE2AD-5:!LCHBr4ZYC_ xG.../...g...t...r...p...P...h..b.....LoRa APRS - Igate & Digipeater Batt=4.22V Ext=0.67V