Best IoT SIM card for Spain: 2026 comparison
Eight IoT SIM providers with presence in Spain: iot.cards, 1NCE, ThingsMobile, Simbase, Onomondo, emnify, Hologram and Soracom. This page does NOT name a universal winner — it names when each one fits your use case, vertical, legal requirements and billing model. If your team is choosing a vendor for 2026, start here.
Short answer
Spain-centric deployment, regulated vertical, private APN or static IP: iot.cards — documented tri-carrier multi-IMSI, Spanish invoicing and an engineering support team in Seville.
Low-data sensors with a 5-10 year horizon: 1NCE — the lifetime plan (€10, 10 years, 500 MB) remains unbeaten for small, predictable traffic.
Prototypes and prepaid purchases with no contract: ThingsMobile or Simbase — prepaid balance, self-service, low per-SIM cost.
Pan-European fleet run by a software team: Onomondo or emnify — cloud-native abstraction and API-first, without a Spain focus.
Global-first with self-service and eUICC from the prototype: Hologram or Soracom — dashboard, credit card and go; invoiced from the US.
The long answer — and the reasoning behind each fit — is below.
How to read this comparison
There is no universal "best" in the IoT SIM market. There are eight valid propositions with different fits. The choice depends on three questions: where you deploy (Spain vs pan-European vs global), what you need (real multi-carrier, private APN, static IP, Spanish-language support, local billing), and what it costs to switch later (especially with solderable MFF2). We've summarised each vendor in a card with its main strength and the ideal case where it wins, without positioning iot.cards as the automatic winner.
The eight propositions, one by one
🇪🇸 iot.cards
Spanish IoT MVNO with documented tri-carrier multi-IMSI in Spain
Strengths
- Multi-IMSI with public access to Movistar, Vodafone and Orange in Spain.
- Private APN from the first SIM, no enterprise committee; static IP as a volume add-on (€600 + VAT installation, €0.5 + VAT/SIM/month).
- Engineering support in Spanish from Seville, with human technical onboarding.
- Spanish company (Kore Logic SL, CIF B90463662); Spanish-VAT invoice.
- Documented operational experience in metering (PRIME/G3-PLC), Iberdrola partner.
Ideal case
Deployment mostly in Spain with requirements for real multi-carrier, private APN, static IP or regulated vertical (metering, healthcare, energy).
Where it doesn't fit
Main focus on Spain and Spanish verticals. If your deployment is 80% Germany or US, players with their own pan-European or American network may fit better.
🇩🇪 1NCE
German IoT MVNO with widely-adopted lifetime tariff (10 years, 500 MB)
Strengths
- Lifetime tariff: €10/SIM for 10 years with 500 MB included. Predictable for fixed budgets.
- Wide pan-European coverage with Deutsche Telekom as anchor carrier and local partners.
- Massive volume: millions of SIMs sold across Europe.
- REST API, dashboard, mature developer ecosystem.
Ideal case
Cases with low and predictable consumption (telemetry sensor, asset tracker sending a few KB/day), with device deployed 5-10 years, where tariff predictability matters more than tri-carrier specifically in Spain.
Where it doesn't fit
The lifetime model doesn't fit devices with growing consumption (CCTV, large OTAs) or customers needing private APN, static IP or per-carrier audit. No invoice from Spain either.
🇮🇹 ThingsMobile
Italian IoT MVNO with prepaid balance and low per-SIM cost
Strengths
- Simple prepaid model: top up balance, consume MB until depleted, no mandatory monthly fee.
- Low per-SIM cost in small quantities (ideal for prototyping).
- Wide coverage in Europe and Latin America via partners.
- Self-service dashboard and documented REST API.
Ideal case
Prototypes, hobby, hardware prototyping, small deployments where you buy 5-50 SIMs and want prepaid balance with no contract. Also valid for resellers embedding connectivity into their product for small end customers.
Where it doesn't fit
For enterprise fleets with SLA, monthly pooled invoice, private APN or regulatory audit requirements, the prepaid model is more friction than value. No legal entity in Spain.
🇳🇱 Simbase
Dutch IoT MVNO with developer-first experience (CLI, modern dashboard)
Strengths
- Polished developer experience: CLI, clean dashboard, rich developer-oriented documentation.
- Pan-European coverage via partners.
- Public pricing in the dashboard, no lock-in.
- Modern REST API with webhooks.
Ideal case
Pan-European developer-first teams without specific Spain focus, who value CLI and cloud abstraction over phone support. Good fit for startups and projects where zero-day learning curve matters more than carrier anchoring.
Where it doesn't fit
No public tri-carrier agreement specific to Spain. Private APN and static IP as enterprise products (not standard layer). No invoice from Spain and no Spanish-language phone support.
🇩🇰 Onomondo
Danish IoT MVNO with cloud-native proposition and "single network" abstraction
Strengths
- "Single global network" model with pan-European and multi-region coverage.
- Modern REST API, clean dashboard, cloud-native focus.
- Operator-agnostic: no need to think about which underlying carrier serves each SIM.
- Polished English documentation.
Ideal case
Pan-European or multi-region deployments where the "single network" abstraction simplifies operations, with no specific requirement to know which underlying carrier serves each SIM.
Where it doesn't fit
No public tri-carrier agreement specific to Spain. The "single network" abstraction makes it hard to audit per-carrier coverage in Spain. Private APN and static IP as enterprise products. No invoice from Spain.
🇩🇪 emnify
German cloud-native platform with a virtualized mobile core on AWS
Strengths
- Cloud-native core pioneer: connectivity is managed like any other piece of your cloud infrastructure.
- API-first, with native AWS and Azure integrations and per-SIM policy controls.
- Broad global multi-network coverage, built for fleets spread across countries.
- Network diagnostics and visibility tooling aimed at software teams.
Ideal case
Mid-sized multi-country deployments run by software engineering teams that want connectivity as programmable infrastructure, with no carrier-by-carrier audit requirement in Spain.
Where it doesn't fit
No public Spain-specific tri-carrier agreement. The developer-first approach assumes an in-house technical team. Private APN and static IP as enterprise configuration. Invoices from Germany.
🇺🇸 Hologram
US platform with self-service onboarding and multi-profile eUICC
Strengths
- Self-service signup in minutes: order SIMs with a credit card and activate from the dashboard.
- Multi-profile eUICC (their Hyper line) to switch carriers without touching hardware.
- Mature dashboard and REST API, with a solid reputation in the developer community.
- Global coverage via agreements with hundreds of operators.
Ideal case
Global-first teams, or teams with a US center of gravity, that value the self-service purchase cycle and want eUICC from the first prototype.
Where it doesn't fit
Support, pricing and billing in dollars from the US. No legal entity or specific focus in Spain; Spanish coverage runs on partner roaming, with no auditable tri-carrier agreement.
🇯🇵 Soracom
Japanese-American platform built for prototyping and direct cloud integration
Strengths
- Self-service console with a very fast start for first tests.
- Managed services of its own (Beam, Funnel, Harvest) that offload work from the device: the SIM talks straight to your cloud.
- Virtualized network core on AWS, focused on experimentation and short runs.
- Extensive technical documentation and an active maker community.
Ideal case
Prototyping and first production runs where direct SIM-to-cloud integration saves weeks of backend work, with the final architecture decision deferred.
Where it doesn't fit
Its proprietary service catalog introduces some architecture lock-in if you build on it. No Spain focus, invoices from the US/Japan, enterprise support via a sales team.
Quick comparison by key dimension
Summary for fast scanning. Look at the column you care about most and see where each vendor fits. The iot.cards row is highlighted because it's our proposition — the rest is based on their public documentation and our operational experience in the market.
| Spain tri-carrier coverage | Private APN / static IP | Spanish-language support | Invoice from Spain | Spanish regulated vertical | |
|---|---|---|---|---|---|
| iot.cards | Yes, documented multi-IMSI (Movistar+Vodafone+Orange) | APN from 1st SIM · static IP by volume | Yes, engineering team in Seville | Yes, Spanish VAT | Documented (PRIME/G3-PLC, Iberdrola partner) |
| 1NCE | ES coverage via Deutsche Telekom + partners | Private APN under enterprise contract | Multilingual; no Spain-specific phone | Invoice from Germany | No specific focus |
| ThingsMobile | ES coverage via partners | Enterprise product | Multilingual; no Spain-specific phone | Invoice from Italy | No specific focus |
| Simbase | ES coverage via partners (no public tri-carrier deal) | Enterprise product | English (and Dutch) | Invoice from Netherlands | No specific focus |
| Onomondo | ES coverage via partner network (operator-agnostic) | Enterprise product | English (and Danish) | Invoice from Denmark | No specific focus |
| emnify | ES coverage via global multi-network (no public tri-carrier deal) | Enterprise configuration | English (and German) | Invoice from Germany | No specific focus |
| Hologram | ES coverage via partner roaming | Enterprise product | English | Invoice from the US | No specific focus |
| Soracom | ES coverage via partner roaming | Enterprise product | English (and Japanese) | Invoice from the US/Japan | No specific focus |
How to choose an IoT SIM provider in 2026: five questions
They apply to this list and to any provider that isn't on it. If a sales rep can't answer them in writing, you already have your answer.
1. What is the real coverage model?
Permanent roaming on a single carrier, multi-IMSI with several national agreements, or local profiles via eUICC are not the same thing. Inside the EU, permanent roaming isn't the regulatory problem it is in Brazil or Turkey; the problem is operational: when the network serving your SIM degrades in an industrial park outside Albacete, is there a second and a third national network to switch to — and who decides that switch? Ask for the list of networks per country, not the number of countries.
2. eUICC today, and SGP.32 on the roadmap?
For hardware that will live 10 years in the field, eUICC is the minimum bar in 2026: it lets you change operators without touching the SIM. SGP.32 — the GSMA standard for IP-based remote provisioning, with no SMS dependency — is reaching the market this year and will be the foundation of zero-touch deployment. Ask for concrete support dates, not roadmap promises.
3. How does Spain's 2G/3G sunset affect you?
Vodafone has already switched off its 3G network. Movistar is in the final phase of its shutdown, with 2G and 3G fully out of service by the end of 2027 at the latest. MasOrange will switch off 3G on December 31, 2027 and keeps 2G running until the end of the decade as a residual M2M network. The Ministry closed its public consultation in January 2026 to set the definitive roadmap. If your current fleet is 2G/3G-only, migrating to 4G, LTE-M or NB-IoT is no longer optional: ask each provider which technologies it supports in Spain and what migration path it offers.
4. What does it really cost, beyond €/MB?
Per-SIM activation, inactivity fees, overage, lock-in periods, SMS/USSD, public IP, zone surcharges. The cheapest provider per megabyte is rarely the cheapest deployment over three years. Ask for a bill simulation with your real traffic profile and compare the total, not the headline rate.
5. Who invoices, from where, and in what language does engineering answer?
Legal entity and jurisdiction, Spanish VAT or reverse charge, where traffic breaks out to the internet (GDPR), and whether technical support — not the chatbot — answers in your language with a written SLA. For a regulated Spanish vertical, an invoice from Delaware is a procurement problem before it is a coverage one.
Decision tree by use case
Four typical scenarios in Spain. Recommendation is driven by technical-commercial fit — not by sales budget.
Regulated metering (Spanish regulator-monitored DSO: electricity/gas/water)
iot.cards fits because of documented operational experience in PRIME/G3-PLC, dedicated private APN to the DSO, private static IP per meter and ICCID-keyed traceability for regulatory audit. 1NCE fits if the meter sends very little predictable traffic and you don't need a dedicated private APN.
24/7 video surveillance (IP cameras, remote NVR)
iot.cards or 1NCE depending on consumption. If the camera uploads video (gigabytes/month), iot.cards with shared data package or enterprise tariff. If the camera only sends short events (KB/month), 1NCE lifetime can be cheaper over 10 years.
Vehicle fleet / asset tracking (GPS, dashcams)
iot.cards fits because of tri-carrier multi-IMSI (Movistar/Vodafone/Orange) that reduces offline windows in areas with uneven coverage. Onomondo or Simbase fit if the fleet is pan-European with no Spain focus. ThingsMobile fits for small fleets with prepaid purchases.
Prototyping / hobby / small projects (1-50 SIMs)
ThingsMobile or Simbase fit because of low per-SIM cost and self-service. iot.cards offers a SIM Test Kit (1 unit, 1 GB over 12 months, 15 € VAT included, free shipping to Spain) for pre-production validation when the final destination will be a Spanish company.
Frequently asked questions
- Which is really "the best" IoT SIM for Spain in 2026?
- There is no universal best. There are better and worse fits depending on your case. If your deployment is mostly in Spain and you need real multi-carrier with Movistar/Vodafone/Orange, private APN or static IP as a standard layer and Spanish-language support, iot.cards fits well. If your device consumes very little (sensor with KB/month) and lives 5-10 years deployed, 1NCE lifetime is very hard to beat on cost. If you do small prototyping, ThingsMobile prepaid simplifies. If you're developer-first pan-European, Simbase or Onomondo. The right question isn't "which is the best", it's "which fits MY case".
- Aren't direct Movistar, Vodafone or Orange the best option for Spain?
- For a Spanish company with a direct commercial relationship with a national operator, contracting IoT directly with that operator can make sense if your volume justifies it and you accept dependency on a single network. The difference vs a multi-carrier IoT MVNO is effective footprint: with a single operator, where that network doesn't reach, your device doesn't reach. We cover this in /comparisons/iotcards-vs-single-carrier.
- Why is iot.cards highlighted in the table?
- Transparency: this site is iot.cards'. To avoid the bias of "the winner is always the one writing the page", we've described each vendor with their real strengths, ideal case and where iot.cards doesn't fit. If your case is pan-European developer-first, you should seriously evaluate Simbase or Onomondo. If your case is lifetime with predictable consumption, you should seriously evaluate 1NCE. This page is a guide, not a sales ambush.
- Can I combine multiple providers?
- Yes, and many large companies do: a 1NCE lifetime SIM in low-consumption predictable sensors + an iot.cards multi-carrier SIM in critical fleet with SLA + a ThingsMobile prepaid SIM in prototypes. The friction is managing multiple portals and invoices. As the fleet grows, most consolidate to one or two providers.
- And the major carriers (direct Telefónica, Vodafone, Orange) don't compete here?
- They compete, but with a different model: direct contracts for high volume, commercial minimums, enterprise committee. IoT MVNOs like the eight listed here are optimised to enter with 5 SIMs and scale to 10,000 without renegotiating. For volumes >50,000 SIMs and annual commitment, contracting directly with the operator can be more cost-efficient — but you lose real multi-carrier.
- And eSIM (eUICC) vs physical SIM? Does it change the ranking?
- It doesn't change the ranking much. All eight providers offer eSIM. SGP.32 eSIM helps OEMs that want to swap operator profiles remotely without touching hardware — useful for products destined for multiple countries. For a purely Spanish deployment, multi-IMSI physical SIM covers the case without SGP.32 complexity. We cover the options at /products/iot-esim.
- What if my deployment is global, not Spain-centric?
- Then this isn't your page — and we'd rather say so than stretch the argument. "Best global IoT SIM" has a different set of finalists: emnify, Onomondo, Hologram, Soracom and 1NCE all compete there with solid offers, and the decision turns on per-country coverage models, eUICC/SGP.32 and pricing structure. This comparison is deliberately anchored to Spain: national tri-carrier access, Spanish invoicing, regulated verticals. If your fleet is 70% Spain, keep reading; if it's 70% elsewhere, run the five-question framework above against the global players.
- What IoT SIM pricing models exist in 2026?
- Five families: prepaid balance (ThingsMobile, Simbase — top up and consume), lifetime (1NCE — one payment for 10 years), pay-as-you-go with a shared data pool (iot.cards and most enterprise MVNOs — SIMs share an allowance), flat rate per SIM/month, and enterprise volume contracts with SLAs. The trap is never in the headline rate: it's in activation, inactivity, overage and lock-in. Ask for a bill simulation with your real traffic.
- How does Spain's 2G/3G sunset affect the provider choice?
- It's the silent expiry date on half the shopping list. Vodafone has already switched off 3G; Movistar completes its shutdown with a final horizon of 2027; MasOrange switches off 3G on 31 Dec 2027 and keeps 2G until the end of the decade for M2M. The practical translation: any 2G/3G-only hardware you buy today starts depreciating against a clock. Demand 4G/LTE-M/NB-IoT support in Spain from your provider, and ask what happens to already-deployed SIMs as each network goes dark.
- What about MFF2 solderable and migration?
- MFF2 solderable is the rugged industrial format, but it ties you to the operator of the IMSI burned in the chip if it's not eUICC. Before soldering thousands of units, validate real coverage with a removable 2FF/3FF/4FF SIM pilot. Once soldered, migrating to another provider means swapping the PCB. No vendor ranking compensates for a poorly-made form-factor decision.
Want us to size your case?
Tell us how many devices, what they consume, your requirements (APN, IP, regulated vertical) and where they're deployed. We'll honestly tell you which fits better — even if the answer is "stay with 1NCE" or "start with ThingsMobile prepaid".
Related reading
- IoT SIM card plans: pay-as-you-go pricing (iot.cards)→
- IoT SIM cards for Spain (iot.cards commercial page)→
- iot.cards vs single operator (direct Movistar/Vodafone/Orange)→
- 1NCE vs iot.cards (lifetime vs multi-carrier)→
- ThingsMobile vs iot.cards→
- Simbase vs iot.cards→
- Onomondo vs iot.cards→
- Telefónica Kite vs iot.cards→
- Olivia Wireless vs iot.cards→
- Hologram vs iot.cards→
- EMnify vs iot.cards→
- Soracom vs iot.cards→
- iot.cards multi-operator SIM (technical detail)→
- iot.cards coverage in Spain (Movistar, Vodafone, Orange)→