PacketTrends Mesh a public map of nodes that asked to be on one map stations

JDR_99

!0cdc117c · updates every minute

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; above the default of 3. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Heard on 37 days Sep 15 to Nov 15 · 37 active days · 953 RF frames · 2 gateways

Sep 15 Nov 15

Most recent

Home Two no pin 11m !617b46f7 no pin 422m Meshtastic e9dc 3815m Home One no pin 24527m Meshtastic f540 no pin 26969m

Who heard it

Last 24 hours, plus 3 direct link(s) heard earlier.

This node is a gateway. It has received 1 node(s) itself (4 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Home Two both ways 330 RF 0 9.2 dB … 4.8 5 11 min ago
!617b46f7 heard by this node 148 RF 0–1 12.0 dB … 8.2 4 7h 2m ago
Meshtastic e9dc heard by this node 4 RF — 9.5 dB … 7.8 — 2d 15h ago
Home One heard by this node 25 RF 0 11.2 dB … 9.0 5 17d 0h ago
Meshtastic f540 73 RF 0 7.5 dB … 5.5 5 18d 17h ago
Reading the hop budget. Every Meshtastic frame carries a hop limit that each relay decrements. A reception showing 0 left is one that arrived with nothing to spare — one more relay in the path and it would not have arrived at all. That is the closest this data comes to explaining a loss, and it is still not a loss: a frame that was dropped is exactly the one that never reached a gateway to be counted here.