Customer experience

UXHub

Launch a branded self-service experience for plan purchase, activation, usage, billing, upgrades, and support.

YOUR BRANDPLANSSELF-SERVICESUPPORTExplore UXHub
Three hubs on one data model, one API, and one invoice.Read the API docs
Platform
Solutions
Services
Customers
Resources
Home eSIM NB-IoT vs LTE-M vs 5G RedCap: How to Choose in 2026

NB-IoT vs LTE-M vs 5G RedCap: How to Choose in 2026

NB-IoT vs LTE-M vs 5G RedCap compared on mobility, latency, battery, coverage and cost, plus an acceptance test to run before you commit hardware.

Line-art illustration of a small sensor, a cell tower and a moving delivery van connected by thin orange lines, with one peach accent on the tower.

TL;DR / At-a-Glance Summary

NB-IoT fits small, infrequent reports from fixed devices with deep indoor reach. LTE-M fits moving devices, larger payloads and over-the-air updates. RedCap brings 5G NR at reduced complexity. Battery life depends on the reporting cycle and network timers, so prove the choice with a field pilot.

NB-IoT for still, small reports

Meters and fixed sensors that send little and can tolerate delay.

LTE-M for movement and updates

Handover, faster response and larger transfers for trackers and fleets.

Battery is not a fixed ranking

Timers, retries and coverage change which radio uses less energy.

RedCap needs its own check

Confirm module, bands and operator support before designing around it.

Pilot before you commit

Test the exact module and network, and compare radio logs with delivered data.

Last verified 2 November 2026.

NB-IoT vs LTE-M comes down to how the device behaves. NB-IoT suits stationary devices that send small, infrequent reports and need deep indoor reach. LTE-M suits devices that move, send larger payloads, need faster response or must take firmware updates over the air. 5G RedCap is a third option for applications that need 5G New Radio at lower device complexity than full 5G. Neither low-power radio is automatically the longer-lasting one: battery life depends on the whole reporting cycle and on timers the network sets, not on the technology name.

The rest of this guide gives the head-to-head table, then the questions that change the answer: mobility, latency, battery, coverage, cost and what eSIM can and cannot do. It ends with an acceptance test you can run on real hardware. For the wider field of options, including LoRaWAN and satellite, see the IoT connectivity comparison. Treat every figure below as a starting hypothesis: a standard describes what a radio can do, and only a named module on a named network proves what your device will do.

Three orange paper-cut devices on a hillside, a still water meter under a tower, a moving delivery van and a small 5G camera, linked by cream ribbons to one cell tower
The same network can serve a still meter, a moving tracker and a camera, but each needs a different radio.

Head-to-head: NB-IoT vs LTE-M vs 5G RedCap

NB-IoT and LTE-M are low-power wide-area cellular technologies that 3GPP standardized in Release 13. Reduced Capability (RedCap) is a 5G New Radio device class defined in Release 17. They overlap, but they target different workloads, and you should compare the named device category (for example Cat-NB1, Cat-M1) rather than the marketing label.

CriterionNB-IoTLTE-M5G RedCap
Starting specification3GPP Release 13 (Cat-NB1); Release 14 added Cat-NB23GPP Release 13 (Cat-M1)3GPP Release 17, reduced-capability NR
Bandwidth180 kHz allocation (one LTE resource block, 200 kHz carrier)1.4 MHz channelUp to 20 MHz in FR1 and 100 MHz in FR2
Peak data rate in a real moduleTens of kbps for Cat-NB1 (u-blox lists 27.2 kbps down, 62.5 kbps up for one module)Hundreds of kbps (the same u-blox module lists 375 kbps for Cat-M1)Megabit-class and far higher; read the module datasheet
Mobility while connectedCat-NB1 has no connected-mode mobility; Cat-NB2 added someHandover is an inherent featureStandard NR mobility; validate on your route
VoiceNot a voice technologyVoLTE where the operator supports itOperator and device dependent
Power-saving toolsPSM and eDRXPSM and eDRXPower-saving features; module dependent
Best first guessSmall reports, tolerant of delay, hard-to-reach placesMoving assets, larger transfers, over-the-air updatesWorkloads that need NR at lower cost and complexity than full 5G

Sources: Nordic Semiconductor Academy for bandwidth, handover and Cat-NB2; u-blox SARA-R410M-02B datasheet figures as reported in CNX Software; ETSI TS 38.300 v17.9.0 for the RedCap release. Peak rates are datasheet maxima; protocol overhead and signal conditions lower them.

Key takeaway: choose the smallest radio capability that meets the application requirement, then validate the whole device and service. A newer release is not automatically a better commercial fit.

