APRS Packet Errors for BD6ICM-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
20261001121825BD6ICM-7>APBM1D,BG4RDQ,DMR*,qAR,BG4RDQ:@21822.h3217.54N/1837.067Ee088/052DMR BM APRS
20261001123335BD6ICM-7>APBM1D,BG4RDQ,DMR*,qAR,BG4RDQ:@123331h3211.04N/1149.253Ee140/051DMR BM APRS
20261001124108BD6ICM-7>APBM1D,BG4RDQ,DMR*,qAR,BG4RDQ:@124105h3207.32N/1185.158Ee248/000DMR BM APRS
20261001141646BD6ICM-7>APBM1D,BG4RDQ,DMR*,qAR,BG4RDQ:@141643h3159.81N/11850.544e026/141DMR BM APRS
20261001142413BD6ICM-7>APBM1D,BG4RDQ,DMR*,qAR,BG4RDQ:@142410h3155.51N/1154.526Ee141/052DMR BM APRS
20261001155134BD6ICM-7>APBM1D,BH4TNL,DMR*,qAR,BH4TNL:@155131h133.480N/12004.61Ee073/623DMR BM APRS