APRS Packet Errors for N2USM (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
20260208140100	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@140059h3923.00N/09434.87Wk000/000N2USM
20260208141102	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@141057h3923.00N/09434.87Wk000/000N2USM
20260208142103	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@142102h3923.00N/09434.87Wk000/000N2USM
20260208154113	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@154112h3923.00N/09434.87Wk000/000N2USM
20260208155115	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@155057h3923.00N/09434.87Wk000/000N2USM
20260208160116	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@160115h3923.00N/09434.87Wk000/000N2USM
20260208173113	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@173112h3923.00N/09434.87Wk000/000N2USM
20260208174115	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@174114h3923.00N/09434.87Wk000/000N2USM
20260208183122	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@183121h3923.00N/09434.87Wk000/000N2USM
20260208184124	N2USM>APBM1D,N2USM,DMR*,qAR,N2USM:@184110h3923.00N/09434.87Wk000/000N2USM