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

Meshtastic c288

!433ac288 · updates every minute

97% 4.15 V · 19 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.

4 max hops — This station sets its traffic to be rebroadcast up to 4 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 · 1177 RF frames · 26 gateways

Sep 15 Nov 15

Most recent

david79-uconsole 113m Parrish Gateway 473m ViVSoft.live MQTT Gateway 473m Meshtastic f79e 8240m Earl1 34314m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic f79e 3 RF — -12.8 dB … -16.0 — 5d 17h ago
Earl1 2 RF — -21.2 dB — 23d 19h ago
david79-uconsole 6 RF — relayed — not attributable — 1h 53m ago
Parrish Gateway 2 RF — relayed — not attributable — 7h 53m ago
ViVSoft.live MQTT Gateway 3 RF — relayed — not attributable — 7h 53m 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.