APRS Packet Errors for DG2YHR-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
20250916102625DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@102623h5141.68N/0067.073E>025/000Dave on route
20250916102809DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@102807h5141.680/E1>925/025Dave on route
20250916103615DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@103613h41.6830N/00657.08E>128/001Dave on route
20250916103755DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@13752.h5141.66N/00655857E>184/018Dave on route
20250916103907DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@103904h51.2219N/00657.58E>168/015Dave on route
20250916103940DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@103937h5141.100/E1>925/161Dave on route
20250916104437DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@104434h5140.37N/00659.031>925/183Dave on route
20250916104649DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@104646h5140.30N/0069.929E>157/016Dave on route
20250916104722DG2YHR-9>APBM1D,DMR*,qAS,DL3OCK-12:@104719h5140.20N/00659.997>925/113Dave on route