LoRaWAN vs NB-IoT for Fleet Asset Tracking

Jul 6, 2026 Resolute Dynamics

A Low-Power Wide-Area Network (LPWAN) is a class of wireless network that trades data rate for range and battery life, letting a fleet track thousands of low-value or non-powered assets for years on a single battery — a job that real-time cellular telematics is too power-hungry and too costly to do at scale.

A trailer sitting in a yard, a shipping container crossing a region, or a piece of equipment moving between sites does not need a live data stream; it needs its location reported reliably a few times a day for years without a battery change.

This guide explains what an LPWAN is, how LoRaWAN and the cellular options NB-IoT and LTE-M work, how they compare for fleet asset tracking, how the trackers actually find their location, and how to design a large-scale deployment.

This article states the position as of mid-2026. Connectivity standards and coverage change, so version- and figure-specific facts carry a source so the page ages honestly.

What Is a Low-Power Wide-Area Network (LPWAN)?

An LPWAN is a wireless network built for devices that send small amounts of data over long distances while consuming very little power. It sits between short-range technologies such as Bluetooth and Wi-Fi, which cannot reach across a region, and high-bandwidth cellular, which drains batteries and costs too much per device to deploy across a large asset base.

The whole category exists to serve one profile: many devices, wide area, tiny payloads, and years of battery life.

The LPWAN Tradeoff — Range and Battery over Bandwidth

The defining LPWAN tradeoff is that it sacrifices bandwidth to gain range and battery life. An LPWAN device transmits at data rates measured in kilobits per second rather than the megabits of cellular, and in exchange it reaches many kilometres and runs for years on a small cell.

That tradeoff is exactly right for asset tracking, where the payload is a location fix and a status flag, not a video feed or a continuous telemetry stream. Trying to force a high-bandwidth technology into this role wastes power and money; the LPWAN is engineered for it.

Why Asset Tracking Is Different from Real-Time Telematics

Asset tracking reports location periodically, while real-time telematics streams data continuously, and the two demand opposite kinds of network. A powered vehicle running safety and control systems needs the low latency and high throughput of cellular or a private network — the profile examined in the guide to private LTE and 5G networks for fleet operations.

A non-powered asset needs the opposite: minimal power, minimal data, maximum battery life, reported on a schedule. Deciding how often an asset reports and how much it sends is the same design question addressed in the comparison of event-driven versus continuous data capture for fleets, and for LPWAN assets the answer sits firmly on the periodic end.

LoRaWAN — Unlicensed, Enterprise-Owned Networks

LoRaWAN is an open LPWAN standard that runs on unlicensed spectrum and lets an organization own its entire network. Maintained by the LoRa Alliance, it is the LPWAN option that gives a fleet the most control, because the gateways and the network server belong to the operator rather than a mobile carrier. That ownership is its defining characteristic and the source of both its advantages and its obligations.

How LoRaWAN Works

LoRaWAN separates the radio layer from the networking layer: the LoRa physical layer carries the signal, and the LoRaWAN protocol manages the network. LoRa is a proprietary modulation derived from Chirp Spread Spectrum (CSS), patented by Semtech, which spreads a narrowband signal across a wider channel to achieve long range and strong resistance to interference.

On top of it, the LoRaWAN protocol defines a secure, bidirectional network in a star-of-stars topology: end devices transmit to gateways, and gateways relay the traffic to a central network server.

Devices fall into three classes — Class A uses the least power and only listens briefly after transmitting, Class B adds scheduled receive windows, and Class C listens continuously at the highest power — so the class is chosen to match how quickly an asset must be reachable.

Spectrum, Range, and Battery Life

LoRaWAN runs on unlicensed sub-GHz spectrum, reaches several kilometres, and lasts years on a single small battery. It operates in regional ISM bands — 868 MHz in Europe and 902 to 928 MHz in North America — with typical range of 2 to 5 kilometres in dense urban areas and 10 to 15 kilometres in rural line-of-sight.

Battery life reaches 5 to 10 years on a single AA-class lithium cell for a device sending a small uplink every half hour, which is what makes it viable to deploy on assets that are hard to reach and expensive to service.

Because the spectrum is unlicensed, regional duty-cycle limits cap how often a device may transmit, reinforcing the periodic-reporting model.

Public vs. Private LoRaWAN Networks

A fleet can either build its own private LoRaWAN network or use a public one, and the choice depends on where the assets are. A private network of a few gateways covers a depot, yard, or port completely and carries no per-device connectivity fee, which suits a concentrated asset base under the operator’s control.

A public LoRaWAN network extends coverage across a wider area without the operator building infrastructure, at the cost of a service relationship. Many fleets run private gateways where their assets congregate and rely on public or cellular coverage for assets that roam beyond them.

NB-IoT and LTE-M — Licensed Cellular LPWAN

