Trying to settle LoRaWAN vs NB-IoT for a battery-powered sensor? You’ll likely want LoRaWAN for range, low power and no subscription, and NB-IoT for carrier-managed coverage and lower latency.
This comparison sits inside the wider topic of iot development, where picking a network is one of the earliest decisions.
| Item | Value |
|---|---|
| LoRaWAN outdoor range (line-of-sight, one gateway) | 5-15 km |
| LoRaWAN typical payload size | Up to 250 bytes |
| LoRaWAN peak current | 32 mA |
| Battery life, LoRaWAN / NB-IoT (vendor comparison) | 15+ years / 10+ years |
| NB-IoT carrier cost per device | Roughly $0.50/month |
| Standard cellular cost per device | $1-10/month |
These figures come from TagoIO’s connectivity guide and Ubidots’ LoRaWAN vs NB-IoT comparison. They can change, so check the source before you rely on them.
How the two networks work
LoRaWAN uses unlicensed spectrum: TagoIO’s guide lists 868 MHz in Europe and 915 MHz in North America. You pay nothing for spectrum access, so you can run your own gateways.
NB-IoT runs on licensed cellular spectrum managed by mobile network operators, as the same guide explains. You buy a SIM card and pay a monthly fee instead of deploying infrastructure.
In a LoRaWAN network, Kaa IoT’s comparison says end devices communicate with gateways, which forward data to a network server. That layout lets an organisation build a private network without relying on a telecom operator.
Range and coverage compared
LoRaWAN range depends on the environment, but TagoIO reports that outdoor deployments regularly reach 5-15 km line-of-sight with a single gateway. Kaa IoT gives the same typical range of 5-15 km for rural or open sites.
With NB-IoT, coverage is wherever the carrier’s network reaches. In dense urban areas that often beats LoRaWAN thanks to better building penetration, according to TagoIO.
The catch is carrier availability. TagoIO’s guide reports that AT&T ended NB-IoT service in early 2025 and migrated customers to LTE-M. Confirm your target markets before you commit.
Interference is another difference. Kaa IoT says LoRaWAN’s chirp spread spectrum modulation gives strong resistance to interference and multipath effects. It also says NB-IoT coverage depends entirely on operator networks, which can leave gaps in remote areas.
Power and battery life
Vendor comparisons favour LoRaWAN. Ubidots lists 15+ years of battery life against 10+ years for NB-IoT. Treat both as best-case numbers, not promises.
For a more practical example, TagoIO says a sensor on two AA batteries can run for 5-10 years sending data every 15 minutes. That is a useful planning range for a real deployment.
The reason is current draw. Ubidots puts LoRaWAN’s peak current at 32 mA, one fourth of NB-IoT’s. A CNX Software write-up of AMIHO Technology’s datasheet comparison found LoRaWAN about three to five times more efficient in current terms.
The same CNX Software piece warns that the advantage is not constant. Three things move the result:
- Message rate: CNX Software says LoRaWAN really shines when sending few messages per day, because it stays longer in sleep modes.
- Signal quality: a LoRaWAN node far from the gateway may not last as long as an NB-IoT node closer to its base station, per the same write-up.
- Coverage: when many messages are sent each day, the power gap narrows and coverage should enter your power equation, CNX Software adds.

Data rate, payload and latency
Both are low-bandwidth technologies, so the trade-offs show up in the details:
- Bitrate: NB-IoT can reach around 100 kbps, against 300 bps to 38.4 kbps for LoRaWAN, according to CNX Software.
- Payload: LoRaWAN packets are typically up to 250 bytes, which TagoIO says suits a temperature reading or GPS coordinate but not a photo.
- Latency: Kaa IoT says LoRaWAN’s higher latency and duty-cycle constraints limit its suitability for real-time control.
- Density: NB-IoT supports up to 50,000 devices per cell, per Kaa IoT.
Cost: subscriptions versus gateways
Kaa IoT frames the key difference as cost structure: NB-IoT shifts costs to OPEX through connectivity subscriptions, while LoRaWAN shifts them to CAPEX through gateway deployment.
On the NB-IoT side, TagoIO puts the price at roughly $0.50/month per device on most carrier plans. Standard cellular is typically $1-10/month, depending on data volume and carrier.
For LoRaWAN, Kaa IoT points to the absence of subscriptions as a strength for long-term deployments with limited maintenance access, as its comparison describes. Budget for the gateways up front.
Which should you pick for your project?
TagoIO says no connectivity technology wins for every use case. Your decision rests on how often the device sends, what coverage it needs, how long it must run on battery, and whether you want to own the network.
Lean towards LoRaWAN when:
- Devices are battery powered and send small, infrequent updates.
- You want to own the gateways and the data path.
- Sites are rural, remote or spread across a campus.
Lean towards NB-IoT when:
- Devices are fixed in urban areas, such as utility meters or parking sensors.
- A carrier you trust already covers your sites.
- You prefer paying a subscription over running infrastructure.
Cellular, Wi-Fi and satellite may also be in play, and the guide to iot connectivity options lines them up side by side. If you are also choosing the board that runs the radio, the esp32 vs raspberry pi comparison covers that side.
Frequently asked questions
Do I need a SIM card for LoRaWAN?
Show answer
No. LoRaWAN devices join through a gateway, and platforms such as TagoIO connect to network servers including TTN, ChirpStack and Actility, as its guide notes.
Is NB-IoT available everywhere?
Show answer
No, because it depends on a carrier. TagoIO’s guide says Vodafone offers nationwide NB-IoT coverage in the UK, but check the operator’s own coverage map before you commit.
Which one is more secure?
Show answer
Ubidots rates NB-IoT as the more secure option, citing 256-bit 3GPP encryption against AES 128-bit for LoRaWAN. Weigh that against your own threat model.
Can I use both on one project?
Show answer
You can, since there is some space for complementary use. Ubidots still expects most organisations to pick one because of budget limits.
