When does NACE Rev. 2.1 apply?

Reference year 2025 is the first year for which Rev. 2.1 is mandatory for EU statistical reporting. Historic data stays in Rev. 2.

Is a Rev. 2 code the same as a Rev. 2.1 code?

Most 4-digit numbers survive, but Eurostat publishes an official correspondence that maps each Rev. 2 class to one or more Rev. 2.1 classes; some splits, some merges.

Do national codes (NAF, WZ, CAE, ATECO, CNAE, SBI, PKD) also change?

Yes. National statistical institutes republish their 5-digit local subclasses on the same date, so a business may see its local code change even when the underlying activity has not.

What should I do with historic time series?

Keep historic points in Rev. 2, keep new points in Rev. 2.1, and store the revision year with every code. The correspondence table lets you re-aggregate historic points into Rev. 2.1 groupings when you need a continuous series.

EU statistical classification · NACE Rev. 2.1

NACE Rev. 2.1 — the 2025 revision

From reference year 2025, EU statistical reporting switches from NACE Rev. 2 (2008) to NACE Rev. 2.1. Here's what changes and what stays the same.

Most classes keep the same 4-digit number, but a set of activities is renamed, split, merged or newly created — mostly around digital platforms, data centres, renewable energy, repair and reuse, waste treatment, and health and social care. National institutes republish their 5-digit local subclasses (NAF, WZ, CAE, ATECO, CNAE, SBI, PKD, …) on the same date.

Timeline at a glance

2006 — NACE Rev. 2 adopted (Regulation (EC) 1893/2006).
2008 — Rev. 2 first applied to reference year data.
2023 — Rev. 2.1 adopted at EU level.
2025 — Rev. 2.1 mandatory for EU statistical reporting.
2025 → National 5-digit subclasses re-aligned to Rev. 2.1.

Rev. 2 vs Rev. 2.1 — what actually changes

Area	NACE Rev. 2 (2008)	NACE Rev. 2.1 (2025)
Reference year	2008 onward	2025 onward (mandatory for EU statistics)
Structure	21 sections · 88 divisions · 272 groups · 615 classes	Same 4-level structure; class count adjusted by splits/merges
Digital platforms & marketplaces	Bucketed into generic wholesale/retail and IT classes	Dedicated classes for platform-mediated marketplaces and gig work
Data centres & cloud	Grouped with generic 63.11 data processing / hosting	Split-out treatment for data-centre operation and cloud infrastructure
Renewable energy	Merged with generic electricity generation (35.11)	Renewable generation and grid balancing separated for reporting
Repair & reuse	Narrow, item-specific repair classes	Broader classes aligned with circular-economy policy
National 5-digit subclasses	NAF, WZ, CAE, ATECO, CNAE, SBI, PKD… aligned to Rev. 2	National institutes republish subclasses aligned to Rev. 2.1 in 2025

Bridging historic data

For anyone maintaining a time series that spans the changeover, the practical rule is: never renumber the historic points, and always store the revision alongside the code.

Eurostat publishes an official correspondence table between Rev. 2 and Rev. 2.1 — some mappings are 1:1, some split a Rev. 2 class into several Rev. 2.1 classes, and a few merge in the other direction. NACEBridge exposes both revisions in parallel and falls through the official correspondence on every cross-border conversion.

NACE

Browse NACE Rev. 2.1 →

Open the NACE hub with search, browse and download in every EU language.

FAQ

When does NACE Rev. 2.1 apply?: Reference year 2025 is the first year for which Rev. 2.1 is mandatory for EU statistical reporting. Historic data stays in Rev. 2.
Is a Rev. 2 code the same as a Rev. 2.1 code?: Most 4-digit numbers survive, but Eurostat publishes an official correspondence that maps each Rev. 2 class to one or more Rev. 2.1 classes; some splits, some merges.
Do national codes (NAF, WZ, CAE, ATECO, CNAE, SBI, PKD) also change?: Yes. National statistical institutes republish their 5-digit local subclasses on the same date, so a business may see its local code change even when the underlying activity has not.
What should I do with historic time series?: Keep historic points in Rev. 2, keep new points in Rev. 2.1, and store the revision year with every code. The correspondence table lets you re-aggregate historic points into Rev. 2.1 groupings when you need a continuous series.