What NB-IoT and LTE-M have in common

They are better understood as complementary than as rivals. Both are 3GPP standards, both run on licensed cellular spectrum, both support PSM and eDRX, both use cellular-grade authentication with a SIM or eSIM, and both were designed for large numbers of devices per cell. Many fleets use NB-IoT for fixed sensors and LTE-M for moving or higher-data devices, and run both under one management layer. A useful shorthand: NB-IoT is a heart monitor sending a pulse once an hour, while LTE-M is a smartwatch that syncs and moves with you.

If you need…Start with
Deep indoor or underground reachNB-IoT
A fixed meter that reports a few times a dayNB-IoT
Moving asset trackingLTE-M
Firmware updates over the airLTE-M
Fast two-way commandsLTE-M
Voice on a wearableLTE-M, where the operator supports it
NR features at reduced device complexity5G RedCap

How do data rate, mobility and latency affect the choice?

They matter only against the application’s delivery requirement. A moving tracker may need an unbroken session, while a meter can reconnect between reports. Measure the time from a device event to a usable record in your backend, including wake-up, network access, retries and processing.

For a quick NB-IoT vs LTE-M decision, shortlist NB-IoT for small, infrequent reports where delayed delivery is acceptable, and LTE-M when movement during an active session, larger transfers or frequent interaction matter. These are hypotheses to test, not guarantees.

Separate movement from session continuity

A device can travel between reporting locations without holding a session the whole way. That is different from handing an active connection from cell to cell. Cat-NB1 had no connected-mode mobility, Release 14 Cat-NB2 added some connection transfer between base stations, and LTE-M handles handover natively (Nordic Semiconductor Academy). Adoption of the NB-IoT mobility enhancements varies by operator, so do not assume them. Test your actual route and the recovery behavior after a cell change, and avoid copying a vehicle-speed threshold from a generic comparison.

Test deadlines, not advertised peaks

Latency is where the two differ most in practice, and it depends heavily on coverage conditions. Ericsson’s NB-IoT overview puts uplink latency from about 1.6 seconds in good coverage to about 7.6 seconds at the deepest coverage extension (Ericsson Technology Review). In Nordic’s field test on one Norwegian network, an LTE-M device connected from a cold start in roughly 3.4 to 4.8 seconds, against 17 to 28 seconds for NB-IoT. Those are single-network, single-hardware results, so use them as direction, not as a spec for your fleet.

Record message size, acknowledgement policy and acceptable delivery time. Include command delivery to a sleeping device. Peak radio rates leave out protocol overhead, signal quality and scheduling. RedCap deserves evaluation when its NR capabilities fit the workload, not because the roadmap says 5G.

How should NB-IoT vs LTE-M battery life be compared?

Both technologies are designed for multi-year battery operation, and Ericsson cites a design target of more than 10 years with sustained reachability for NB-IoT using PSM and eDRX. That is a design target under idealized duty cycles, not a promise for your device. The honest answer to which lasts longer is that it depends on payload, coverage, retries, sleep current and network timers.

Nordic’s published field experiment shows why a fixed ranking fails. Over most of the distances tested, LTE-M used less charge per connection because it attached faster. NB-IoT used less in a few obstructed positions and reached farther. Nordic also found the NB-IoT cell used a longer RRC inactivity timer (18 s vs 11 s) and a longer connected-mode DRX cycle (2048 ms vs 320 ms), and when it simulated each network’s settings the average current came out at about 31 µA for LTE-M and 18 µA for NB-IoT. The author attributes that gap to the network configuration, not to the technology. Read the full write-up: it dates from 2022, used one nRF9160 module and static positions, and the network operator, not the device, set the timers.

Power Saving Mode (PSM) lets a device sleep and stay unreachable between reports. Extended DRX (eDRX) lengthens paging intervals. PSM arrived in Release 12 and eDRX in Release 13 (Ericsson). The settings a device requests and those the network grants can differ, so log both.

A tracker labelled Send, a Wi-Fi-style puck labelled Wait and a moon pillow labelled Sleep joined in a loop by a cream ribbon under a tower, showing the connect, send, wait and sleep cycle.
Energy is spent across connection, transfer, waiting and sleep, so measure the whole loop.

Build an energy budget you can reproduce

Measure charge across connection establishment, transfer, waiting and sleep. Add failed attempts, recovery and firmware maintenance. Include the sensor, processor and power supply, because modem consumption alone is not device consumption. State usable battery capacity, operating temperature and service-life assumptions before you estimate a replacement interval.

