Short answer
The list of network generations a device can attach to is a statement about how long it will work. A device that lists only GSM and 3G depends on 3G staying in service; the FMC003 listing is 4G LTE Cat 1 with 3G and 2G fallback. When an operator retires a generation, only devices that can reach a newer layer survive the change.
Key takeaways
- A fallback list is a service-life statement: the device lives as long as its newest supported layer.
- Check the radio generations of every device you buy: a GSM/3G-only listing depends on 3G; the FMC003 listing is 4G LTE Cat 1 with 3G and 2G fallback.
- Retirement is an operator decision per market, so the same device can outlive itself in one country and not another.
- LTE-M and NB-IoT were specified in 3GPP Release 13, so an LPWA device is on a newer layer than a 2G one.
- Plan replacement from the newest supported generation, not from the hardware warranty.
01The row nobody reads carefully
On most tracker datasheets there is a line listing the cellular generations the device can attach to, and it is usually read as a reassurance about coverage. It is more useful read as a date. A device attaches to whatever it supports and no more, so the newest generation on that list is the last layer that will still be there when the older ones are gone. Two example listings make the contrast plain. One device lists GSM and 3G only. The FMC003 listing states 4G LTE Cat 1 with 3G and 2G fallback. Both can be capable devices for their roles today, but they are not equivalent purchases in a five-year frame, because one of them has a fourth-generation layer to fall back to and the other does not. The same check applies to every device in a quote, trackers and smart locks alike: ask the supplier to confirm in writing the supported generations for the exact model and hardware version you will receive.
02Why operators retire a generation at all
Spectrum is finite, and a generation left running consumes bands and base-station capacity that a newer one would use more efficiently. That is the whole economic argument, and it does not require any hostility toward legacy devices to be compelling: an operator carrying an old layer for a shrinking population of devices is spending real money on capacity it could refarm. The consequence for asset owners is that the decision sits entirely outside their control and outside the vendor's. No manufacturer can extend the life of a 2G-only device by improving it, because the thing being withdrawn is not in the device. This is why a fallback list matters more than most hardware specifications: it is the one line on the datasheet that describes a dependency on somebody else's roadmap.
03Retirement is per market, not global
A second property complicates fleet planning in the GCC specifically. Each operator in each country decides its own schedule, so a generation can be gone in one market and healthy in the next. For a domestic fleet that is a single dependency to track. For an asset that crosses borders it is several, and the binding one is whichever market retires first, a cross-border truck loses reporting in the country that moved earliest, while the same device continues working at home. The same logic applies within a country when two operators diverge. This is exactly the situation where a dual-SIM device is genuinely useful and also genuinely limited: two subscriptions add operator redundancy, but they cannot add a radio layer the device does not have.
04What LPWA changes about the timeline
The low-power radio classes sit on a newer foundation, and that is a service-life argument rather than only a battery one. Both LTE-M and NB-IoT were specified in 3GPP Release 13 and continued in Releases 14 and 15, which places them on the LTE generation rather than beneath it. A device on either of those layers is therefore not dependent on 2G or 3G remaining in service at all. The trade-off is the one that always applies to LPWA: Cat NB1 peaks at 26 kbit/s down and 66 kbit/s up in a 180 kHz channel, and Cat-M1 at 1 Mbps in 1.4 MHz, so the newer foundation comes with a narrower pipe. For a scheduled reading that is an easy exchange. For a device sending continuous records it is not, which is why the trackers we list are Cat 1 rather than Cat M1.
05What the failure actually looks like
A retirement rarely presents itself as a clean stop, which is why it is often diagnosed as something else. What operations teams typically see first is a rising rate of devices that report intermittently, attach slowly, or hold a session for a shorter time than they used to, because as an operator refarms spectrum, the old layer thins before it disappears. A tracker with a fallback list will drop to its next layer and keep working with worse latency, which looks like a performance complaint rather than an infrastructure change. A device with nothing below its only layer simply goes quiet. Knowing the fallback list in advance is what lets a team read that pattern correctly instead of replacing SIMs, reseating antennas and opening vendor tickets against a fault that is not theirs.
06How to plan a fleet you already own
Start with an inventory keyed on the newest supported generation rather than on model or purchase date, because that is the field that predicts retirement. Group the fleet into devices whose newest layer is 4G or above, devices whose newest layer is 3G, and devices that are 2G only, and treat those three groups as separate replacement programmes with separate urgency. Then map each group against the markets it operates in, since the binding constraint for a cross-border asset is the earliest retirement it will encounter. Finally, decide replacement timing from that map instead of from the hardware's condition. A device in excellent physical shape whose only layer is being withdrawn is at the end of its service life, and a device on 4G with a worn enclosure is not.
07What to require of the next purchase
Three requirements do most of the work on a new specification. Require the full attachment list in writing, with the generation and the category, not simply the word 4G, since Cat 1 and Cat M1 are different radio classes with different operator support even inside the same generation. Require at least one layer below the newest, because a single-layer device has no graceful degradation when a cell is congested rather than retired. And require the answer to be stated per market you intend to operate in, since a device is only as current as the newest network it can find where it actually sits. The FMC003 listing satisfies the first two by naming 4G LTE Cat 1 with 3G and 2G fallback; the third is a question for the operator, not the manufacturer.
| Question | A GSM / 3G-only device | Teltonika FMC003 |
|---|---|---|
| Attachment list | GSM / 3G | 4G LTE Cat 1 / 3G / 2G |
| Newest supported layer | 3G | 4G LTE Cat 1 |
| Layers below the newest | One (GSM) | Two (3G, 2G) |
| Survives a 2G withdrawal | Yes, via 3G | Yes, via 4G or 3G |
| Survives a 3G withdrawal | No | Yes, via 4G |
| Second SIM helps after retirement | No, no newer layer to reach | Not needed for this reason |
| What bounds its service life | Whichever market retires 3G first | The eventual 4G horizon |
Figures and sources
- Teltonika FMC003 cellular generations, including its fallback layers: 4G LTE Cat 1 / 3G / 2G (Source: ENTEK.AI product catalogue, as of 2026-08-31)
- 3GPP release in which the low-power radio classes were specified, a newer foundation than 2G: Release 13, continued in 14 and 15 (both LTE-M and NB-IoT) (Source: GSMA LTE-M and NB-IoT Deployment Guides to Basic Feature Set Requirements, v3 (June 2019), as of 2026-08-31)
- Cat-M1 device bandwidth and peak rate, the pipe that comes with the newer layer: 1.4 MHz bandwidth; 1 Mbps peak in DL and UL (Source: GSMA LTE-M Deployment Guide v3 (June 2019), as of 2026-08-31)
- NB-IoT peak data rates by 3GPP device category, and its occupied bandwidth: Cat NB1: DL 26 kbit/s, UL 66 kbit/s multi-tone, half duplex; 180 kHz occupied (Source: 3GPP device category specification table (Narrowband IoT), as of 2026-08-31)
- Teltonika model-letter convention, FMC denotes Cat 1, not Cat M1, inside the same generation: FMC003 described as "LTE CAT1 advanced plug and play tracker" (Source: Teltonika Telematics Wiki, FMC003, as of 2026-08-31)
- Teltonika model-letter convention, FMM denotes Cat M1 (LTE-M), a different radio class: FMM003 described as "LTE CAT M1 advanced plug and play tracker" (Source: Teltonika Telematics Wiki, FMM003, as of 2026-08-31)
- Saudi operator low-power technology split in the GSMA commercial launch register: Mobily: LTE-M; STC: NB-IoT, non-overlapping (Source: GSMA Mobile IoT Commercial Launches (data last updated November 2025), as of 2026-08-31)
Questions
How do I tell how long a tracker will keep working?
Read the newest generation on its attachment list, because that is the last layer that will still be there once the older ones are withdrawn. A device that lists only GSM and 3G has 3G as its newest layer; the FMC003 listing is 4G LTE Cat 1 with 3G and 2G fallback, so its newest layer is 4G.
Will a second SIM keep an old device alive after a network is retired?
No. Two subscriptions add operator redundancy, but they cannot add a radio layer the device does not have. If a device supports only GSM and 3G and both operators in a market have withdrawn 3G, neither SIM has anything left to attach to.
Is "4G" on a datasheet enough detail?
No, because different radio classes sit inside the same generation with different operator support. The Teltonika wiki describes FMC003 as an LTE Cat 1 tracker and FMM003 as an LTE Cat M1 tracker, and Cat M1 is LTE-M, a technology an operator may or may not have launched. Ask for the generation and the category.
Does an LPWA device have a longer service life?
On the network dimension, yes: LTE-M and NB-IoT were specified in 3GPP Release 13, so they sit on the LTE generation rather than beneath it and do not depend on 2G or 3G at all. The cost is throughput, Cat NB1 peaks at 26 kbit/s down in a 180 kHz channel, which suits a reading but not a continuous record stream.