APRS Packet Errors for KR8MER-15 (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
20251215210951KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@210949h00.6324N/08402.75WX201/000DMR
20251215211420KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@211418h400.631N/08402.75WX225/000DMR
20251215212233KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@212230h4100.630/W0X225/081DMR
20251215212639KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@212636h100.633N/08402.75WX081/000DMR
20251215212842KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@212839h4100.63N/0402.753WX081/000DMR
20251215213500KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@213458h4100.63N/08402.750X225/081DMR
20251215213703KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@213701h100.635N/08402.75WX081/000DMR
20251215213906KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@13904.h4100.63N/0402.755WX081/000DMR
20251215215735KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@25733.h4100.63N/0842.754WX225/000DMR
20251215220141KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@20139.h4100.63N/0802.755WX225/000DMR
20251215222619KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@222617h4100.630/W0X225/250DMR
20251216011406KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@011403h4100.630/W0X225/240DMR
20251216011642KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@011639h4100.63N/08402751WX240/000DMR