Watch out: a device that sends less data can still use more energy if it searches repeatedly or waits on unsuitable timers. Use a successful report, with failed attempts included, as the comparison unit.

For a connected sensor deployment, align battery measurements with the real sampling and reporting schedule, and test long coverage loss explicitly, because retries can dominate an otherwise efficient cycle. The IoT sensors and connectivity guide covers how sensor type shapes that schedule.

What determines coverage, roaming and global availability?

Availability depends on the radio service, supported bands, device approval and subscription agreement together. An operator’s LTE or 5G footprint does not prove NB-IoT, LTE-M or RedCap is offered to your device. NB-IoT was designed with a 164 dB link-budget target, against about 144 dB for GPRS and 142.7 dB for LTE, which Ericsson equates to roughly 20 dB of added reach for deep indoor and underground sites. Treat that as a design target: actual indoor performance depends on the installation, antenna and local network.

The GSMA Mobile IoT deployment map shows which operators have launched LTE-M, NB-IoT or both, which helps build a shortlist. It does not promise indoor reception, roaming access or every optional feature. Ask the provider which serving networks and restrictions apply to your contracted scope; long-term roaming policies in particular vary by operator.

RedCap needs its own commercial check. T-Mobile’s RedCap update describes one operator’s service and devices. It is evidence that RedCap is deployed in a specific context, not that every 5G subscription or module supports it.

Write down the supported combination

Record the module model, firmware, antenna design, bands, operator, subscription and enabled features, and keep that matrix versioned alongside the bill of materials. A firmware change or service migration can invalidate an earlier test. Pilot in weak-signal places, inside real enclosures and along real routes, and record failures as carefully as successes. One successful attach in one country is not evidence for a launch list. The same logic applies to single-network deployments: see the risks in the guide to single-carrier IoT.

How do module cost and total cost of ownership compare?

Module price is one line in cellular IoT ownership cost. Certification, integration, connectivity charges, battery replacement, field visits and eventual migration can outweigh a small difference in module price. NB-IoT modules have generally been positioned as the cheaper option, but compare quotes for the same countries, volumes, traffic and support scope instead of relying on price bands. The IoT connectivity cost guide develops the commercial model separately.

Cost inputUnit to recordEvidence to obtain
Hardware and integrationPer device and one-time project costModule, antenna, engineering and certification quote
Connectivity servicePer active line, period and traffic unitContracted countries, minimums and usage terms
Field maintenancePer interventionMeasured failure rate and service process
MigrationPer affected device and projectHardware limits, service notice and replacement plan

Source: proposed procurement worksheet. No prices or failure rates are supplied.

Ask what happens to billing when devices are suspended, replaced or stored before activation, get separate quotes for configurations that pass technical screening, and record exclusions and support ownership. The cheapest data allowance is rarely the lowest lifecycle cost.

What changes with eRedCap, network evolution and eSIM?

Enhanced RedCap (eRedCap) belongs to Release 18. It defines a reduced peak rate of 10 Mbps and an optional 5 MHz baseband bandwidth in FR1, with the radio-frequency bandwidth still 20 MHz. It is a lower-cost step down from RedCap, not an LTE-M replacement, so confirm which category a proposed module supports.

Release 17 also added satellite (non-terrestrial network) support for NB-IoT and LTE-M. That does not make existing devices satellite-ready: it takes a compatible module, firmware, bands and a commercial satellite service.

Definition: eSIM changes subscription profiles on compatible hardware. It does not add radio bands, an antenna or a modem technology, so it cannot turn an LTE-M modem into a RedCap one.

Provisioning is a separate layer from the radio; the SGP.22 vs SGP.32 guide and the IoT SIM cards guide explain it. An eSIM migration still needs compatible hardware, supported profiles and a recovery path, and remote provisioning will not remove every truck roll. On longevity, obtain each operator’s current support position and contractual notice terms instead of assuming a universal sunset year for NB-IoT or LTE-M.

How should you choose and validate a cellular IoT radio?

Run a documented acceptance test on the supported device and service combination before fleet rollout. Define delivery, power, mobility and recovery requirements first, then keep radio logs and application records together so a successful attach cannot hide failed business data.

A test device on a pedestal beside a paper log, a delivery van on a road and a cell tower, joined by a ribbon that returns to the start to show the pilot loop.
A pilot compares radio logs with application records on the exact device and network you will ship.
TestRecordAcceptance owner
Normal reportingPayload, delivery time, retries and energyProduct and device engineering
Movement or weak coverageCell changes, losses and application recoveryRadio engineering and operations
Remote commandsSleep settings and command completionApplication engineering
Maintenance and outageUpdate interruption, rollback and service restorationDelivery and support

