IoT eSIM in Norway: The eUICC and SGP.32 Guide (2026)

Ask a Norwegian IoT supplier whether they do eSIM and the answer is almost always yes. It is also almost useless. "eSIM" now covers at least four different things, and only one of them is the standard actually built for a device that will spend the next decade up a mountain, inside a substation or bolted to a fish cage. This guide separates the eUICC and SGP.32 reality from the brochure, and looks at who can genuinely give you control of the profile inside your device once it is deployed across Norway.

IoT eSIM in Norway at a glance

eSIM, eUICC and SGP.32: what the words actually mean

Most confusion in this market comes from one lazy habit: using "eSIM" to mean a soldered SIM. It does not. The soldering is a form factor. The technology that matters is eUICC (embedded Universal Integrated Circuit Card), which is the ability of the SIM to store more than one operator profile and switch between them remotely.

An eUICC can turn up as a conventional removable 2FF SIM, a 3FF micro, a 4FF nano, a soldered MFF2 chip or an integrated iSIM built into the modem silicon. The plastic is irrelevant. What matters is whether the thing can hold multiple profiles and be reprovisioned over the air, and under whose control that happens.

That control is defined by which GSMA Remote SIM Provisioning (RSP) architecture is in play:

• SGP.02 is the old M2M architecture. Capable, but heavy to integrate and effectively operator-managed.
• SGP.22 is the consumer architecture. It works beautifully when a human is stood there scanning a QR code. An electricity meter is not stood there scanning anything.
• SGP.32 is the new IoT architecture, designed for exactly the case where nobody is present. It introduces two components worth knowing by name: the IoT Profile Assistant (IPA) on the device, and the eSIM IoT Remote Manager (eIM) that issues profile operations remotely. If you want the full walk-through, our what is SGP.32 explainer covers the architecture in detail.

So when a Norwegian supplier says "we support eSIM", the honest follow-up is: which architecture, and who controls the eIM? Those two answers tell you far more than any coverage map.

The Norwegian core: Com4, Telenor and Telia

Norway is not stuffed with independent IoT MVNOs. The market that actually matters for a device living in Norway is a triangle: one Norwegian IoT specialist and two Nordic operators.

Com4

Com4 is the most interesting place to start because it is genuinely Norwegian and genuinely specialised. Headquartered in Oslo and founded in 2011, it is an IoT-focused mobile operator rather than a consumer network selling an IoT service on the side. It runs its own mobile core (EPC and 5G core) and its own PLMN, and in Norway its non-steered SIMs reach both Telenor and Telia, which matters the moment equipment moves beyond the cities.

On eUICC, Com4 has form. The company says it was the first IoT operator in Europe to offer GSMA-compliant eUICC subscription management, and that it carried out Europe's first profile swap over its own RSP platform. Take the superlatives with the usual pinch of salt, but the point stands: this is not a company that discovered eUICC last week. Its SIMs are offered in everything from Mini through to eSIM and iSIM, and it now markets its IoT SIMs as SGP.32-ready.

The other thing worth saying plainly is that Com4 is not a Norway-only outfit. It advertises access to more than 750 networks across 190-plus countries and says it now manages over 20 million SIM connections, spanning 2G, 4G, 5G, LTE-M, NB-IoT and satellite. So a Norwegian manufacturer can, in theory, deploy the same connectivity proposition at home and in export markets rather than sourcing a different SIM for every country. One footnote that matters when you map the market: Com4 has been part of the Wireless Logic group since 2021. Norwegian operator on the outside, large international IoT group underneath. We have looked at Com4's position in more detail over on IoT Portal.

Best suited to: Norwegian and international deployments that want multi-network access, real IoT support, established eUICC and a credible path to SGP.32.

Telenor IoT

Telenor needs no introduction in Norway, but its IoT arm reaches well beyond the domestic network, with a footprint across the Nordics, EMEA, the Americas and APAC and more than 30 million connected devices under management.

