Guide · Connectivity
LTE-M vs NB-IoT: the differences that matter for devices on the move
LTE-M and NB-IoT are both low-power cellular standards from 3GPP for small, battery-powered devices. LTE-M uses a 1.08 MHz channel, hands off between cells while connected, and reaches about 100 to 150 kbps in the field. NB-IoT uses 180 kHz, peaks near 26 kbps down and 66 kbps up, and reaches deeper indoors. For a device that moves between jobsites all day, LTE-M is usually the better fit.
Last updated By ZeroBadge
What are LTE-M and NB-IoT?
LTE-M and NB-IoT are two cellular standards built for devices that send small amounts of data and run on batteries, such as meters, trackers and worn badges. Both came out of 3GPP Release 13, and 3GPP announced NB-IoT complete in June 2016 (3GPP). Both run on mobile operators' licensed spectrum, so they use the carrier's towers instead of equipment you install.
They were designed with different priorities. A 3GPP overview describes LTE-M as able to offer lower latency and higher throughput than NB-IoT and to support voice over IP, while NB-IoT targets ultra-low device complexity and can run in a system bandwidth as low as 200 kHz (3GPP). The GSMA Mobile IoT Deployment Guide (February 2026) calls them complementary and says they are often deployed side by side in the same network.
- LTE-M
- Also called LTE Cat-M1 or eMTC. A trimmed-down LTE that rides the carrier's existing LTE network, keeps LTE's handover between cells, and carries more data.
- NB-IoT
- Narrowband IoT, Cat-NB1 and NB2. A much narrower radio that can sit inside an LTE carrier, in its guard band or on its own, built for small, infrequent messages and deep coverage.
How do LTE-M and NB-IoT compare side by side?
LTE-M gives up a little coverage depth in exchange for more speed and proper mobility. NB-IoT gives up speed and mobility in exchange for reach and simplicity. The table uses the GSMA's published figures.
| LTE-M (Cat-M1) | NB-IoT (NB1 / NB2) | |
|---|---|---|
| Standard | 3GPP Release 13 | 3GPP Release 13 |
| Channel width | 1.08 MHz narrowband channel | 180 kHz |
| Data rate | About 300 kbps down and 380 kbps up (half duplex); 100 to 150 kbps average in the field | Peak 26 kbps down and 66 kbps up (NB1); NB2 roughly doubles it |
| Latency in normal coverage | About 100 to 150 ms | Around 1 second |
| Moving between cells while connected | Handover is part of the baseline (intra-frequency since Release 13, inter-frequency since Release 14) | Connected-mode mobility was added later; the GSMA says it is yet to see wide adoption |
| Deep coverage in deployed networks | CE Mode A, about +5 dB; the deeper Mode B had no known deployment as of 2025 | Up to 164 dB maximum coupling loss, about +20 dB over GSM |
| Power saving | PSM and eDRX | PSM and eDRX |
| Voice | VoLTE possible, with limited deployment | No |
| SMS | Many operators support it | Many operators have not enabled it |
| Networks deployed worldwide (Oct 2025) | 129 | More than 140 |
How much data can each one move, and does it matter?
LTE-M moves several times more data than NB-IoT, and that matters for large transfers and quick replies, not for small periodic reports. The GSMA puts LTE-M at around 300 kbps down and 380 kbps up in half-duplex mode, with 100 to 150 kbps on average in the field, and NB1 at a peak of 26 kbps down and 66 kbps up, with latency around 1 second in normal coverage (GSMA).
A location report is small, so either standard carries it easily. Where the gap shows is a firmware update pushed to a fleet of devices.
Time to download a 1 MB firmware update
- Size in bits
- 1 MB = 1,000,000 bytes × 8 = 8,000,000 bits
- LTE-M at 100 kbps (low end of the field average)
- 8,000,000 / 100,000 = 80 seconds
- LTE-M at 150 kbps
- 8,000,000 / 150,000 ≈ 53 seconds
- NB-IoT NB1 at its 26 kbps downlink peak
- 8,000,000 / 26,000 ≈ 308 seconds, about 5 minutes
- NB-IoT NB2 at roughly double that
- ≈ 154 seconds, about 2.5 minutes
- What it means
- On NB-IoT, a large download takes several times longer, and the NB-IoT figures are peak rates
The 1 MB size is an example, not any particular device. Protocol overhead and retries add time to every figure. In weak coverage, the GSMA notes both standards fall to a few kbps.
What happens when a device moves from one cell to the next?
On LTE-M, the network hands a connected device over to the next cell as it moves. On NB-IoT, a device mostly reselects a new cell while idle, and keeping a connection alive across cells depends on a later feature that the GSMA says is yet to see wide adoption.
The GSMA guide explains the two modes. In idle mode, the device decides when to reselect a cell. In connected mode, the network decides when the device moves and to which cell, and triggers the handover. The guide recommends LTE-M networks support intra-frequency handover (since Release 13) and inter-frequency handover (since Release 14) for all data traffic, and it notes LTE-M performance requirements defined for speeds around 240 km/h at 1 GHz.
NB-IoT went the other way. One of its power-saving features, relaxed monitoring, lets a device that is not moving check neighbouring cells as seldom as every 24 hours. That suits a gas meter in a basement. It does nothing for a badge that rides in a pickup from the shop to a jobsite to a supply house.
How often a short report is caught mid-handover
- Report interval
- Every 5 minutes = 300 seconds
- Time connected per report (assumed)
- About 2 seconds
- Share of time connected
- 2 / 300 ≈ 0.7%
- A cell change at a random moment while driving
- Lands during a transfer about 0.7% of the time
- Where mobility really matters
- Long transfers, downlink commands and reselecting quickly after each move, more than the small reports themselves
The 2-second connection time is an assumption to show the arithmetic; it varies with signal and network settings. The point holds: brief reports rarely straddle a handover, but a 5-minute download on a moving device often does.
How do PSM and eDRX save power, and what do they cost?
Both standards save power by letting the radio stop listening, and the cost is that the network cannot reach the device while it sleeps. Power Saving Mode (PSM) is a deep sleep. Extended discontinuous reception (eDRX) is a series of short naps. Both are available on LTE-M and NB-IoT, and the GSMA recommends both as baseline features.
- PSM
- After sending, the device listens for a short active time (timer T3324), then sleeps until its next periodic update (timer T3412) while staying registered, so it does not have to re-attach. The GSMA gives about 413 days as the longest possible sleep and 186 minutes as the longest active time. The device can still send at any moment.
- eDRX
- The device wakes on a regular cycle to check for messages, then switches its receiver off again. The GSMA describes it as suited to cases where being unreachable for several seconds to a few hours is acceptable, and as a compromise between reachability and power.
The device asks for timer values, but the network decides what to grant, and the GSMA notes networks may override requests or enable neither feature. It also recommends operators buffer at least the last 100-byte downlink packet while a device sleeps, so a short command is held rather than lost.
How long a command waits to reach a device that reports every 5 minutes
- PSM, active window after each report (assumed)
- 10 seconds listening, then asleep until the next report
- Worst-case wait with PSM
- 300 − 10 = 290 seconds, nearly 5 minutes
- Average wait with PSM
- Roughly half of 290 ≈ 2.4 minutes
- eDRX with a 20-second cycle (assumed)
- Worst case ≈ 20 seconds, average ≈ 10 seconds
- The trade-off
- PSM saves the most power; eDRX keeps the device reachable within seconds
Timer values here are examples, not any carrier's settings. Uplink is never delayed: the device sends whenever it has something to send, in either mode.
How far does each one reach into basements and pits?
NB-IoT reaches deeper than LTE-M in the networks actually deployed today. Both use coverage enhancement, which repeats transmissions so a weak signal can still be decoded, but the GSMA's figures put the deepest commonly available level well apart.
- NB-IoT: coverage enhancement takes maximum coupling loss from 144 dB up to 164 dB, with up to 128 repetitions at the deepest level in normal use. The GSMA recommends all three levels be supported.
- LTE-M: CE Mode A, which every LTE-M device must support, adds about 5 dB with up to 32 repetitions. Mode B adds about 15 dB with up to 2,048 repetitions, but the GSMA reports no operator known to have implemented it, and no device known to support it, as of 2025.
What 20 dB of extra reach means
- Decibels to power ratio
- Every 10 dB is a factor of 10
- NB-IoT at 164 dB vs 144 dB
- 20 dB = 10 × 10 = 100 times weaker signal still usable
- LTE-M CE Mode A, about +5 dB
- 10^0.5 ≈ 3.2 times weaker signal still usable
- In practice
- NB-IoT can hold on in spots where LTE-M drops: a parking level below grade, an elevator pit, a mechanical room behind concrete
Repetition costs energy and time. The GSMA notes LTE-M latency rises to a few seconds in CE Mode A and NB-IoT to several seconds in extended coverage.
Deep coverage only helps if the data can wait. A device that stores its readings in a dead spot and uploads them on reconnect, with the original timestamps, loses nothing even when neither standard can get a signal out. Coverage checks for real sites are covered in cellular badge trackers.
Do carriers support both LTE-M and NB-IoT?
Some carriers support both, some support one, and support differs by country and changes over time. The GSMA counted more than 140 NB-IoT networks and 129 LTE-M networks worldwide as of October 2025, and keeps a deployment map by country and operator.
Features vary even when the radio is supported. The GSMA notes that many operators enable SMS on LTE-M but not on NB-IoT, that VoLTE on LTE-M is not widely deployed, and that different PSM and eDRX settings between networks change how a device behaves and how long its battery lasts, especially when roaming.
- Ask each carrier, in writing, whether it supports LTE-M, NB-IoT or both in every market where you work.
- Ask whether either network has an announced retirement date. Carriers have retired networks before.
- Ask which PSM and eDRX timer values the network grants, since it can override what the device requests.
- Ask whether the device can switch between LTE-M and NB-IoT if one is unavailable.
- For devices that cross borders, ask about roaming support for the specific technology, not just the carrier.
On lifespan, the GSMA guide says both technologies form part of the global 5G standard and are expected to remain in service well into the 2030s.
Which one suits a worn badge that moves between jobsites?
LTE-M, in most cases, because a worker's badge moves all day and handover is part of LTE-M's baseline. NB-IoT earns its place where devices sit still in deep coverage and send very little. Score your own use against the requirements below.
| Requirement | Why it matters on a crew | Better fit |
|---|---|---|
| Moves between cells several times a shift | Shop, jobsite, supply house and back, often by truck | LTE-M |
| Reachable for a remote command within seconds | The office pings or restarts a badge | LTE-M with eDRX; either with short timers |
| Firmware updates over the air | A fleet of badges updated without collecting them | LTE-M |
| Reports from below-grade levels | Parking decks, pits, mechanical rooms | NB-IoT reaches deeper; store and upload covers both |
| Small reports every few minutes | Location and battery, a few hundred bytes each | Either |
| Many carriers and markets | Crews that travel to out-of-state work | Whichever your carriers support; a device that can use both is safest |
How ZeroBadge handles this
The ZeroBadge badge has its own cellular connection. It never uses the worker's phone, data plan or the site's Wi-Fi password, and nothing is installed on any jobsite. It reports about every 5 minutes, and if signal drops, reports are stored on the badge and uploaded on reconnect with their original timestamps. Badges are powered off between shifts.
For location, it uses GPS outdoors, Wi-Fi positioning indoors and cellular continuity in between, labelled low confidence, and every reading stores its method and confidence. Ask for the badge specification sheet with your quote for the radio technology and supported carriers. More on the hardware: the ZeroBadge badge.
Frequently asked questions
Is LTE-M or NB-IoT better for a tracker that moves?
Does NB-IoT have better coverage than LTE-M?
Does LTE-M use more battery than NB-IoT?
Can a device use both LTE-M and NB-IoT?
Will LTE-M and NB-IoT be shut down like 3G?
Sources
- 1.Mobile IoT Deployment Guide (February 2026): PSM, eDRX, coverage enhancement, mobility, SMS, network counts · GSMA
- 2.What is the difference in data throughput between LTE-M/NB-IoT and 3G or 4G? · GSMA
- 3.Mobile IoT deployment map by country and operator · GSMA
- 4.The Cellular Internet of Things (EC-GSM-IoT, LTE-M and NB-IoT in Release 13) · 3GPP
- 5.Standardization of NB-IOT completed (Release 13, June 2016) · 3GPP
Keep reading
- The badgeCellular badge trackersCellular versus BLE and LoRaWAN badges, and the checks to run before you buy.
- The badgeWorker tracking without gatewaysWhy nothing needs to be installed on a jobsite to know who was there.
- GuideGPS vs Wi-Fi vs cellular accuracyWhat each location method can tell you, and how far apart jobsites must be.
- GlossaryWhat is LTE-MThe term defined, in plain words.
- GlossaryWhat is NB-IoTThe term defined, in plain words.
- SolutionMulti-jobsite time trackingSite transfers, transit and supply runs inside one shift record.
