APRS Packet Errors for DN9TOM-2 (last 24 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
20251014101644	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@101642h535.426N/00954.63E>313/000DN9TOM
20251014131933	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@131930h5335.42N/004.6373E>326/000DN9TOM
20251014140316	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@140313h5335.420/E0>025/056DN9TOM
20251014140926	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@14923.h5335.42N/00954422E>305/000DN9TOM
20251014141333	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@11330.h5335.41N/0094.645E>000/000DN9TOM
20251014142610	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@12605.h5335.42N/00956369E>119/000DN9TOM
20251014143021	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@143016h5335.42N/054.6401E>333/000DN9TOM
20251014143842	DN9TOM-2>APBM1D,DB0FS,DMR*,qAR,DB0FS:@143840h5334247N/00954.64E>000/000DN9TOM