More to the point, Telenor IoT is the operator that has actually shipped. It began commercial delivery of fully standardised SGP.32 SIMs on 17 April 2026, and by early May had its first customer, transport-display maker Axentia, live on a standardised SGP.32 solution. That makes Telenor the furthest-ahead operator anywhere on this list, and it has been deliberately loud about the standardised part, pitching itself against non-standard "eSIM" offerings on an anti-lock-in argument. For a Norwegian business deploying internationally, the useful questions are therefore no longer whether Telenor "does eSIM" but how its SGP.32 implementation handles bootstrap connectivity, local profiles in regulated markets, and a future change of provider.

Best suited to: larger Norwegian and multinational fleets that want an established Nordic operator with commercial, standardised SGP.32 available today rather than on a roadmap.

Telia

Telia is the other obvious operator, with a strong Norwegian and wider Nordic and Baltic footprint and a proper managed IoT operation covering 4G, 5G, LTE-M and NB-IoT, plus private APN and VPN options that matter for infrastructure and industrial work.

Its Norwegian SIM portfolio already includes eUICC, and Telia has moved past vague eSIM talk: in early 2026 Telia Norway published a dedicated SGP.32 explainer through its own eSIM lead, positioning the standard as the next stage of IoT profile management and saying it expects commercial SGP.32 adoption to accelerate during 2026. So Telia is worth a conversation both for current eUICC deployments and for projects being designed around SGP.32, provided you push past the roadmap language to what is orderable now.

Best suited to: Norwegian enterprises wanting a major operator with strong domestic infrastructure, Nordic reach and a clear SGP.32 direction.

The international platforms that also cover Norway

Beyond the Norwegian core sit the international IoT connectivity platforms. None of them is Norwegian, but all of them work in Norway, and each illustrates a different point on the "who controls the profile" spectrum.

• Wireless Logic is one of Europe's largest dedicated IoT connectivity groups and, as noted above, owns Com4. It supports all three RSP architectures (SGP.02, SGP.22 and SGP.32) and runs SGP.32 as a fully managed service. For a Norway-only deployment, Com4 is usually the more direct conversation; for a complex multinational estate, it is worth understanding what the wider group adds behind Com4.
• emnify takes a cloud-native approach and has built its Advanced eSIM proposition on SGP.32, leaning hard on programmable, remote profile switching and embedded fallback profiles as resilience features. Its Norwegian coverage includes NB-IoT through Telenor. A strong fit for API-centric deployments and OEMs designing in one country and shipping to many.
• Eseye combines multi-IMSI with eUICC in its AnyNet proposition and makes a particular virtue of localisation: rather than roaming indefinitely on one foreign identity, an eUICC device can take an appropriate local profile. Useful for globally exported kit where permanent-roaming rules bite.
• 1NCE is the odd one out commercially, built around long-duration, low-data connectivity for sensors, meters and trackers. It supports industrial eUICC and a "Freedom to Switch" capability for adding, changing and deleting profiles remotely. Worth comparing against conventional monthly contracts for very low-data Norwegian devices, but check the exact Norwegian network and radio technology on your specific product rather than assuming global coverage means every local network.

The only questions that really matter

There is no single best IoT eSIM provider in Norway. The right answer depends entirely on what the device does and where it will live. For a Norwegian deployment, the checklist that actually separates providers is:

• Which Norwegian networks can the SIM reach, and is selection steered or non-steered?
• Does it support the radio you need: 4G, 5G, LTE-M, NB-IoT?
• Is the SIM genuinely eUICC, or just a fixed-profile SIM in an eSIM form factor?
• Which RSP architecture is used, and is SGP.32 available now, in pilot, or merely promised?
• Who controls the eIM, and can third-party operator profiles be downloaded?
• Can the connectivity provider be changed after deployment, and what happens to the SIM if you terminate the original contract?
• Is localisation available outside Norway? Are private APNs, VPNs and an API available?
• What happens to all of this in year ten or fifteen?

That last one is the one everybody forgets. The SIM costs almost nothing next to the equipment attached to it. Sending an engineer to a remote pumping station, a wind turbine or a substation because somebody picked the wrong SIM a decade earlier costs a great deal more.

