APRS Packet Errors for BG2GDN-11 (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
20260209091336BG2GDN-11>APBM1D,DMR*,qAS,BM4602-10:=4630.08N/12452.45EX360/000/A=000698大庆阳光叔
20260209130345BG2GDN-11>APBM1D,DMR*,qAS,BM4601-10:=4630.01N/12452.45EX360/000/A=000715大庆阳光叔
20260209131900BG2GDN-11>APBM1D,DMR*,qAS,BM4601-10:=4630.02N/12452.46EX360/000/A=000669大庆阳光叔
20260209132029BG2GDN-11>APBM1D,DMR*,qAS,BM4601-10:=4630.09N/12452.47EX360/000/A=000347大庆阳光叔
20260209132204BG2GDN-11>APBM1D,DMR*,qAS,BM4601-10:=4630.09N/12452.46EX360/000/A=000301大庆阳光叔