Article
Meshtastic in Europe: What the Duty Cycle Really Changes
An off-grid messaging mesh for a few dozen euros. But European regulation imposes a limit American content never mentions, and it changes how you must size your network.
A box the size of a cigarette pack, an antenna, a battery. It sends text messages several kilometres, with no carrier, no SIM card, no internet, and every box relays everyone else's. That's Meshtastic, and it's the most interesting civilian communication project of the decade.
It's also where the gap between video promises and European reality is widest. There's a precise reason: the regulation governing the European band has no equivalent in the United States, where most of the content comes from. This article covers what that difference changes in practice, the ranges actually observed, and the limits you need to know before building a communication plan on it.
What it is, in one minute
Meshtastic is open-source software running on cheap LoRa radio boards. Each device (a node) connects to a phone over Bluetooth and exchanges text messages and positions with other nodes in range. What creates the value: every node relays the messages it receives, extending coverage beyond the reach of any single device.
A distinction that matters below: LoRa is the radio layer, the modulation. Meshtastic is the mesh protocol running on top of it. Saying "I use LoRa" is as vague as saying "I use Wi-Fi" without specifying for what.
Four items suffice: a compatible board, an antenna tuned to the right band, a battery, a phone. Budget roughly €40 to €100 per node depending on the model.
Something vendors leave out: a single node is useless. You need two minimum, and the system's value grows with the number of participants around you.
The duty cycle: the European constraint nobody mentions
Here is the difference that invalidates part of the English-language content.
In Europe, Meshtastic uses the 868 MHz band, specifically 869.4 to 869.65 MHz in the EU_868 configuration, with a centre frequency of 869.525 MHz for the default preset. That slice of spectrum is licence-free, but it is subject to a 10% duty cycle limit, calculated over a rolling one-hour window.
In plain terms: about six minutes of transmission per hour, no more. The Meshtastic firmware enforces this itself: the device stops transmitting once the threshold is reached and waits until it's allowed again.
In the United States, the equivalent band around 915 MHz has no such constraint. That's why American demonstrations show chatty networks, positions sent every minute, and dozens of nodes replying continuously. Reproducing that configuration in Europe produces a network that gags itself.
What consumes your transmission budget, and is systematically underestimated:
- the messages you send, obviously;
- the ones you relay for others: that's the very nature of a mesh;
- periodic position beacons;
- telemetry (battery, sensors);
- acknowledgements.
A well-placed fixed node relaying traffic for a whole neighbourhood hits the limit far sooner than an individual node in a pocket. That's the system's paradox: the nodes most useful to the network are the first ones silenced.
The practical consequences, and they drive all your sizing:
- Space out position beacons. Every fifteen minutes is enough for most uses; every minute is an American luxury.
- Disable telemetry you have no use for.
- Limit the hop count. The maximum is seven, the default is three, and every extra hop multiplies the airtime consumed across the whole network.
- A dense network isn't a performant one. Past a certain number of active nodes in one area, collisions and duty cycle degrade the service for everyone.
A legal trap worth flagging, because it concerns licensed readers directly: operating on 868 MHz is not amateur radio. It's licence-exempt spectrum with strict technical conditions. Your callsign grants you no privileges on that band, and short-range-device rules apply in full. It's the exact counterpart of what we wrote about the Baofeng and PMR446: every transmitted packet belongs to a legal framework.
Real ranges, without the records
This is the second source of disappointment. The community record exceeds 300 km ground-to-ground, achieved peak to peak, in clear line of sight, with high-gain directional antennas. That figure circulates everywhere and has no predictive value for your use.
The orders of magnitude actually observed:
| Context | Range between two nodes |
|---|---|
| Dense urban, nodes at head height | 0.5 to 2 km, sometimes less |
| Urban / suburban, one node elevated | 1 to 5 km |
| Clear line of sight, rural | 10 to 15 km and beyond |
| Peak to peak, directional antennas | tens of kilometres |
What makes the difference, in order: antenna height, far ahead of everything else. Raising an antenna by five metres can double your range. Then antenna quality and tuning. Only then, the rest. Transmit power comes far behind, as always in radio, and as we already wrote about handheld sets.
Practical corollary: a node in a backpack, in a city, communicates poorly. A functional urban network requires fixed nodes placed high: a roof, an elevated balcony, a high point. That discreet infrastructure is what keeps big-city networks alive, not the devices people carry.
What Meshtastic doesn't do
No voice, no images. Throughput is on the order of a few hundred bits per second. Short text and positions, nothing else. That's a physical constraint, not a software limitation.
The default channel isn't private. The public preset uses a key shared by everyone: any device in range can read what passes through it. For real use you must create a channel with your own key and share it out of band with your contacts. It's the most widespread configuration error, and the most consequential for anyone who believes they're protected.
It isn't a real-time system. A message can take tens of seconds to cross a multi-hop mesh, or never arrive if a relay is saturated or offline. Meshtastic is asynchronous messaging and should be treated as such.
It isn't a guaranteed service. No operator, no supervision, no obligation of result. That's precisely what makes it an interesting backup and an unacceptable primary.
In the vocabulary of the PACE plan we use elsewhere, Meshtastic is an excellent C (contingency): it works without infrastructure. It replaces neither your primary nor your emergency means.
Where to actually start
- Two nodes minimum, never one. A T-Beam, a Heltec or equivalent, around €40 to €100 each. Flashing takes a few minutes from a browser.
- Select the EU_868 region, and verify it: that setting is what applies the duty cycle limit and the correct band. A board configured for a US region transmits outside the frame.
- Keep the LongFast preset at first. It's the best range/airtime compromise, and it's what others around you are using: a different preset isolates you from the existing network.
- Create a private channel with your own key before any serious use, and hand it over in person.
- Look for the local network before buying. In several European cities, fixed nodes already exist. Joining a live mesh changes everything; starting alone in an empty area gives you two devices talking to each other.
- Test before you need it. Record the ranges you actually observe from your usual locations: that's exactly what the radio memo sheet in our library is for.
Conclusion
Meshtastic delivers a rare promise: communicating with no carrier, no subscription and no infrastructure, for the price of a dinner. That promise is real, and it earns the place it holds in resilience discussions.
But in Europe it operates within a frame imported content ignores: six minutes of transmission per hour, urban ranges on the order of a kilometre, a default channel readable by all, and a band that isn't amateur radio. A network designed around those four points works. A network designed from an American video disappoints, and its owner concludes the technology doesn't work.
Configure for the duty cycle. Raise the antenna. Encrypt your channel. Test beforehand.
Companion sheet: Download the printable A4 PDF
Sources and further reading
- Meshtastic: LoRa Configuration. Official documentation: 10% limit on EU_433 and EU_868, rolling one-hour calculation, presets and hop count.
- Meshtastic: Radio Settings: bands, frequencies by region and the LongFast preset.
- RF.Guru: Meshtastic, MeshCore, 868 MHz and the Ham Radio Trap: why 868/869 MHz licence-exempt spectrum isn't amateur radio, and what 10% duty cycle means in practice.
- Meshtastic Range Guide (2026): realistic ranges by terrain, the importance of antenna height, and the 331 km record under exceptional conditions.
- Complete Beginner's Guide to Meshtastic (2026): required hardware, throughput limits and the unencrypted public channel.
- Meshtastic vs MeshCore in 2026: comparative analysis of airtime load by network architecture.