NB-IoT and LTE-M are cellular LPWAN standards that run on licensed operator spectrum and need no gateways of the operator’s own. Both were standardized by the 3GPP as part of LTE Release 13 in June 2016, and both connect devices directly to the existing mobile network, so coverage comes from the carrier rather than from infrastructure the fleet installs. The distinction between the two decides which suits a moving asset.

How NB-IoT Works

NB-IoT is a narrowband cellular standard that connects devices directly to mobile base stations over licensed spectrum, with deep coverage and no gateways to deploy. It occupies a narrow 200 kHz channel and can be deployed in three modes — standalone, in-band within an LTE carrier, or in an LTE carrier’s guard band — usually as a software upgrade to existing cellular infrastructure.

Its narrowband design gives it a strong link budget and excellent penetration into basements, deep indoors, and dense urban environments, and because it uses licensed spectrum it has no duty-cycle limit, so it can report more frequently than LoRaWAN when needed. Battery life reaches around ten years for infrequent small transmissions.

The Mobility Question — Why LTE-M Often Beats NB-IoT for Moving Assets

NB-IoT is optimized for static devices, so for assets that move, LTE-M is usually the better cellular choice. NB-IoT is limited to idle-mode cell reselection and is not well optimized for mobile asset tracking, because it lacks the seamless cell-to-cell handover that a moving device needs.

LTE-M, its Release 13 sibling, supports mobility and handover at vehicle speeds and higher data rates, which is why it is the recommended cellular LPWAN for anything that moves, including asset tracking and vehicle telematics.

For a fleet, this is a decisive nuance that generic comparisons miss: NB-IoT fits fixed or slow-moving assets, while LTE-M fits assets that travel across the network.

Coverage, Cost, and the SIM/eSIM Model

Cellular LPWAN delivers wide-area coverage immediately by reusing the carrier’s network, in exchange for a per-device subscription and a SIM. Because NB-IoT and LTE-M ride existing national and international cellular footprints, they cover assets that roam across regions without the fleet building anything, which is their central advantage over private LoRaWAN.

The cost is an ongoing connectivity subscription per device and dependence on the operator, and the model increasingly uses embedded SIMs (eSIM) so that a device can be provisioned and re-provisioned across carriers without swapping a physical card — useful for assets that cross borders.

LoRaWAN vs. NB-IoT vs. LTE-M for Fleet Asset Tracking

The choice among the three turns on who owns the network, whether the asset moves, how wide the coverage must be, and the cost model. No single technology wins every case, and large fleets frequently mix them — LoRaWAN where assets concentrate and the fleet wants control, cellular where assets roam.

When Each Fits a Fleet Asset-Tracking Deployment

Match the technology to where the assets live and whether they move. LoRaWAN fits assets concentrated on sites the fleet controls — trailers in a yard, containers in a terminal, equipment on a campus — where owning the network removes per-device fees.

NB-IoT fits fixed or slow-moving assets that need deep indoor coverage and only report occasionally. LTE-M fits assets that travel widely and change cells frequently, where its mobility and handover matter more than the lowest possible power draw. A large fleet with a mix of these profiles deploys more than one.

How LPWAN Trackers Determine Location

An LPWAN tracker finds its position in one of three ways, and the choice is governed by a tradeoff between accuracy and battery life. Location is the entire purpose of asset tracking, but the most accurate method is also the most power-hungry, so the right choice depends on how precisely a given asset must be located and how long its battery must last.

On-Device GNSS/GPS — Accurate but Power-Hungry

On-device GNSS gives the most accurate position but consumes the most power, shortening battery life. A satellite receiver on the tracker fixes location to a few metres, but an asset-tracking device has to work for years on a small battery, which is hard to achieve if power-hungry GNSS hardware is added and its fixes are transmitted regularly.

GNSS also struggles indoors, where satellite signals do not penetrate. It is the right choice when precise outdoor position genuinely matters and the battery budget can absorb it.

Network-Based Geolocation — Lower Power, Lower Accuracy

Network-based geolocation derives position from the network itself, using far less device power at the cost of accuracy. LoRaWAN offers two network methods: coarse RSSI-based positioning, accurate to roughly 1,000 to 2,000 metres, and finer Time Difference of Arrival (TDoA), accurate to roughly 20 to 200 metres depending on conditions.

TDoA is network-assisted — a position is calculated when three or more time-synchronized gateways receive the same uplink and multilaterate from the timing differences — so the device itself spends almost no extra energy.

Cellular networks offer analogous methods such as Cell-ID and OTDOA. Because network-based positioning consumes less power on the device than an onboard GPS receiver, it extends battery life for assets where approximate location is enough.

Wi-Fi Scanning and Hybrid Approaches