Why SGP.32 changes the Norwegian conversation

SGP.32 matters in Norway specifically because it fixes an awkward compromise in the older architectures. SGP.02 could manage machines but was heavy to integrate. SGP.22 simplified eSIM but assumed a human with a screen. Neither suited a tracker buried in a machine or a meter on a wall. SGP.32 is designed around the reality that nobody is present, using the IPA on the device and the eIM in the back office to manage profiles remotely and at fleet scale.

What it does not automatically mean is "no lock-in". The plastic disappears, but commercial agreements, profile availability, platform design and, above all, control of the eIM still decide how free you actually are. An SGP.32 logo on a datasheet is the start of the diligence, not the end of it. If you want to see where the lock quietly relocates to under SGP.32, our sister site sgp32.co.uk takes that argument apart in detail, and esimiotmanager.com covers the eIM itself.

The wider Nordic picture

Norway should not be read in isolation. Sweden, Denmark and Finland have similarly mature cellular markets and, between them, one of Europe's more interesting IoT regions, and several of the providers above operate across the whole area.

• Sweden adds Tele2 IoT, which is arguably the most interesting Nordic SGP.32 story after Telenor: at Mobile World Congress in March 2026 it launched one of the first end-to-end SGP.32 solutions, stitching together Tele2 connectivity, Cisco IoT Control Center and IDEMIA's eSIM infrastructure. That is precisely the kind of implementation worth pulling apart to ask who owns which piece.
• Denmark brings Onomondo, whose cloud-native, software-led network is a genuinely different model from conventional MNO-based IoT connectivity.
• Finland has its own strong ecosystem, including Elisa, alongside DNA and Telia.

The differences between the four markets are big enough to justify treating them separately, so we will cover Sweden, Denmark and Finland in their own guides. But the underlying shift is the same everywhere. The question is moving away from "which SIM gives me roaming coverage?" and towards "who controls the connectivity profile inside my device, and can I change it when circumstances change?" For long-life IoT equipment, that is the one that ends up mattering.

Frequently asked questions

Is eSIM the same as eUICC?

No, and the muddle costs people money. "eSIM" is loosely used for a soldered SIM, but that is just a form factor. eUICC is the underlying capability to store multiple operator profiles and switch between them remotely. A removable plastic SIM can be a eUICC; a soldered chip might not be. When comparing Norwegian providers, ask about eUICC and the RSP architecture, not "eSIM".

Which Norwegian provider actually has SGP.32 today?

As of August 2026, Telenor IoT is the operator that has commercially shipped standardised SGP.32 SIMs, with delivery from 17 April 2026. Com4 markets its IoT SIMs as SGP.32-ready, and Telia expects commercial adoption to accelerate through 2026. Always confirm what is orderable now versus on a roadmap, and which SGP.32 version and components have been certified or tested.

Can I use one SIM for Norway and for export markets?

Potentially, yes. Com4, Wireless Logic, emnify and Eseye all offer international coverage, and eUICC with localisation lets a device take a local profile rather than roaming permanently. Whether that is right for you depends on the target markets' permanent-roaming rules and on which local networks and radio technologies your specific SIM product actually supports. Check the specifics rather than the headline country count.

What does "who controls the eIM" mean in practice?

Under SGP.32, the eIM (eSIM IoT Remote Manager) is what issues profile operations to your fleet. If your provider controls it and will not let you point at third-party SM-DP+ environments or download competing operator profiles, then the plastic has gone but the lock-in has simply moved up a layer. It is the single most useful thing to interrogate on any SGP.32 proposal.

---

Related reading: What is SGP.32? · SGP.32 architecture and lock-in (sgp32.co.uk) · The eSIM IoT Remote Manager explained (esimiotmanager.com)

By Peter Green. Independent, vendor-neutral coverage of eUICC and eSIM standards for IoT. Commercial status reflects the market as of August 2026 and will be updated as the ecosystem develops.