APRS Packet Errors for AB9A (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
20250701031745AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@031744h0000.00N/00000.00E[121/000Clay
20250701032100AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@032059h0000.00N/00000.00E[121/000Clay
20250701032409AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@032407h0000.00N/00000.00E[121/000Clay
20250701032710AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@032709h0000.00N/00000.00E[121/000Clay
20250701033201AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@033200h0000.00N/00000.00E[121/000Clay
20250701033502AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@033501h0000.00N/00000.00E[121/000Clay
20250701033829AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@033828h0000.00N/00000.00E[121/000Clay
20250701034130AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@034129h0000.00N/00000.00E[121/000Clay
20250701034431AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@034430h0000.00N/00000.00E[121/000Clay
20250701034732AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@034731h0000.00N/00000.00E[121/000Clay
20250701035033AB9A>APBM1D,AB9A,DMR*,qAR,AB9A:@035032h0000.00N/00000.00E[121/000Clay