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

Beanfield Roof

!f11fec37 · updates every minute

80% 3.99 V · just now

6 max hops — This station sets its traffic to be rebroadcast up to 6 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 7 days Nov 9 to Nov 15 · 7 active days · 725 RF frames · 21 gateways

Nov 9 Nov 15

Most recent

david79-uconsole 0m Parrish Gateway 0m K4EX_MQTT 120m ViVSoft.live MQTT Gateway 150m Beanfield 🐊 flme.sh 690m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Parrish Gateway 537 RF — 9.5 dB … 1.5 — 0 min ago
Beanfield 🐊 flme.sh 47 RF — 8.0 dB … 1.5 — 11h 30m ago
Moka 2 RF — -16.8 dB — 3d 2h ago
david79-uconsole 27 RF — relayed — not attributable — 0 min ago
K4EX_MQTT 1 RF — relayed — not attributable — 2h 0m ago
ViVSoft.live MQTT Gateway 6 RF — relayed — not attributable — 2h 30m 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.