APRS Packet Errors for K3MOT-7 (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
20250420150859K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@015857h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420161312K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@161307h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420161615K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@161611h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420161746K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@161743h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420161918K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@161912h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162050K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162048h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162222K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162218h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162354K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162352h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162526K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162521h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162658K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162653h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn
20250420162830K3MOT-7>APBM1D,K3MOT,DMR*,qAR,K3MOT:@162828h0000.00N/00000.00E(000/000!SN!@NCCO_DE_Skywarn