Meshtastic Map: How to Find Nodes and Meshes Near You

To find Meshtastic nodes near you, start with the official Local Groups directory and the Local Mesh Discovery scan built into the Android and Apple apps, then use online node maps as a rough guide. Online maps only show nodes whose data reaches the internet through MQTT, so an empty map doesn’t mean nobody’s there, and a busy map doesn’t tell you which radio settings the locals use.

This guide is based on the official Meshtastic documentation, including Joining your local mesh. LoRa Mesh Atlas is independent of the Meshtastic project and doesn’t run its own node map.

Step 1: Check the official Local Groups directory

The Meshtastic docs maintain a Local Groups page listing “groups that have been actively organizing Meshtastic networks in their regions.” The US section is organized by state and includes Discord servers, Reddit communities, and websites. As of this writing it has more than 100 US entries across dozens of states plus Washington, DC, and Puerto Rico.

Why start here: the joining guide says “regional groups publish their settings to people joining, which is how to find a mesh a scan cannot see.” That matters because many communities use a non-default preset or their own channel.

A couple of notes from the page itself:

• Groups may not use “Meshtastic [Your City Here]” as their name, to avoid implying official sponsorship. So search the list by state, not by “Meshtastic + city.”
• Group organizers add themselves by editing the page, so coverage is uneven. No listing for your area doesn’t mean no mesh.

Step 2: Scan with Local Mesh Discovery

The Android and Apple apps include Local Mesh Discovery. Per the Android docs, it “cycles your connected node through one or more presets you choose, dwells on each one — listens for a set time — to collect packets, then analyzes and ranks the results.” Dwell times range from 1 to 180 minutes per preset. On Android it’s under Settings → Advanced → Local Mesh Discovery.

What it can and can’t see, per the joining guide:

• It listens on each preset’s default frequency slot with the default public channel.
• A mesh whose primary channel has a custom name sits on a different slot, and one with a custom key can’t be decoded, so neither appears.
• “An empty result means nothing is running on the public channel nearby, not that nothing is running.”

The scan temporarily changes your node’s LoRa settings and restores them afterward.

Step 3: Match your settings

Once you know what’s in use, set your region (US), then match the modem preset. If the group uses its own channel, add it from their shared URL or QR code, which carries the channel name, key, and LoRa settings together.

Two settings traps the docs highlight:

• Long Fast vs. Long Turbo. Starting with firmware 2.8 (an alpha release as of October 2026), a US node whose region is first set on the device screen starts on Long Turbo, while setting it from an app leaves it on Long Fast. Those nodes “can’t hear each other” and sit nearly 2 MHz apart (finding your local mesh).
• Don’t rename the primary channel. Its name sets your frequency slot, so renaming it moves you off the shared slot. Use secondary channels for private groups.

See Meshtastic modem presets for details.

Confirm you’re connected

The docs recommend testing with a direct message, because only the recipient’s acknowledgment confirms delivery. A channel message counts as delivered as soon as any one nearby node repeats it, even if nobody beyond that node receives it.

Also note that your node list remembers nodes heard on previous settings. Firmware 2.8.1 and later (alpha as of October 2026) marks nodes not heard on your current settings; older firmware shows them as if they were still reachable.

Step 4: Use online node maps, with caveats

Where maps get their data

Online Meshtastic maps are built from MQTT data, not from the radio mesh directly:

• Map reports. When a node has MQTT and map reporting enabled, it periodically publishes an unencrypted report with its names, ID, position (at configurable precision), hardware model, role, firmware version, region, modem preset, primary channel name, and count of local online nodes (MQTT module).
• Uplinked packets. Gateways uplink position and NodeInfo packets they hear to an MQTT broker. On the project’s public server with the default key, only imprecise positions (10–16 bits of precision) are passed (MQTT integrations).

The official Android docs say map reports “appear at meshmap.net and similar community map services” (Android MQTT). That’s the only map site we found named in the official Meshtastic docs; it’s described there as a community service, not one run by the project.

Limits of online maps

• Most nodes aren’t on them. A node only appears if its data reaches an MQTT server: either it reports itself, or a nearby gateway uplinks its packets (and, on the default channel, the node has OK to MQTT enabled). Nodes without internet nearby are invisible.
• Locations are approximate. Default map-report precision is a maximum deviation of about 1,459 m, and the public server filters precise positions.
• They may be stale. Map reports are sent at most once an hour by default, and maps vary in how long they keep old entries.
• They don’t tell you the preset unless the map displays map-report details. Ask the local group.
• Regional scope. Since August 2024, the project’s public MQTT server no longer allows subscribing to all topics; maps and tools use regional topics such as msh/US/# (MQTT broker changes).

Privacy before you add yourself

The project restricted its public MQTT server in 2024 after observing “that public mesh maps were now storing and, in some cases, tracking node positions over time,” and that many users weren’t aware their position was being shared online. The tips page warns that connecting a node to the public MQTT server may publish the locations of all nodes in your mesh. In the Android app, turning on map reporting opens a consent card and requires a publish interval of one hour or more, with a precision slider. See Meshtastic MQTT and Meshtastic privacy.

The in-app map

The Meshtastic apps also include a map of nodes in your node’s database that report a position (Android Map & Waypoints). If your node uses MQTT, that can include nodes heard over the internet; the Android map has filters such as Only show direct nodes and Exclude MQTT to narrow it to what your radio actually heard. Filtered that way, it’s the most direct picture of who is in radio range, but it only includes nodes that share location on a channel you have.

MeshCore users

MeshCore is a separate system with its own map. The MeshCore FAQ links the MeshCore Map and explains how to add a companion, repeater, or room server to it from the MeshCore app (MeshCore FAQ). MeshCore and Meshtastic nodes can’t communicate, so check which system your local group runs. See Meshtastic vs MeshCore.

If there’s nobody near you

The joining guide notes that “if nobody has confirmed a mesh in your area, silence on its own says very little.” You can start one: two radios on matching settings form a mesh, and one node placed high and outdoors helps the most. See what is Meshtastic, the range guide, and /devices/ or the finder for hardware.