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
20251214090716KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@090714h4100633N/08402.75WX239/000DMR
20251214122822KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@122820h4100330N/08402.75WX358/000DMR
20251214123634KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@123632h4100.63N/W0X225/358DMR
20251214123837KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@123835h400.632N/08402.75WX225/000DMR
20251214124255KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@124252h410.632N/08402.75WX358/000DMR
20251214124701KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@124658h4100.63/08402.75WX358/000DMR
20251214125715KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@125713h4100.63N/W0X225/358DMR
20251214130121KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@130119h40.6325N/08402.75WX358/000DMR
20251214130730KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@130728h4100322N/08402.75WX358/000DMR
20251214131136KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@131134h40.6313N/08402.75WX358/000DMR
20251214131340KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@131337h00.6323N/08402.75WX358/000DMR
20251214132203KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@13201.h4100.63N/08402525WX358/000DMR
20251214134043KR8MER-15>APBM1D,KR8MER,DMR*,qAR,KR8MER:@134040h4100.63N/W0X225/358DMR