UK settings at a glance
| Region | EU_868 |
|---|---|
| Default preset | LongFast: 250 kHz, SF11, CR 4/5 |
| Frequency | 869.525 MHz (the band only has room for one 250 kHz slot) |
| Power limit | 500 mW ERP. The firmware caps output at 27 dBm |
| Airtime limit | 10% an hour, enforced by the firmware |
| Licence needed | No |
Your region, preset and channel must match the people you want to reach. LongFast is the default, so it's what most nodes use, but a busy area may have moved to a faster preset. Check the local mesh before changing yours.
Is Meshtastic legal in the UK?
Yes, without a licence. Meshtastic's EU_868 region uses 869.40 to 869.65 MHz, which Ofcom's IR 2030 (entry IR2030/1/19) allows for any short-range device at up to 500 mW ERP and a 10% duty cycle, unless it uses listen-before-talk techniques as good as those in the EN 300 220 standard.
The duty cycle is looked after for you. In EU_868, the firmware counts your airtime over a rolling hour and stops transmitting when you reach 10%. There's an Override duty cycle setting: leave it off, as turning it on takes you outside the rules.
The power cap isn't. The firmware limits the radio's output to 27 dBm, which is 500 mW at the radio, but Ofcom's limit is on radiated power, so the antenna counts. Into a 5 dBi antenna, 27 dBm is about 1 W ERP. Most boards only reach 22 dBm, which is legal into a small whip, but a booster board or a high-gain antenna can take you over. Leaving TX power at 0 uses the board's own maximum, so set it yourself and use the checker.
Which preset?
The band has room for only one 250 kHz slot, so every 250 kHz preset sits on 869.525 MHz, and the preset is what separates meshes. LongModerate, at 125 kHz, gets two slots and by default uses 869.4625 MHz. All the nodes you want to talk to must use the same preset.
| Preset | Bandwidth (kHz) | SF | CR | Data rate | Link budget | Best for |
|---|---|---|---|---|---|---|
| ShortTurbo | 500 | 7 | 4/5 | 21.9 kbps | 140 dB | US only. Too wide for the UK band |
| ShortFast | 250 | 7 | 4/5 | 10.9 kbps | 143 dB | Very busy city meshes |
| ShortSlow | 250 | 8 | 4/5 | 6.25 kbps | 145.5 dB | Busy meshes |
| MediumFast | 250 | 9 | 4/5 | 3.52 kbps | 148 dB | Busy suburban meshes |
| MediumSlow | 250 | 10 | 4/5 | 1.95 kbps | 150.5 dB | Busy suburban meshes |
| LongTurbo | 500 | 11 | 4/8 | 1.34 kbps | 150 dB | US only. New US default in 2.8 |
| LongFast | 250 | 11 | 4/5 | 1.07 kbps | 153 dB | The default. Quiet and rural meshes |
| LongModerate | 125 | 11 | 4/8 | 0.34 kbps | 156 dB | Very long, quiet links |
Link budgets are Meshtastic's figures at 22 dBm with a 0 dBi antenna. Firmware 2.8, still in alpha, adds more presets, including Medium Turbo and the very narrow Tiny Fast and Tiny Slow. The 500 kHz Turbo presets are wider than the UK band, so don't use them here. In April 2025 the Meshtastic developers recommended that busy meshes, with more than about 60 nodes in range of each other, move off LongFast to a Medium or Short preset. Faster presets lose a little range, but each message is on air for much less time, so more people can use the channel and the 10% goes further.
MeshCore and Meshtastic share the band
LongFast is exactly as wide as Ofcom's band, so it shares the airwaves with MeshCore on 869.618 MHz. The two systems can't read each other's messages, but they do get in each other's way. See Meshtastic vs MeshCore for how the two compare.
What about 433 MHz?
Meshtastic's EU_433 region also works in the UK, licence-free, under IR2030/1/10: 433.05 to 434.79 MHz at 10 mW ERP with a 10% duty cycle. That's a twentieth of the 868 MHz power, so range is much shorter. The firmware caps EU_433 at 10 dBm, which goes over 10 mW ERP into anything with more gain than a dipole. Meshtastic's lowest 433 MHz slot starts at 433.0 MHz, below the UK band, so use the default slot (433.875 MHz) or one of the two between. Fewer people use 433 MHz, so check there's a local mesh first.
Licensed amateurs
If you hold a UK amateur licence, you can use Meshtastic's licensed mode on the 70 cm band, with the power your licence allows. Your licence bans messages encrypted to hide their meaning, so licensed mode turns encryption off and sends your callsign. Licensed nodes can't read encrypted traffic, so they can't fully take part in an ordinary encrypted mesh. Firmware 2.8 adds amateur regions for 2 m and 70 cm, and signs messages instead of encrypting them.
Getting on air
- Get an 868 MHz board that Meshtastic supports. The web flasher lists them. Fit the antenna before powering it up.
- Flash the firmware from the web flasher in Chrome or Edge, choosing your board and a stable release. Many boards come with Meshtastic already installed.
- Install the Meshtastic app (Android, iPhone or web) and pair over Bluetooth. Screens show the PIN; screenless boards default to 123456.
- Set the region to EU_868. A new node won't transmit until you do. Leave the preset on LongFast unless your local mesh uses another.
- Set the TX power using the checker, and decide on position sharing.
- Say hello on the default channel, and look at the node list to see who's in range.
How Meshtastic passes messages on
Meshtastic uses managed flooding. Unlike MeshCore, every node relays by default, handhelds included. Before passing a message on, a node waits a moment; if it hears another node relay it first, it stays quiet. Nodes that heard the message weakly wait less, so the most distant ones tend to relay first. Each relay lowers the message's hop limit, which starts at 3 and can be set as high as 7. At 0, nobody passes it on.
Direct messages start the same way. Since firmware 2.6, once a reply comes back, the nodes on the way learn the next hop towards each other, and only that node relays later messages. If it goes quiet, the sender falls back to flooding on its last retry.
What a node does is set by its role:
| Role | Relays others' messages? | Use it for |
|---|---|---|
| CLIENT (default) | Yes, unless another node already has | A handheld or home node |
| CLIENT_MUTE | No | A second node near another of yours, or a busy area |
| CLIENT_BASE | Yes, favouring your own nodes | A home base station that helps your handhelds |
| ROUTER | Always | A well-sited fixed node agreed with your local mesh |
| ROUTER_LATE | Always, after everyone else | Filling a local dead spot |
| TRACKER, SENSOR | Only while awake | Sending positions or sensor readings |
Don't set a handheld or a home node to ROUTER. Badly placed routers relay everything, use up airtime and drain batteries. Talk to your local mesh first.
Channels and privacy
- The default channel (named after the preset, such as LongFast) uses a key everyone knows,
AQ==, so anyone can read it. - Private channels use a key you generate and share by QR code or link. Anyone with it can read the channel. Messages are encrypted with AES; firmware 2.8 adds an option to detect tampering, which every node on the channel has to turn on.
- Direct messages are encrypted with keys only the two nodes can work out, using each node's public and private key.
- Not hidden: the packet header, including who sent it, and anything sent on the default channel, such as your node name and, if you share it, your position.
A text message holds up to about 228 bytes. Up to firmware 2.7, Meshtastic shares your position by default if the node has GPS or your phone provides it. Firmware 2.8 keeps it private by default, with position and telemetry broadcasts off. Whichever you run, check the position settings in the app.
Range and antennas
Height and a clear view matter more than anything else. Mount the antenna vertically, clear of your body and metal, and keep coax short: 5 m of RG58 loses about 2.5 dB at 869 MHz. If you change the antenna, run the checker again.
When it doesn't work
| Problem | Things to check |
|---|---|
| App can't find or connect to the node | Bluetooth permissions, that no other phone is connected, and the pairing PIN shown on the node's screen (screenless nodes default to 123456). |
| Nothing heard | The region, preset and frequency slot. All three must match your local mesh. Check the antenna and try outdoors. |
| Messages show as sent but never acknowledged | Whether anyone is in range: check the node list and its signal readings. Try a node nearby first. |
| UK: the node stops transmitting for a while | It has used its 10% for the hour. Cut down position and telemetry intervals, or move to a faster preset. |
| Battery drains fast | The role (CLIENT relays traffic), GPS, screen timeout and Bluetooth. Power saving mode helps on some boards. |
Meshtastic isn't an emergency service and nobody is guaranteed to be listening. In an emergency, call 999 or 112.
Sources
- Ofcom, IR 2030, 23 October 2026 edition, entries IR2030/1/10 and IR2030/1/19.
- Meshtastic docs: LoRa settings, presets, device roles, mesh algorithm, encryption, switching from LongFast and 2.8 notes.
- Meshtastic firmware source (region limits, preamble and packet sizes).
Checked November 2026. See also Meshtastic USA, MeshCore UK and Meshtastic vs MeshCore.
Questions
What frequency does Meshtastic use in the UK?
869.525 MHz, in the EU_868 region with the default LongFast preset (250 kHz, SF11). It's the only 250 kHz slot in the 869.4 to 869.65 MHz band.
Is Meshtastic legal in the UK?
Yes, licence-free, under Ofcom IR2030/1/19: up to 500 mW ERP and a 10% duty cycle.
Does Meshtastic keep me within the UK power limit?
Not on its own. The firmware caps output at 27 dBm, but the 500 mW limit is radiated power, so antenna gain counts. 27 dBm into a 5 dBi antenna is about 1 W ERP.
Does Meshtastic stick to the 10% duty cycle?
Yes, in the EU_868 region the firmware enforces 10% over a rolling hour, unless you turn on Override duty cycle.
Should I use 433 MHz or 868 MHz Meshtastic in the UK?
868 MHz. It allows 500 mW ERP against 10 mW on 433 MHz, and most UK meshes use it.
Which Meshtastic preset should I use in the UK?
The one your local mesh uses. That's usually LongFast, but busy meshes may move to MediumFast or another faster preset.