Telenor IoT Goes Live with SGP.32 Today: What It Means and Why It Matters

Today – 17 April 2026 – Telenor IoT begins commercial delivery of SGP.32 SIM cards. This is not another announcement. It is not a roadmap commitment or a proof of concept. Physical SGP.32 SIMs are being shipped to paying customers today.

For anyone watching the SGP.32 market mature, this is a significant date. Telenor IoT is one of the most established names in global IoT connectivity, with over 30 million connected devices in operation and enterprise customers including Volvo Cars, Scania, Hitachi, Verisure, and Great Wall Motors. When an operator at this scale moves from pilot to commercial delivery, the market moves with it.

What Telenor Announced and When

Telenor IoT made the announcement on 27 February 2026 – not coincidentally at the same time as Mobile World Congress was running in Barcelona, where Tele2, IDEMIA and Cisco were also announcing their own SGP.32 commercial launch. February 27 was a busy day for SGP.32 news.

The announcement was specific: SGP.32 SIM cards available for ordering immediately, with deliveries beginning 17 April 2026. The April date has been maintained. Today is that date.

Telenor IoT has history with this standard. They were among the first operators to launch SGP.02 when that standard arrived years ago. They committed to SGP.32 adoption publicly in April 2025, a year before the commercial launch. This is not a reactive move – it is the execution of a planned transition that has been in progress for twelve months.

What Telenor IoT Is Actually Offering

The commercial SGP.32 offering from Telenor IoT is a standardised eSIM SIM card – a physical card with an eUICC that implements the full GSMA SGP.32 v1.2 specification. This means it supports the eIM (eSIM IoT Manager) architecture, server-initiated profile management, and – critically – the open standards that prevent vendor lock-in.

Telenor is explicit about this. Their positioning centres on three things: interoperability, lifecycle flexibility, and regulatory compliance. The SGP.32 standard eliminates compatibility issues that existed with proprietary or non-standardised eSIM approaches. It enables devices to be managed without heavy backend integrations. And it provides a path to inject locally compliant profiles in markets where permanent roaming is restricted – Brazil and Turkey being the most frequently cited examples.

Telenor also offers test agreements for companies wanting to evaluate SGP.32 before committing to large-scale deployment. This is a sensible commercial approach given that the ecosystem is still maturing – hardware certification pipelines take time, and enterprises need confidence before specifying SGP.32 across a new product line.

Why Telenor Matters More Than Most

There have been several SGP.32 commercial announcements in the past twelve months. IDEMIA achieved GSMA certification in April 2025. KPN IoT launched a commercial SGP.32 solution in February 2025. Tele2 IoT, IDEMIA and Cisco announced an end-to-end solution at MWC in March 2026. KORE announced their SGP.32 portfolio in April 2026.

Telenor IoT sits in a different tier of significance for the UK and European market. Their connectivity platform already reaches enterprises in the Nordic and Baltic region, EMEA, the Americas, and APAC. They have been operating IoT connectivity for over 20 years. They are listed in the Gartner Magic Quadrant for Managed IoT Connectivity Services for the eighth consecutive year.

When Telenor adds a standard to their commercial portfolio, enterprises already working with them get SGP.32 capability without changing provider relationships. That is a very different adoption path from the IDEMIA certification story, which required enterprises to actively seek out a new infrastructure partner.

What SGP.32 Enables That Earlier Standards Could Not

For anyone new to the standard, the Telenor launch is a useful moment to explain what SGP.32 actually changes in practice. Earlier eSIM standards – SGP.02 for M2M and SGP.22 for consumer – either required complex SM-SR infrastructure with operator lock-in, or assumed a user would be present to initiate profile changes via QR code. Neither worked well for headless IoT at scale.

SGP.32 addresses both problems. Server-initiated management via the eIM means no user interaction is needed at the device. CoAP transport over UDP means the protocol works on NB-IoT and LTE-M networks where data budgets are measured in kilobytes. Asynchronous operations mean devices in deep sleep can receive profile change instructions and act on them when they next wake.

For Telenor IoT customers deploying in regulated markets, the locally compliant profile capability is the headline feature. Permanent roaming restrictions in Brazil, Turkey, and other markets require devices to use a local operator profile rather than connecting permanently via a foreign SIM. Under SGP.32, this switch happens remotely over the air. Under older standards, it required a physical SIM swap or a proprietary workaround.

Telenor and the Bootstrap Question

