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

Pi3 MeshtasticD

!ebfc74d6 · updates every minute

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

Silent for 48d 19h Sep 22 to Sep 28 · 4 active days · 6 RF frames · 1 gateway

Sep 22 Nov 16

Most recent

TreeTop Solar Alfa 2m Meshtastic 75f5 7m KE4CQE portable 16m DaMeshMode3 no pin 34m Jurrd Ethernet Bridge Node no pin 36m

Who heard it

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

This node is a gateway. It has received 23 node(s) itself (308 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
TreeTop Solar Alfa heard by this node 5453 RF — 8.2 dB … 5.2 — 2 min ago
Avali Ship heard by this node 4 RF 0–1 -20.2 dB 3 11d 15h ago
!b1f525ba heard by this node 1 RF 0 3.8 dB 3 16d 17h ago
!2844753d heard by this node 5 RF 0 5.5 dB … 4.2 3 25d 21h ago
Meshtastic 75f5 heard by this node 19 RF — relayed — not attributable — 7 min ago
KE4CQE portable heard by this node 18 RF — relayed — not attributable — 16 min ago
DaMeshMode3 heard by this node 1 RF — relayed — not attributable — 34 min ago
Jurrd Ethernet Bridge Node heard by this node 4 RF — relayed — not attributable — 36 min ago
SunrisePlazaStation heard by this node 1 RF — relayed — not attributable — 1h 5m ago
4FTx Tastic heard by this node 21 RF — relayed — not attributable — 1h 18m ago
HorizonWestOrange Solar/Tree by KE4CQE heard by this node 3 RF — relayed — not attributable — 2h 20m ago
DMM Solar Node heard by this node 4 RF 2 relayed — not attributable 5 3h 50m ago
Meshtastic b1d1 heard by this node 20 RF — relayed — not attributable — 4h 42m ago
Lone Pine 2 EC8F heard by this node 1 RF — relayed — not attributable — 5h 15m ago
H&C HQ 9b18 heard by this node 5 RF — relayed — not attributable — 7h 38m ago
W⚓ heard by this node 2 RF — relayed — not attributable — 7h 50m ago
!11b3b4f5 heard by this node 1 RF 2 relayed — not attributable 2 8h 47m ago
Meshtastic 2c63 heard by this node 2 RF — relayed — not attributable — 9h 7m ago
!bd468190 heard by this node 1 RF — hop distance not reported — 9h 17m ago
!fec1534f heard by this node 1 RF 2 relayed — not attributable 2 10h 47m ago
Ocoee Solar heard by this node 2 RF — relayed — not attributable — 12h 22m ago
👽 BUZZ BASE LAUNCH FACILITY SOLAR heard by this node 1 RF — relayed — not attributable — 13h 53m ago
d3fm0nk3y heard by this node 1 RF — relayed — not attributable — 14h 5m ago
Meshtastic e522 heard by this node 3 RF — relayed — not attributable — 15h 10m ago
!33691a2c heard by this node 1 RF — relayed — not attributable — 16h 44m ago
!43b78c3c heard by this node 1 RF — relayed — not attributable — 19h 50m 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.