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

Meshtastic revS

!9857107c · updates every minute

95% 4.11 V · 22 h ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

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.

History

Heard on 62 days Sep 15 to Nov 15 · 62 active days · 1479 RF frames · 30 gateways

Sep 15 Nov 15

Most recent

Wild Reset MQTT no pin 92m TTB Base ed94 92m Mandarin a37e💥 170m !9e766638 no pin 363m BenClient 946m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Wild Reset MQTT 1 RF — relayed — not attributable — 1h 32m ago
TTB Base ed94 2 RF — relayed — not attributable — 1h 32m ago
Mandarin a37e💥 4 RF — relayed — not attributable — 2h 50m ago
!9e766638 1 RF — relayed — not attributable — 6h 3m ago
BenClient 1 RF — relayed — not attributable — 15h 46m 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.