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

Florida mesh

Which gateways heard which Meshtastic nodes, and how well. Click a pin to see who received it, from how many hops away, and how much hop budget was left when the frame arrived. Only nodes that publish a map report get a pin — that is an opt-in on the radio, and most nodes do not enable it, so the map is always a small subset of the mesh that is actually out there.

193nodes heard (1h)
74receiving gateways
35publish a position
35mapped this hour
469RF frames (1h)
0MQTT frames (1h)
heard in the last hour heard in the last day blurred position — the circle is where it could be

Basemap detail ends at zoom 13; you can zoom 17 to separate close pins, but no new map detail appears past 14.

What this can and cannot tell you. Every frame counted here is one that arrived. A packet that was dropped is exactly the packet that is missing from the data, so this page can show that a node's traffic habitually arrives with no hop budget left — a reason frames would be lost — and can never show a loss itself. Signal readings describe the last hop only: a relayed frame's SNR is a fact about the relay that carried it, not about the node that sent it, so only a direct (0-hop) reception is attributed. Absence of a node means only that no participating gateway heard it — not that it is off the air.