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

Meshtastic 32804

!6d244631 · updates every minute

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

History

Heard on 6 days Nov 2 to Nov 14 · 6 active days · 27 RF frames · 2 gateways

Nov 2 Nov 15

Most recent

Meshtastic 0690 no pin 1174m W⚓ 1192m AW-Node-03 1195m JT HeltecV4 (MQTT) 1198m College Park Meshtastic 1e53 1235m

Who heard it

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

This node is a gateway. It has received 5 node(s) itself (23 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
Meshtastic 0690 heard by this node 47 RF — 7.5 dB … 5.8 — 19h 34m ago
College Park Meshtastic 1e53 heard by this node 25 RF — 8.0 dB … 5.8 — 20h 35m ago
Solar Node 9e5b both ways 33 RF — -9.0 dB … -18.2 — 10d 20h ago
Meshtastic 9a93 heard by this node 11 RF — 5.0 dB … -8.8 — 10d 22h ago
Meshtastic 7a78 heard by this node 3 RF — 0.8 dB … -8.2 — 11d 7h ago
W⚓ heard by this node 19 RF — relayed — not attributable — 19h 52m ago
AW-Node-03 heard by this node 1 RF — relayed — not attributable — 19h 55m ago
JT HeltecV4 (MQTT) 1 RF — relayed — not attributable — 19h 58m ago
EL Attic heard by this node 1 RF — relayed — not attributable — 20h 43m 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.