One detail that Telenor IoT is well placed to answer is the bootstrap question – how does a device get its first SGP.32 profile before it has any operational connectivity? Telenor has deep experience with SGP.02 bootstrap provisioning across their existing fleet, and their SGP.32 offering will need to bring the same rigour to the newer standard.

The Teltonika and Tele2 partnership gives a useful reference point here – Tele2 IoT provides the bootstrap profile pre-loaded on Teltonika routers, providing initial global connectivity for the first-time provisioning sequence. Telenor IoT is a direct competitor to Tele2 in this space and will need to provide an equivalent bootstrap pathway for SGP.32 devices in their ecosystem.

For enterprises evaluating Telenor IoT SGP.32, the bootstrap question is worth raising directly: what bootstrap profile ships with the SGP.32 SIM, what is the validity period, what networks does it roam on, and what is the recovery path if the initial provisioning fails?

What This Launch Does Not Mean

Being precise about scope matters here. Telenor IoT going live with SGP.32 SIM cards does not mean SGP.32 hardware is widely available or that the ecosystem is fully mature. The bottleneck in SGP.32 adoption has never been the connectivity provider – it has been the device hardware. Certified SGP.32 eUICC chips need to make their way from chip suppliers through module manufacturers and into device designs before SGP.32 can be deployed at the scale that Telenor IoT and the rest of the operator community are building toward.

Telenor acknowledges this directly in their SGP.32 documentation, noting that ecosystem support across device vendors and profile providers continues to mature. They recommend enterprises evaluate compatibility and readiness across their full value chain before committing to SGP.32 for a new deployment.

The significance of today is not that SGP.32 is everywhere. It is that a major operator with genuine enterprise relationships and operational scale has moved the standard from roadmap to reality. That changes the conversation in procurement meetings. When a CTO asks their IoT connectivity provider whether they support SGP.32 and the answer is yes with a commercial product and real customers behind it, the standard moves from emerging to established in enterprise perception.

Frequently Asked Questions

Is Telenor IoT the first operator to commercially launch SGP.32?

No. KPN IoT launched a commercial SGP.32 solution in February 2025 in partnership with IDEMIA. Tele2 IoT, IDEMIA and Cisco announced an end-to-end commercial SGP.32 solution at MWC in March 2026. Telenor is among the first operators to ship physical SGP.32 SIM cards to customers at commercial scale, but it is part of a wave of launches in 2025-2026, not an isolated first.

Can I order Telenor IoT SGP.32 SIMs in the UK?

Telenor IoT operates globally and serves UK enterprise customers. Their sales presence covers EMEA. UK enterprises should contact Telenor IoT directly to discuss SGP.32 SIM availability and test agreement options. The direct route is iot.telenor.com/contact.

Does Telenor IoT SGP.32 work with Teltonika routers?

Teltonika routers currently use SGP.22, managed via RMS. They are not native SGP.32 devices. A Telenor IoT SGP.32 SIM in a Teltonika router would operate as an SGP.22 profile unless Teltonika releases SGP.32-compatible firmware. The two standards are separate architectures – see the standards comparison for the technical differences.

What does SGP.32 mean for permanent roaming restrictions?

SGP.32 enables remote injection of locally compliant operator profiles, which resolves the permanent roaming problem for markets like Brazil and Turkey. Telenor IoT specifically highlights this as a core benefit of their SGP.32 offering. See the eSIM benefits guide for a full explanation.

What is the difference between SGP.32 and SGP.22?

SGP.22 is the consumer eSIM standard – it requires a user to initiate profile changes via QR code or app. SGP.32 is the IoT eSIM standard – profile management is server-initiated with no user required. SGP.32 also supports CoAP for constrained networks that cannot handle HTTPS. Full comparison at SGP.32 vs SGP.02 vs SGP.22.

What is an eIM and do I need one?

The eIM (eSIM IoT Manager) is the server-side component that manages profile lifecycle in SGP.32. Telenor IoT operates the eIM infrastructure for their customers – you do not need to build or host your own. If you are evaluating independent eIM platforms, the provider questions guide covers what to ask about eIM portability and security accreditation.

When will SGP.32 hardware be widely available?

Certified SGP.32 modules from Quectel, Thales, and Kigen are entering commercial availability in 2025-2026. The hardware certification pipeline lags the standards publication by 12-18 months. New IoT hardware designs started in 2025 or later should specify SGP.32-capable eUICC chips. For a full hardware landscape overview, see the eSIM hardware guide.