APRS Packet Errors for BM1CCR (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
20251122170604BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@170601h2508478N/12144.34E[001/000DMR ID: 4660138
20251122172513BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@172511h2508.79N/144.0874E[272/000DMR ID: 4660138
20251122172835BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@12832.h2508.79N/1214.074E[290/000DMR ID: 4660138
20251122174329BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@17426.h2508.80N/12144068E[272/001DMR ID: 4660138
20251122175608BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@175605h2508.81N/12144.070[125/074DMR ID: 4660138
20251122175641BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@175638h250.812N/12144.07E[074/000DMR ID: 4660138
20251122180426BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@180423h28.8102N/12144.08E[040/002DMR ID: 4660138
20251122180604BM1CCR>APBM1D,BX2AJD,DMR*,qAR,BX2AJD:@180602h2508.81N/2144.074E[079/001DMR ID: 4660138