8th September 2026By Neil Skoglund
LoRaWAN Coverage Guide
Before you buy a single sensor, there is one question worth answering properly: will LoRaWAN actually reach your site? Unlike the mobile networks, nobody guarantees nationwide LoRaWAN coverage across the UK. It exists in a patchwork of community networks, decentralised hotspots, commercial operators and private gateways - and whether it reaches your building depends on things a national coverage map will never tell you.
This guide is about answering that question for your site, not explaining LoRaWAN from first principles - if you want the plain- English basics first, see our LoRaWAN 101 glossary. Here, we cover how UK coverage actually works, what determines whether a signal reaches your building, when public network coverage is genuinely enough, and when it makes sense to plan and install your own gateway.
When you buy a SIM card, coverage is (mostly) a solved problem - EE, O2, Vodafone and Three have spent decades and billions of pounds building out infrastructure with an expectation of near-universal coverage. LoRaWAN has no equivalent obligation and no single operator responsible for the whole country. Instead, UK coverage comes from several different, unconnected sources:
A free, community-run network built entirely from volunteers' gateways. Coverage is genuinely strong in cities and towns with an active local community, and thin to non-existent everywhere else. You can browse registered gateways on the TTN coverage map, though a pin on that map is a starting point, not proof of a usable link at your address.
A decentralised network of independently owned hotspots, viewable on Helium's own IoT coverage map. Density varies enormously by area, and it has changed over time as hotspot operators have come and gone - a location that had a nearby hotspot a couple of years ago is not guaranteed to still have one today. Always check current coverage rather than relying on what you remember or what a colleague told you.
Dedicated IoT network operators are also building out UK LoRaWAN infrastructure on a commercial basis, often through partnerships with telecoms infrastructure providers, targeting utilities and large enterprise contracts rather than open, free-to-use access. Useful to know this layer exists, but it is a different proposition to a community network - coverage is typically built around contracted customers, not general availability.
A gateway you own and control, placed exactly where your site needs it. No dependency on volunteers, decentralised incentives or someone else's contract - the coverage is there because you put it there, and it stays there.
The upshot: "does LoRaWAN cover the UK?" is the wrong question. The right one is "does LoRaWAN cover my site," and the only way to answer that is to check.
The TTN map and Helium's coverage map show where gateways are registered, not what signal actually reaches ground level at your building. A gateway two streets away can still leave you with nothing usable if a hill, a steel-clad building, or simple distance and antenna height get in the way.
Community tools such as TTN Mapper log actual measured signal strength from real devices moving around, which is a more honest picture of what you would get than a static gateway pin. It still will not tell you what happens once you go indoors, though.
There is no substitute for putting a real LoRaWAN device where it will actually live - on the loading bay, in the basement plant room, at the back of the warehouse - and seeing what it can reach over a few days. A single day of on-site testing is far cheaper than discovering the gaps after a hundred sensors are already deployed.
If missed readings have a real cost - compliance, safety, cold chain, security - do not rely on ad-hoc testing alone. An RF propagation survey models your specific site (building materials, layout, terrain) and tells you exactly where coverage will and will not reach, and how many gateways you actually need to close the gaps.
LoRaWAN can travel a genuinely long way on a clear line of sight, but real sites are rarely a clear line of sight. These are the factors that matter most:
In open, rural conditions with a clear line of sight, a single gateway can cover several kilometres. In built-up areas with obstructions, effective range typically drops to well under a kilometre. More gateways nearby means more redundancy, not just more range.
Timber frame and standard brick are fairly forgiving. Reinforced concrete, steel-frame structures, metal cladding and low-e glass attenuate signal significantly and are the usual cause of a site that looks covered on a map but isn't in practice.
Hills, valleys and dense urban clutter block line of sight even when a gateway is technically nearby. A gateway on the wrong side of a ridge, or three streets of tall buildings away, may as well not exist for your site.
Outdoor assets can often piggyback on a gateway some distance away. Indoor deployments - especially deep inside large steel- clad buildings, basements or plant rooms - usually need a gateway that is much closer, often inside the same building.
There is no universally right answer - it depends on your site, your use case, and how much a missed reading actually costs you.
| Situation | Public network coverage | Private gateway |
|---|---|---|
| Outdoor assets in an area with decent hotspot density | Often enough | Optional, for redundancy |
| Steel-clad warehouse or industrial building, indoor sensors | Usually not reliable | Generally required |
| Small pilot or proof of concept, low message volume | Good starting point | Worth planning ahead of scale-up |
| Remote or rural site with no nearby registered gateway | Likely no coverage at all | Required |
| Multi-site rollout needing a consistent, predictable SLA | Coverage varies site to site | Recommended for consistency |
| Safety, compliance or cold-chain critical alerting | Gaps carry real risk | Recommended |
Plenty of businesses land somewhere in the middle - a private gateway covering the buildings and yard where reliability matters most, with public network coverage picked up as a bonus wherever it happens to be available. Getting that mix right is exactly what a coverage survey is for.
When coverage genuinely needs to be guaranteed rather than hoped for, our LoRaWAN consultancy team carries out RF propagation modelling and gateway placement surveys before any hardware goes up, so you know coverage will work rather than finding out the hard way once sensors are already in the field.
From there we handle full gateway deployment - from DIN-rail indoor units to IP67 outdoor gateways with LTE backhaul - and design and run the LoRaWAN Network Server behind it, whether that is ChirpStack, The Things Network, The Things Industries, Actility or a private hosted setup. For multi-site or cross-border projects, we can combine private gateways with public network roaming where it genuinely makes sense, and we work across EU868, US915, AU915 and AS923 frequency plans for deployments outside the UK too.
If you are also evaluating LoRaWAN specifically for tracking vehicles, equipment or goods, our LoRaWAN asset tracking platform pairs directly with this kind of coverage planning, so trackers report reliably from day one rather than dropping out in the parts of a site nobody checked in advance.
Simulate coverage for your actual building and terrain before a single gateway is installed.
Antenna selection, indoor and outdoor installation, sited to maximise range, reliability and redundancy.
Production-grade LNS setup and hosting, so the coverage you plan for actually turns into reliable, decoded data.
No, and this is the single most important thing to understand before planning a deployment. EE, O2, Vodafone and Three have built (and are obliged to maintain) near-universal cellular coverage. LoRaWAN has no equivalent - coverage exists only where someone has actually installed a gateway, whether that is a community volunteer, a decentralised network like Helium, a commercial operator, or your own business. Coverage is real in plenty of places, but it is a patchwork, not a guarantee.
Start with the public coverage maps for The Things Network and Helium to see if a gateway is registered nearby, then treat that as a starting point rather than proof. The only reliable way to confirm coverage is to put a LoRaWAN device at the actual location - including indoors, in the basement, or wherever it will really sit - and see what it can reach. For a permanent business deployment, a proper RF propagation survey removes the guesswork entirely.
Reinforced concrete, steel-frame construction, metal cladding, low-emissivity glass and dense server rooms or plant rooms all attenuate LoRaWAN signal significantly. Basements and the centre of large steel-clad industrial buildings are typically the hardest environments. Timber-frame and standard brick buildings are far more forgiving. Distance to the nearest gateway and how much it can "see" through walls both matter as much as raw distance.
Sometimes, for the right use case. If your assets are mostly outdoors, in an area with decent existing hotspot or gateway density, and a missed reading now and then is not a big deal, public networks can be a genuinely good, low-cost option. Where you need guaranteed indoor coverage, cover a remote site with no nearby coverage, or cannot tolerate gaps because the data feeds a safety or compliance process, a private gateway - or a mix of private and public - is the more dependable route.
It depends entirely on the building, the terrain and where your devices sit. A single well-placed rooftop gateway can sometimes cover a whole small-to-medium site outdoors, while a large steel-clad warehouse with devices tucked among racking might need several indoor units to close the dead spots. This is exactly what an RF propagation survey is for - modelling your specific site rather than guessing.
Yes. Our LoRaWAN consultancy team carries out RF propagation modelling and gateway placement surveys, then handles deployment of indoor and outdoor gateways, network server design and hosting, and integration into your dashboard - so you get a coverage plan that is proven before a single sensor goes into service, not one you find the gaps in after the fact.
Not sure whether your site is covered? Talk to our LoRaWAN consultancy team about an RF propagation survey, or explore the LoRaWAN asset tracking platform if you already know coverage is in place and want to see it working on your own assets.
Get a personalized walkthrough of our platform. We'll show you how Trackpac can solve your specific monitoring challenges.
30 minutesNo commitmentPick any time
