APRS Packet Errors for EA4BHK-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
20260110153617EA4BHK-10>APLHRG,WIDE1-1,QC2O6,qAR,EA4DAT-10:!4004.52ä00g1°€÷SY.../.W-..t043b10191 LoRa APRS BMbyy¤ZX Âhtu=³®ib
20260110183617EA4BHK-10>APLHRG,WIDE1-1,QB9O2,qAR,EA4DAT-10:!4004.58NLš8‘0.30W_.../...g...t031b10230 LoRa APRS BME280 WX Batt=3.94V
20260110184617EA4BHK-10>APLHRG,WIDE1-1,QB9O2,qAR,EA4DAT-10:)40¸4.58NL00210.30W_.../...g...t031b10232 LoRa APRS BME280 WX Batt=3.90V
20260110195617EA4BHK-10>APLHRG,WIDE1-1,QB9O2,qAR,EA4DAT-10:!4004.58NL90¢¡9.30W_.../...g...t030b10240 LoRa APRS BME280 WX Batt=3.76V