🧭 Path Prefix Decoder
Paste a MeshCore message path (the repeater prefix hashes it travelled through) to decode it into named repeaters, hop distances, and flag any ambiguous or repeated hops.
Accepts 1, 2 or 3-byte prefixes per hop, in any common format — e.g. e1,3a,7f, !e1 !3a !7f,
e1a2,3ac1,7f09, or newline/pipe/arrow separated. One path per box.
Reading this view: each card is one hop, in the order it appears in the path (first hop closest to the sender).
Green = resolved to a single known repeater, amber = duplicate prefix (matches more than one known repeater — see
path hash mode), grey = unknown prefix (not in current network data), red = invalid token.
A purple ring and badge mark hops that repeat an earlier hop in this same path (same repeater, or same colliding prefix).
When a hop has a duplicate prefix, the repeater with the shortest overall route is shown as the main route and labelled 📏 Shortest Path. The other repeaters sharing that prefix are listed below it — click one to make it the main route instead.
When a hop has a duplicate prefix, the repeater with the shortest overall route is shown as the main route and labelled 📏 Shortest Path. The other repeaters sharing that prefix are listed below it — click one to make it the main route instead.
Paste a path above and click "Decode Path" to get started.