APRS Packet Errors for SP9EP-9 (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
20250421130359SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@130357h4943.53N/846.5646E>345/000TG260998 145.425 MHz
20250421134421SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@134419h4943.53N/01846.560>425/345TG260998 145.425 MHz
20250421134727SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@134725h4943.530/E0>425/345TG260998 145.425 MHz
20250421135951SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@135949h4943.53N/0846.566E>345/000TG260998 145.425 MHz
20250421141521SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@141519h4943.53N/016.5655E>345/000TG260998 145.425 MHz
20250421142306SP9EP-9>APBM1D,SR9US,DMR*,qAR,SR9US:@142304h4943.46N/018.4567E>202/007TG260998 145.425 MHz