Meshtastic range has no fixed number: it can be very short through buildings or more than 100 miles between mountaintops, and the biggest factors are line of sight, antenna height, terrain, and the modem preset. The official documentation lists a 331 km (205 mile) ground-to-ground record, set between two elevated sites with outdoor antennas and a very slow radio setting.
This guide summarizes what the Meshtastic docs say about range and explains the physics in plain terms. LoRa Mesh Atlas has no test lab and hasn’t run its own range tests. To estimate a specific link, try our radio horizon and Fresnel zone calculator.
Documented range records
The Meshtastic Range Tests page lists community records, with the settings used:
| Record | Distance | Settings listed | Notes |
|---|---|---|---|
| Current ground-to-ground | 331 km (205 mi) | 868 MHz, 62.5 kHz bandwidth, SF12, CR 4/8 (“Very Long Slow”) | Two fixed nodes with external antennas, including a 55 cm collinear |
| Previous ground record | 254 km (158 mi) | 915 MHz, Long Fast (250 kHz, SF11), CR listed as 4/8 | 5.8 dBi outdoor antenna on one end |
| Earlier ground record | 166 km (103 mi) | 868 MHz, 125 kHz, SF12, CR 4/8 | 5 and 6 dBi antennas |
| Ground-to-air | 206 km (128 mi) | 915 MHz, Long Fast | One node carried by a balloon, stock antennas |
Two things stand out. The 331 km record was mountain to mountain and the air record used a balloon, and two of the three ground records used settings slower than the default. Note that the “Very Long Slow” preset used for the 331 km record is not among the general-purpose presets the Radio Settings page lists today; it would be a custom setting on current firmware. These are records, not expectations.
Why line of sight matters most
LoRa at 915 MHz travels best when the two antennas can “see” each other. Hills, buildings, and dense trees block or weaken the signal. The Meshtastic docs reflect this throughout:
- The antenna selection page notes that buildings and walls attenuate signal, while people don’t attenuate it greatly at LoRa frequencies.
- The device roles blog post describes a strategic location as “a tower on mountain peak rather than a tall building,” and recommends line-of-sight viewshed survey tools.
- The Site Planner docs model coverage using terrain elevation data.
Radio horizon
Because the earth curves, even a perfectly clear path ends at the radio horizon. Raising either antenna pushes that horizon out. This is why a node on a roof or hilltop often reaches dramatically farther than the same node at ground level. Our range calculator computes the radio horizon for any two antenna heights.
Fresnel zone
A clear straight line between antennas isn’t quite enough. Radio energy travels in a football-shaped region around that line, called the Fresnel zone. Ground, trees, or roofs intruding into it weaken the link even if you can see the other site. The zone is widest at the midpoint, so long links need height to keep it clear. The calculator shows the Fresnel zone radius for a given distance and frequency.
Antennas and placement
From the official antenna selection page:
- Stock antennas vary. Antennas bundled with boards “usually come from ‘mixed bags’” and may not be tuned for your frequency.
- Match the frequency. For US use, choose an antenna made for the 902–928 MHz band, 50 ohm, with the right connector (often SMA).
- Cable loss is real. “Most cables will significantly degrade the signal strength over any significant distance. It is often more effective to place a node outside than to have it indoors with the antenna outside.”
- Directional vs. omni. A directional antenna reaches farther but must be aimed, so it’s not ideal for mobile use.
- Ground planes. Many antennas, especially quarter-wave stubbies, need a ground plane to perform well.
- Never transmit without an antenna. Signals can reflect back and damage the radio.
In the US, antenna gain also has a legal dimension. See is Meshtastic legal in the USA for how FCC Part 15 treats antennas above 6 dBi.
How modem presets affect range
Meshtastic bundles bandwidth, spreading factor, and coding rate into modem presets. According to the Radio Settings page:
- Each step up in spreading factor doubles airtime and adds about 2.5 dB of link budget.
- Each doubling of bandwidth costs almost 3 dB of link budget.
- Data rate is “inversely proportional to the theoretical range.”
The docs list link budgets (calculated at 22 dBm transmit power and a 0 dBi antenna) from 140 dB for Short Turbo up to 156 dB for Long Moderate. Long Fast, the long-standing default, is 153 dB.
More link budget usually means more range, but there’s a trade-off. Slower presets keep each packet on the air longer, which congests busy meshes. The Meshtastic blog post Is LongFast Holding Your Mesh Back? describes a New Zealand mesh that moved to the faster Short Fast preset and reported that all but a few very marginal links kept working, including a 254 km link between two high sites. Height and line of sight did much of the work there.
Most important: all nodes must share a preset to hear each other at all. A slower preset won’t help you reach a mesh running a different one.
Hops extend reach
Meshtastic is a mesh, so range isn’t just one link. Each relay can carry a message farther, up to the hop limit. The LoRa configuration page sets the default at 3 and the maximum at 7, with the note “Really, 3 is fine.” The tips page adds that unnecessarily high hop counts often cause network problems, and if you must raise it, do so only on nodes at the network’s edges.
Well-placed infrastructure helps too, but the docs warn that poorly placed ROUTER nodes can reduce range by using up hops early. See Meshtastic roles explained.
Transmit power and receive gain
The LoRa config’s transmit power setting defaults to 0, meaning “use default max legal continuous power,” and the docs advise leaving it there in most cases. Some SX126x-based radios also offer “RX boosted gain,” which uses a little more power to improve receive sensitivity. Higher power alone doesn’t fix a blocked path.
Measuring and predicting your own range
- Predict before you climb. The official Meshtastic Site Planner (site.meshtastic.org) produces a coverage map from terrain data. Its docs note the terrain data is accurate to about 90 meters and doesn’t account for buildings or trees, so verify with real-world testing.
- Quick geometry checks. Our range tool estimates radio horizon and Fresnel clearance.
- Field test. Meshtastic includes a Range Test module: a fixed sender transmits sequential packets every 30–60 seconds, and a mobile receiver can save them with GPS coordinates to a .csv file. The docs warn it uses a lot of airtime, so turn it off when done (it shuts off automatically after 8 hours).
- Test before installing. The tips page advises testing settings and hardware before putting a node in a hard-to-reach spot.
Realistic expectations
The docs don’t give “typical” distances, and we won’t invent one. What they do show is consistent: elevated, clear paths with decent antennas produce long links, while ground-level, obstructed paths produce short ones. If you’re starting out, getting at least one node up high and outdoors, keeping the default hop limit, and matching your local mesh’s preset will usually matter more than any single hardware choice. Browse /devices/ or use the finder for hardware with external antenna connectors.
Frequently asked questions
How far can Meshtastic reach?
There is no single number. Range depends mostly on line of sight, antenna height and quality, terrain, and the modem preset. The official docs list a 331 km ground-to-ground record between two mountain sites, which is far beyond typical handheld use.
What is the Meshtastic range record?
The Meshtastic docs list a 331 km (205 mile) ground-to-ground record using a slow 62.5 kHz, SF12 setting at 868 MHz, and a 206 km ground-to-air record with one node carried by a balloon, on the Long Fast preset at 915 MHz.
Does a slower preset increase Meshtastic range?
Generally yes. Per the docs, each step up in spreading factor adds about 2.5 dB of link budget but doubles airtime, and halving bandwidth adds almost 3 dB. Slower presets cost airtime, which matters on busy meshes.
Do hops extend Meshtastic range?
Yes. Each node that relays a message can carry it farther, up to the hop limit (default 3, maximum 7). The docs strongly recommend leaving the hop limit at 3.
Sources
- Meshtastic Docs: Range Tests (records)
- Meshtastic Docs: Radio Settings (presets and link budget)
- Meshtastic Docs: LoRa Configuration
- Meshtastic Docs: Meshtastic Site Planner
- Meshtastic Docs: LoRa Antenna Selection
- Meshtastic Docs: Configuration Tips
- Meshtastic Docs: Range Test Module
- Meshtastic Blog: Is LongFast Holding Your Mesh Back?
- Meshtastic Blog: Choosing The Right Device Role
Found an error? Send a correction and we'll check it against the source.