APRS Packet Errors for BG2GLJ-7 (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
20260209162650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209165650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.48EK360/000/A=000639N7600 438.500 13.80V
20260209172650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.53N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209175650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209182650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.53N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209185650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.53N/12628.48EK360/000/A=000639N7600 438.500 13.80V
20260209192650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.46EK360/000/A=000639N7600 438.500 13.79V
20260209195650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209202650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.53N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209205650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.53N/12628.47EK360/000/A=000639N7600 438.500 13.80V
20260209212650BG2GLJ-7>APN000,WIDE1-1,WIDE2-1,qAS,BR2AG:=4547.52N/12628.47EK360/000/A=000639N7600 438.500 13.79V