Source: proposed field acceptance checklist. Set numeric thresholds from your product requirements before testing.

Define the reporting and command workload, including maintenance. Confirm the approved module, firmware, bands and service. Run comparable tests in normal and adverse conditions, reconcile device logs with received application records, and approve rollout only after assigning ownership for failure and recovery.

Spenza, an MVNE platform for connected-product operations, describes multi-country sensor rollout in its published Butlr case study. That is evidence about coordinating activation across countries, not a ranking of NB-IoT, LTE-M or RedCap, so measure radio performance on your own devices. If a fleet mixes radio types and carriers, a single management layer keeps provisioning and monitoring consistent; see the eSIM orchestration guide and the overview of IoT connectivity management platforms. Moving assets raise their own questions, covered in the asset tracking connectivity guide.

Conclusion: pick from behavior, prove it in the field

Choose NB-IoT, LTE-M or RedCap from the application requirement and the commercial combination you can actually buy. Use standards to understand capability, operator evidence to confirm availability, and field measurements to approve the product. Keep power, delivery and recovery records comparable across candidates.

A radio that looks right on a specification sheet can still fail the installation or the operating model. The next step is a bounded pilot with named owners, documented conditions and thresholds agreed before results arrive, with an alternative configuration held in reserve until the data justifies the rollout.

Frequently asked questions

What is the main difference between NB-IoT and LTE-M?

NB-IoT is built for small, infrequent reports from mostly stationary devices and offers deep coverage. LTE-M offers higher data rates, native handover and faster response, which suits moving devices and over-the-air updates. Both are 3GPP Release 13 technologies on licensed spectrum.

Which is better for battery-powered devices?

Neither always wins. NB-IoT is designed for very long life at low duty cycles, but a field test by Nordic Semiconductor found LTE-M used less energy in normal conditions because it connected faster, and that network timers drove much of the difference. Measure your own reporting cycle on the target network.

Can LTE-M be used for asset tracking?

Yes. LTE-M supports handover between cells and is the usual starting point for moving assets. Test your real routes, because coverage and recovery after losing signal vary by operator.

Can NB-IoT handle firmware updates?

It can carry downlink data, so it is not a one-way technology. Practical updating depends on image size, throughput, energy and recovery from interruption. LTE-M is generally the easier fit for large images. Test a full update under weak coverage, including verification and rollback.

Can these radios support voice calls?

NB-IoT is not a voice technology. LTE-M can support VoLTE where the operator offers it, and RedCap voice depends on the operator and device. Require a supported voice configuration and test calls on the intended network.

Do NB-IoT and LTE-M need a SIM or eSIM?

Yes. Both use cellular authentication, so a device needs a SIM or eSIM that the target network accepts. An eSIM changes subscription profiles but does not change the radio capability of the modem.

Can one module serve every launch country?

Sometimes, but it needs evidence. Supported bands, certification, operator approvals and subscription access must all line up. Keep a country-by-country matrix for the exact hardware and firmware, and plan a separate variant where a configuration is unsupported.

Can NB-IoT and LTE-M run in the same deployment?

Yes. Many fleets use NB-IoT for fixed sensors and LTE-M for mobile or higher-data devices. Managing both under one platform keeps provisioning, monitoring and billing consistent.

Contact Us Today

Related Articles

Discover insights on telecom trends, IoT, eSIM technology, and connectivity solutions with guides.

Orange line art of three cell towers, a SIM card and a small sensor device linked by curved signal lines on a cream panel.

Multi-Carrier SIM Cards: How They Work and How to Choose

Multi-carrier SIM cards explained: multi-IMSI, eUICC and roaming SIMs, steered vs non-steered networks, failover behavior and a checklist for IoT
Line illustration of an invoice with a checkmark, a SIM card, a cell tower, a calculator and a stack of coins on a warm cream panel.

Telecom Billing Software: Buyer's Guide for MVNOs and MSPs

Compare telecom billing software for MVNOs, MSPs and IoT resellers: rating, usage-based billing, taxes, carrier reconciliation and vendor questions.
Orange line drawings of a SIM card, a globe, a signpost with two opposing arrows, a cell tower and a contract sheet with a check mark, on a pale panel beside the post title.

Permanent Roaming Rules by Country for IoT Devices

Explore IoT permanent roaming rules by country, including restrictions, time limits, and local eSIM requirements. Compare rules and plan global

Subscribe for Smarter Connectivity Insights

Join thousands of professionals receiving expert perspectives, industry trends, and practical strategies shaping the future of telecom and connected devices.