Introducing MeshCore
Looking for a new mesh project to tinker with? Check out MeshCore

Meshtastic Map

Created by Liam Cottle

Improved by PBA

👋 Welcome to my open source map of Meshtastic nodes heard on MQTT.
Features
  • The map shows nodes that have sent a valid position to MQTT.
  • Position packets must be unencrypted, or encrypted with the default key.
  • Use the search bar to find nodes by ID or name.
  • Hover over nodes (on desktop) to see basic details.
  • Click a node to see info such as telemetry graphs and traceroutes.
  • Use the top right layers panel to show neighbours and waypoints.
  • Use the settings button to configure the map to your liking.
  • Have a feature request, or found a bug? Open an issue on GitHub.
FAQ
How do I add my node to the map?
Your node, or a node that hears your node must uplink to our MQTT server.
Your position packet must be unencrypted, or encrypted with the default key.
If your node has v2.5 firmware or newer, you must enable "OK to MQTT".
Use the MQTT server details below to uplink to this map.
What MQTT server should I use?
  • Address: mqtt.meshmap.ro
  • Username: meshdev
  • Password: large4cats
  • Encryption Enabled: Yes
  • JSON Output: No
  • TLS Enabled: No
Please note, nodes can only uplink to this server. Downlink is disabled.
We suggest running dedicated nodes for uplinking to the map.
How do I remove my node from the map?
Nodes that have not been heard for 7 days are automatically removed.
Disable position reporting in your node to prevent it coming back.
Use custom encryption keys so the public can't see your position data.
If your node has v2.5 firmware or newer, we ignore packets if "OK to MQTT" is disabled.
To remove your node immediately, send the text message /remove_me from your node on any channel that is gated to this MQTT server. The node row is reset and flagged as removed so it stays off the map.
To re-enable the node later, send /add_me from the same node.
How do I see neighbours a node heard?
Open the top right layers panel and enable neighbours.
Some neighbours are from MQTT, this is patched in latest firmware.
Why is my node showing up in the wrong place?
If your node has reported its real GPS position with "OK to MQTT" enabled, it is shown at the reported coordinates with the precision your firmware advertises.
Older firmware (v2.4 and below) does not include precision flags; for those packets we round positions to a configured number of decimal places.
Positions captured passively (when "OK to MQTT" is off) are obfuscated for privacy:
  • ~300 m random jitter for normal nodes,
  • ~50 m for nodes whose role is set to TRACKER.
If your node has never reported a position, the map tries to estimate one and marks it as triangulated (triangle marker with a "?" overlay):
  • SNR-based trilateration from at least 3 neighbours that heard your node, when available;
  • otherwise the centroid of the topic gateway position, with a small deterministic ring offset so multiple nodes sharing one gateway don't stack on top of each other.
As soon as your node sends its own real position, the estimate is replaced and the triangle becomes a regular dot.
Legal
This project is not affiliated with or endorsed by the Meshtastic project.
The Meshtastic logo is the trademark of Meshtastic LLC.
Map tiles provided by OpenStreetMap