Last verified 2 November 2026.
An IoT asset tracker needs three things: a way to work out where it is, a network that carries that position to your software, and a platform that manages the connectivity once devices are deployed. Location usually comes from GNSS (GPS and its equivalents). The network is the harder choice. For most mobile assets the shortlist is LTE-M, NB-IoT, Cat-1bis, 5G RedCap or satellite, often combined with more than one carrier.
No technology wins everywhere. A container crossing oceans, a rental scooter and a truck with a dashcam have different needs, so choose the network from the use case and not from the SIM you already have. This guide covers the options, a requirements matrix by use case (including supply chain and logistics trackers), failover and SIM steering, roaming rules, battery life and what connectivity really costs. For the platform side, see our guide to IoT connectivity management platforms.
Where projects fail. Failed tracking deployments are rarely down to the GPS chip. They usually trace back to coverage gaps on real routes, roaming restrictions, battery drain from poor signal, or a network chosen before anyone had written down how the asset moves.
Location and connectivity are two different jobs
GNSS (Global Navigation Satellite System) is the family of satellite positioning systems that includes GPS, Galileo, GLONASS and BeiDou. A GNSS receiver in the tracker calculates where the asset is. It does not send anything. A cellular or satellite link carries that position, plus sensor readings, to your application.
So the real design question is not whether to use GNSS but how to pair it with a connection that gets the data out at an acceptable battery and cost. GNSS needs a view of the sky, which is why a pallet deep inside a warehouse or a container stacked in a yard may not get a fix. Trackers for those cases often send their last known position, use a different positioning method, or rely on a short-range tag read by a gateway. RFID is the usual example inside buildings: a passive tag is read at short range by a reader, while a GPS tracker covers the open road. They complement each other and are not alternatives.
Connectivity options for trackers
The right network depends on how often the asset moves, how much data it sends, how long the battery must last and where it operates. The table is a starting point and uses relative terms on purpose: figures vary by operator, module and configuration. For a deeper comparison of the low-power standards, read NB-IoT vs LTE-M vs 5G RedCap.
| Technology | Throughput | Power use | Moving assets | Typical fit |
|---|---|---|---|---|
| LTE-M | Low to moderate | Low | Designed for it | Trucks, trailers, cold chain, mobile cargo |
| NB-IoT | Very low | Lowest | Weaker, varies by operator | Fixed or slow assets, parking, metering |
| Cat-1bis | Up to 10 Mbps downlink, 5 Mbps uplink (peak) | Moderate to high | Yes | Vehicles and powered equipment |
| 5G RedCap | High | Moderate to high | Yes | Video, driver monitoring, dashcams |
| Satellite (NTN) | Low and variable | Depends on service | Yes, where there is sky view | Maritime, mining, remote routes |
LTE-M
LTE-M is built for devices that need low power and still move. It supports mobility, which makes it the usual pick for trucks, trailers and mobile cargo, and it can carry firmware-over-the-air updates. For many mobile trackers it is the best balance of battery life, coverage and throughput, provided your operators support it where the asset travels.
NB-IoT
NB-IoT puts power efficiency first. It suits devices that send small messages occasionally and stay put: parking sensors, utility assets, static equipment. Mobility support depends on how each operator implements it, so it is often a poor fit for assets that regularly cross regions or countries.
Cat-1bis
Cat-1bis is an LTE category defined in 3GPP Release 13 that uses a single receive antenna, with peak rates of up to 10 Mbps down and 5 Mbps up. It runs on mainstream LTE networks, which many buyers choose to avoid gaps in LTE-M availability. It draws more power than LTE-M or NB-IoT, so it fits connected vehicles and industrial equipment that report often and have external power.
5G RedCap
RedCap (reduced capability) is a 5G device type introduced in 3GPP Release 17 to sit between low-power IoT and full 5G broadband. It matters for trackers that now send images, diagnostics or video, such as driver monitoring and dashcams. Those workloads need more bandwidth than LTE-M or NB-IoT handle comfortably. Confirm 5G standalone or RedCap support on your target networks before you design around it.
Satellite and NTN
No cellular network covers every shipping lane, mine or offshore site. Satellite closes that gap. 3GPP lists “IoT over NTN” among its Release 17 work, bringing satellite access to the same IoT device families. Many deployments combine the two: use cellular when it is available and fall back to satellite when it is not. The decision is commercial. Compare the cost of losing visibility on a high-value, remote or cross-border asset with the premium for satellite service.
Connectivity requirements by use case
Most buyers are not looking for the best IoT network. They are looking for the one that fits a particular job. Use the matrix as a first pass and then validate on your own routes.
| Use case | Likely network | Data volume | Power priority | Coverage need | Main cost driver |
|---|---|---|---|---|---|
| Container tracking | LTE-M plus satellite | Low to medium | High | Global, ports and ocean | Roaming and satellite usage |
| Fleet and vehicle tracking | Cat-1bis or LTE-M | Medium | Medium | Regional to national | SIM volume |
| High-value cargo | Multi-network LTE-M | Medium | Medium | Maximum reliability | Redundancy |
| Micro-mobility and parking | NB-IoT | Low | Very high | Urban | Device volume |
| Cold chain | LTE-M | Medium | High | Consistent along the route | Sensor reporting |
| Driver monitoring and video | RedCap or Cat-4 class | High | Lower | Continuous | Data consumption |
Container tracking often needs cellular and satellite together to keep visibility across ports, remote stretches and borders. Fleet and vehicle tracking depends on LTE-M or Cat-1bis for continuous movement and regular reports. High-value cargo benefits from multi-network access and failover. Micro-mobility and parking suit NB-IoT because of the small payloads and the focus on battery. Video and driver-safety systems need more bandwidth and point to RedCap or higher LTE categories.
The cheapest network is not automatically the right one. Weigh coverage, reliability, latency, power, mobility and the total cost across the device’s life.
Supply chain and logistics: tracking at each stage
Supply chain tracking is asset tracking with more hand-offs. One shipment can sit in a warehouse, ride a truck, wait in a port and finish on a delivery van, and each stage favors a different tracker and connection. Connected logistics allows companies to trace every event in the chain. That event history can also feed into audit management processes, giving safety and compliance teams a record of what happened and when. Predictive maintenance in logistics also helps teams detect equipment issues that might affect transparency signals. The common failure is the same everywhere: when a tracker loses signal mid-route, dispatch loses context and delays are harder to prevent. If you are also working out the economics of vehicle fleets, our fleet connectivity cost guide goes into that.
| Stage | What is tracked | Connectivity consideration |
|---|---|---|
| Warehouse and yard | Pallets, cages, forklifts, containers | GNSS may not get a fix indoors. Use short-range tags and gateways, or accept last-known position until the asset moves outside. |
| Road freight | Trucks, trailers, load condition | Handover between networks while moving. LTE-M or Cat-1bis, with a SIM that can use more than one carrier. |
| Port and sea | Containers on ships and in stacks | Long gaps without terrestrial coverage. Plan for satellite or store-and-forward reporting. |
| Cold chain | Temperature, humidity, door openings, shock | Timely alerts matter more than throughput. Late data turns an alert into a post-mortem. |
| Last mile | Vans, motorbikes, parcel lockers | Dense urban coverage. Vehicle power allows higher-bandwidth devices and live notifications. |
Sensors extend what a tracker reports beyond position: temperature, humidity, vibration, shock, light exposure, door state and tamper events. Each adds data volume and a reason to wake the radio. For cold chain especially, the value is in alerts that arrive while someone can still act, which is a coverage and reliability question before it is a bandwidth one. The event history these devices produce also gives operations and compliance teams a record of what happened and when.
Two cautions. First, sensor data is only as good as its delivery: gaps in the feed make analytics, including predictive maintenance models, less reliable. Second, a large base of devices needs centralized control, otherwise SIMs disconnect, devices roam unchecked and bills surprise you. That points to the management layer covered below.
Multi-network failover and SIM steering
One of the most overlooked causes of tracking failure is dependence on a single network. Coverage and performance are not the same thing. A device can have several networks available and still stay attached to one preferred carrier because of roaming policy or SIM steering.
What is SIM steering?
SIM steering directs devices toward preferred partner networks. For the connectivity provider this can reduce wholesale cost. For you it can mean a device that keeps trying the preferred network instead of moving to a better one. The consequences include delayed transmissions, packet loss, failed registrations, extra battery use and less accurate tracking. They are hard to diagnose because the device is “connected” yet reports late.
Forbidden network lists
Devices also keep a forbidden PLMN list on the SIM. Under 3GPP TS 23.122, a network that rejects a registration with a “PLMN not allowed” response can be added to that list and is then avoided in automatic network selection. That protects devices from repeated failed attempts, but for a moving tracker it can leave a network blocked after a temporary or configuration-related rejection. Ask providers how rejections are handled and whether you can see which networks each device has tried. Our piece on single-carrier IoT risks covers the wider exposure.
Myth versus reality. A SIM that works in 200 countries does not remove coverage problems. The number of countries on a coverage map says little about whether the device can reach the best network where it actually is.
Why failover matters
Moving assets seldom stay inside one network footprint. A truck may pass through several operator territories in a day, and a container through dozens of countries over its life. Multi-network designs let a device switch carriers when conditions change. They typically combine multi-IMSI SIMs or eUICC-based eSIMs, profile switching and commercial agreements with several carriers. For tracking, treat failover as a business-continuity feature and not an add-on. The eSIM mechanics are explained in SGP.22 vs SGP.32.
Global coverage, roaming and regulation
Many IoT deployments have relied on permanent roaming to work abroad: a SIM from one country used in another for years. Some regulators restrict that. Cullen International reports that Brazil is an outlier among the eleven countries it surveyed, with Anatel reinforcing its long-standing ban on permanent roaming in 2025 and applying a stricter regime to IoT connectivity. Other markets differ, so confirm the rules per country before shipping devices there. For a deeper look at the global picture, read global IoT connectivity in 2026.
The practical consequence is that connectivity must be compliant as well as functional. A local-profile approach helps: an eSIM-capable device can download and activate a local operator profile when needed, instead of roaming on one home profile indefinitely. Done well, that supports compliance, can improve coverage and can lower roaming cost. Broad operator counts still need testing. Evaluate failover, local-profile support and real network quality in each region where you deploy. For device makers building global products, local-profile capability is becoming a requirement. See eSIM orchestration for global IoT.
Battery life and connectivity
A tracker that needs frequent battery changes is expensive to run, especially across a large fleet or remote sites. Network choice matters, but it is one of several levers.
- Network type. NB-IoT is optimized for infrequent, small messages and generally gives the longest battery life. LTE-M stays efficient while supporting movement. Cat-1bis and RedCap draw more power in return for bandwidth.
- Power saving. PSM (Power Saving Mode) lets a device sleep for long periods while remaining registered, avoiding a full reattach. eDRX (extended discontinuous reception) lengthens the interval between wake-ups to check for incoming messages. Both are optional and have to be supported by the operator network as well as the device.
- Signal quality. In weak coverage a device transmits at higher power and may repeat registration attempts, which costs energy. Aggressive steering can drain a battery that the hardware was tuned to protect.
- Reporting interval. This often matters more than the radio. A tracker reporting every five minutes will not last as long as an otherwise identical one reporting every four hours.
Manufacturers publish multi-year battery figures, but those depend on message size, reporting interval and coverage. We do not quote a number here. Ask for the test conditions behind any claim and repeat the test on your own routes. More frequent data is not always better data: set the reporting interval from the decision it supports.
What tracker connectivity costs
Hardware prices are visible. Connectivity prices are usually less so, because providers advertise a monthly SIM rate and say little about the rest. Several things set the total:
- Data usage. A low-data GPS tracker costs far less to run than a device sending video.
- Coverage. Global deployments usually add roaming and multi-region costs.
- Redundancy. Multi-network access improves reliability and can raise cost.
- Lifecycle management. Provisioning, monitoring, diagnostics and support all add to the total cost of ownership.
| Model | Best for | Advantage | Watch for |
|---|---|---|---|
| Per-SIM plans | Small fleets | Predictable cost per device | Unused data on quiet devices is wasted |
| Pooled data | Large fleets | Unused allowance from one device offsets heavier users | Needs active monitoring so one device cannot drain the pool |
The cheapest SIM can be the costliest choice if poor coverage causes outages or truck rolls. For rates and worked examples, see the IoT connectivity cost guide and the IoT SIM cards guide.
Building and scaling a tracking deployment
Managing connectivity by hand stops working somewhere between hundreds and thousands of devices. Scaling takes automation, centralized visibility and lifecycle control: activation, usage monitoring, troubleshooting, and the ability to change a plan or carrier without touching hardware.
Decide connectivity during device design, because module choice sets network compatibility, power draw, certification and future options. For device makers, eSIM provisioning allows one hardware variant to ship worldwide and activate locally, which simplifies manufacturing and compliance. For fleet operators, a central platform is what keeps activations, usage and diagnostics manageable. Our guide to single-pane-of-glass connectivity management describes what that looks like.
Spenza provides multi-carrier connectivity management through one platform, with centralized visibility, lifecycle management, eSIM orchestration and carrier flexibility so a deployment is not tied to a single network. Whatever platform you evaluate, ask for evidence on the points above: which networks a device used on a test route, how steering is set, and how a profile change is made.
Conclusion
Choose the network from the use case, not the other way around. LTE-M, NB-IoT, Cat-1bis, RedCap and satellite each have a real role. The answer depends on how assets move, how much they send, how long batteries must last and where they travel, from a warehouse to a port to a delivery route.
Teams that plan for multi-network failover, global compliance and long-term fleet economics avoid the hidden costs of coverage gaps, steering problems and carrier lock-in. Write down the asset, its route and its failure tolerance first, then compare providers against those requirements.
Asset tracking connectivity FAQs
What is the best connectivity for asset tracking?
There is no single best option. LTE-M suits most moving assets that need long battery life, NB-IoT suits stationary or slow-moving assets that send small messages, Cat-1bis suits vehicles and equipment on external power, and RedCap suits video and driver-monitoring devices. Add satellite where cellular coverage stops. Decide from how the asset moves, how much data it sends and where it travels.
LTE-M or NB-IoT: which is better for trackers?
LTE-M is the safer default for assets that move, because it is designed to keep a session going across cells and supports higher throughput, including over-the-air firmware updates. NB-IoT is built for the lowest power and the smallest messages, and fits fixed or slow-moving assets. Check that your target operators actually support the one you choose, because support varies by country and by operator.
Is Cat-1bis a good choice for asset trackers?
It is a good choice when the tracker has external power or a large battery and needs more throughput than LTE-M or NB-IoT offer. Cat-1bis is an LTE category with peak rates of up to 10 Mbps downlink and 5 Mbps uplink, and it runs on ordinary LTE networks. It uses more power than the low-power options, so it fits vehicles and equipment better than sealed battery tags.
How long does an asset tracker battery last?
It ranges from months to several years, and no network technology fixes the number on its own. Reporting interval, signal quality, message size, how often the device must reattach to a network and whether PSM and eDRX are enabled all decide it. Ask the device maker for the test conditions behind any battery figure and repeat the test on the routes you actually run.
Do asset trackers work globally?
They can, but a global coverage claim is not enough. You need a roaming or local-profile arrangement that is permitted in each country, devices that attach to the best available network, and a way to see where each device is registered. Some countries restrict long-term permanent roaming for IoT, so check each market before shipping devices there.
What is SIM steering and why does it matter for tracking?
SIM steering directs a device to a preferred partner network, which can lower the provider’s wholesale cost. If the device keeps retrying that network while a better one is available, you can see delayed reports, failed registrations and extra battery drain. Ask any provider how steering is configured and whether you can see and change the networks a device uses.
Do I need a multi-network SIM for asset tracking?
For assets that cross regions or borders, usually yes. A single-network SIM leaves the device with whatever that one operator covers. A multi-network SIM or an eSIM with several profiles lets the device attach elsewhere when coverage drops. For a tracker that never leaves one site, a single network can be enough.
Does cold-chain or supply chain tracking need different connectivity from fleet tracking?
Often yes. Cold-chain trackers must deliver sensor readings and alerts such as temperature excursions or door openings on time, so consistent coverage matters more than throughput. Trailer and container trackers need coverage across borders and ports. Last-mile tracking suits vehicle-powered devices with more bandwidth. Match the network to the failure you cannot afford.