Wi-Fi scanning and hybrid designs sit between GNSS accuracy and network-based frugality. A tracker can scan nearby Wi-Fi access points and send their identifiers over the LPWAN to be resolved against a database, achieving roughly 15 to 30 metre accuracy in areas dense with access points, including indoors where GNSS fails.

Hybrid trackers combine methods — GNSS outdoors, Wi-Fi or network-based positioning indoors, and low-power scan resolving in the cloud — to balance accuracy and battery across the varied places an asset travels.

Choosing Accuracy vs. Battery Life for the Asset

The location method is chosen per asset by weighing how precisely it must be found against how long its battery must last. A high-value asset that must be pinpointed justifies GNSS and a shorter service interval; a low-value asset that only needs to be known within a yard or a city block is better served by network-based positioning and a battery that lasts years.

Setting this deliberately, asset class by asset class, is what keeps a large deployment both useful and maintainable.

Designing a Large-Scale Fleet Asset-Tracking Deployment

Designing a large-scale deployment comes down to four decisions: which technology each asset uses, how often it reports, how its data reaches the platform, and how it fits alongside real-time telematics. Getting these right is what lets a fleet track thousands of assets economically instead of over-engineering each one.

Match the Technology to the Asset

The first decision is matching connectivity to the asset’s value, mobility, and location. Powered vehicles that need live telematics stay on cellular or a private network; non-powered or low-value assets — trailers, containers, tools, generators — go on LPWAN, with LoRaWAN where they concentrate on owned sites and LTE-M where they roam.

Segmenting the asset base this way avoids paying for capability an asset does not need and prevents starving one that does.

Location Cadence, Payload, and Battery Budget

Reporting cadence and payload size are the levers that set battery life, so they are chosen against a battery budget per asset. A tracker reporting once an hour lasts far longer than one reporting every minute, and a small status payload costs less energy than a rich one, so the cadence is set to the slowest rate that still meets the operational need.

This is the same discipline covered in the comparison of event-driven versus continuous data capture for fleets: send on a schedule or on an event, not continuously, and reserve frequent reporting for the assets that truly need it.

Backhaul, Integration, and the Data Platform

Once assets report, their data has to reach and integrate with the fleet platform. LoRaWAN traffic flows from gateways to a network server and onward to the application; cellular LPWAN data flows through the carrier to the platform — a path examined in the analysis of vehicle-to-cloud connectivity architecture.

At scale, thousands of assets reporting on schedule produce a steady event stream that is handled by the backbone described in the guide to real-time streaming architectures for fleet telemetry, and the interfaces that expose it consistently are covered in the telematics API design best practices guide.

Normalizing asset data alongside vehicle data into one model is the same challenge addressed in the guide to vehicle data capture architecture for heterogeneous fleets.

How Asset Tracking Complements Real-Time Telematics

LPWAN asset tracking completes the picture that real-time telematics begins, giving a fleet one view of both its powered vehicles and its passive assets. Sensors capture location and status from every asset regardless of the network it uses; that data is connected over the technology that fits each asset; and it feeds the same control and visibility layer that manages the powered fleet.

A fleet extending visibility to trailers, containers, and equipment at scale can talk to Resolute Dynamics about combining asset tracking with its telematics platform.

Frequently Asked Questions

What is the difference between LoRaWAN and NB-IoT?

LoRaWAN is an unlicensed LPWAN where the fleet owns the gateways and network server, while NB-IoT is a licensed cellular LPWAN that runs on a carrier’s network with no gateways to deploy. LoRaWAN offers infrastructure control and no per-device fees; NB-IoT offers immediate wide-area coverage in exchange for a per-device subscription.

Which is best for tracking trailers and containers?

It depends on where they go. For trailers and containers that stay within owned sites such as yards and terminals, private LoRaWAN is cost-effective and controllable; for those that travel widely across regions, LTE-M is usually the better choice because it handles mobility and cell handover, which NB-IoT does not do well.

How long does an LPWAN tracker battery last?

An LPWAN tracker can last several years on a single small battery — around 5 to 10 years for LoRaWAN and roughly 10 years for NB-IoT with infrequent small transmissions. Battery life depends heavily on reporting cadence, payload size, and the location method, since on-device GPS drains power far faster than network-based positioning.

Does LPWAN asset tracking use GPS?

It can, but it does not have to. Trackers may use on-device GNSS/GPS for a few-metre accuracy at higher power cost, or network-based methods such as LoRaWAN TDoA (roughly 20 to 200 metres) and cellular positioning that use far less device power at lower accuracy, or Wi-Fi scanning for indoor location. The method is chosen by weighing accuracy against battery life.

Can LPWAN replace cellular telematics?

No — LPWAN complements cellular telematics rather than replacing it. LPWAN is built for low-power, periodic tracking of assets, while real-time telematics on powered vehicles needs the low latency and throughput of cellular or a private network. A complete fleet platform uses both: cellular for live vehicle data and LPWAN for large-scale asset tracking.