Mobile numbering and M2M in Spain 2026: what changes for operators and IoT

Key data

Mobile telecommunications operators and M2M service providers in Spain have a new adaptation obligation: the Resolution of April 27, 2026 from SETID modifies the public numbering blocks for mobile and machine-to-machine services, updating a regulation that has been in force since 2010. The change responds directly to the explosive growth of connected devices—smart meters, industrial sensors, vehicle fleets—that have exhausted or strained existing numbering ranges.

This is not a minor administrative modification. It affects network planning, the processes for requesting numbering resources from SETID, and indirectly, the contracts between operators and technology companies deploying large-scale IoT solutions.

What does this regulation establish?

The resolution updates the allocation of public numbering blocks for two types of services:

• Mobile communications services: conventional telephone numbers assigned to mobile lines.
• Machine-to-machine (M2M) communications services: numbering blocks intended for IoT devices, smart meters and similar, which are not used by people but by machines that communicate with each other.

The regulation being modified is the Resolution of March 12, 2010, from the State Secretariat for Telecommunications and the Information Society. It had been in force for more than 15 years without an update of this magnitude.

Economic and operational impact

The impact is not measured in a direct fee or fine, but in operational adaptation costs for operators and in service continuity risk for IoT companies that do not review their agreements in time.

The main impact vectors are:

• Numbering management systems: operators will need to update their internal platforms to incorporate the new ranges or conditions. This involves technical development, testing, and possible maintenance windows.
• Request processes with SETID: the procedures for requesting new numbering blocks change, which requires reviewing the internal workflows of network planning departments.
• Contracts with IoT clients: technology companies deploying large-scale M2M solutions—fleets, utilities, industry—must verify with their operator whether the contracted numbering blocks are affected by the new allocation.
• Medium-term network planning: the update of the national numbering plan conditions expansion decisions for M2M capacity in the coming years.

Who does it affect?

• Mobile telecommunications operators licensed in Spain: direct obligation to adapt numbering management systems.
• M2M service providers that manage numbering blocks themselves or on behalf of third parties.
• Technology companies with large-scale IoT deployments: smart meter manufacturers, fleet operators, industrial companies with connected sensors.
• Utilities and infrastructure companies that use smart meters or sensor networks with M2M numbering.
• Network planning and regulatory departments of any operator with presence in Spain.

Practical example

An energy management company operating 50,000 smart meters in Spain, connected via M2M SIMs from a national operator, must act on two fronts:

First, contact their operator to confirm whether the numbering blocks assigned to their SIMs fall within the ranges affected by the new resolution. If the operator must reassign blocks, it may be necessary to update the configuration of devices deployed in the field.

Second, review the M2M service contract to verify whether there is a regulatory adaptation clause that requires the operator to assume migration costs or whether that cost could be passed on to the customer. In deployments of tens of thousands of devices, even a small per-unit reconfiguration cost can translate into a significant figure.

What should companies do now?

1. Confirm the effective date: the resolution was published on April 30, 2026 but does not specify an effective date. Check the full text in the official BOE to identify exact adaptation timelines.
2. Operators: audit current numbering blocks against the new ranges established by SETID and identify which blocks require migration or updating.
3. Review numbering request processes with SETID: internal network planning procedures must be updated to reflect the new allocation conditions.
4. IoT and M2M companies: contact the operator to confirm whether the numbering blocks of their SIMs are affected and what action plan the operator has planned.
5. Review M2M service contracts: verify regulatory adaptation clauses, especially in large-scale deployments where a numbering change can have significant operational cost.
6. Update medium-term network planning considering the new ranges available for future IoT capacity expansions.