AI Regulation Tracker  /  Implementation gap

Norway Meant to Land Its AI Law With the EU's August Deadline

Norway's government targeted late summer 2026 for the KI-loven, roughly when the bulk of the AI Act became applicable across the EU. The EU's August 2 date has passed, and Nkom, the designated coordinating supervisory authority, still describes the law as on its way.

By Anthony Guerriero  ·  Reviewed by Anthony Guerriero  ·  Published August 3, 2026  ·  Updated August 3, 2026  ·  Implementation gap

Key facts

Regulatory briefing

Instrument

Lov om kunstig intelligens (the KI-loven), Norway's implementation of the EU AI Act

Authority

Ministry of Digitalisation and Public Governance; Nkom as coordinating supervisory authority; Datatilsynet and sector regulators retain their mandates

Jurisdiction

Norway, via the EEA Agreement

Status

Draft consulted in 2025. Nkom describes the law as forthcoming; no entry-into-force announcement found as of August 3, 2026

Bindingness

Binding law once the KI-loven enters into force. Until it does, the AI Act does not apply directly in Norway

Target date

Late summer 2026, per the government's consultation announcement

Primary source

Nkom, Kunstig intelligens and Regjeringen, consultation announcement

Why Norway is on a different clock

This is the part people skip. The AI Act is an EU Regulation. Norway is not in the EU. It is in the European Economic Area, and EEA states take EU single-market law by incorporating it into the EEA Agreement and then into national law. There is no mechanism by which a Regulation simply switches on in Oslo because it switched on in Brussels.

So the August 2, 2026 date that mattered across the EU did not, by itself, do anything in Norway. What matters in Norway is the KI-loven, the national act that carries the Regulation into Norwegian law. Until the KI-loven enters into force, the obligations are not Norwegian obligations.

The government was candid that alignment was the goal. When it sent the draft out for consultation, the responsible minister said the aim was for the law to enter into force in Norway in late summer 2026, at roughly the same time as the main part of the AI Act applies in the EU. That was the plan, and the plan had a date attached to it.

Where it actually stands

I checked Nkom's own pages today rather than infer anything from silence. The regulator describes the law in the future tense. Its landing page for artificial intelligence says the KI-loven is on its way and refers to the coming AI law. Its plain-language explainer, carrying a date of June 10, 2026, says that work is underway to bring the rules into Norwegian law.

That is the coordinating supervisory authority itself, in the present tense, describing implementation as unfinished. It is a better basis for this piece than the absence of an announcement would be, and I would rather report what a regulator says about itself than draw an inference from what I could not find.

What is settled is the institutional shape. Nkom is the coordinating supervisory authority and the contact point toward the EU. Sector supervisors keep their own areas, so the data protection authority stays with personal data and the health and medical-device regulators stay with theirs. That is a multi-agency model with a coordinator on top, not a single AI regulator.

What a coordinating supervisor is, and is not

Nkom's designation is worth reading precisely, because coordinating is not the same as sole. The model Norway has chosen puts Nkom at the centre as the national coordinator and the contact point toward the EU, while sector regulators keep the mandates they already hold. The data protection authority stays with personal data. The health and medical-device regulators stay with theirs.

For a compliance team that matters more than it sounds, because it tells you who you will actually deal with. If your AI system sits inside a medical device, your first conversation in Norway is unlikely to be with a telecoms regulator. If your exposure is a recruitment or scoring tool processing personal data, Datatilsynet keeps its existing mandate over that processing, per its retained role alongside Nkom. The AI Act layer is arriving on top of supervisors who exist and keep their own fields.

That is also why I would not treat the pending KI-loven as a quiet period. The absence of the implementing act does not remove the mandates sector regulators already hold. It means the specific AI Act obligations and the specific AI Act supervisory architecture are not yet the thing you answer to in Norway.

What this means if you sell into Norway

The temptation is to treat Norway as part of the EU block on your compliance map. Plenty of firms do, because commercially it usually behaves that way. Here that is wrong in a way that matters, and it is wrong in both directions.

It is wrong if you assume the AI Act binds you in Norway today. It does not, on its own. The duty arrives with the KI-loven. And it is wrong if you conclude Norway is therefore a soft spot worth exploiting, because the law is coming, the supervisory authority is already named and building capacity, and anything you ship in the meantime will still be in the market when the rules land.

The practical posture is unglamorous. Build to the AI Act, because that is what Norway is implementing and the substance will not diverge much. But do not record Norway as having live AI Act obligations in your register unless the KI-loven has entered into force, and a register that overstates the law is as much a problem in an audit as one that understates it. Note the date you checked and watch for the commencement announcement.

One more thing worth flagging for anyone tracking Europe as a whole. Norway's gap is a timing gap, with a named coordinating regulator already designated behind it. That is a different shape from an EU Member State where the Regulation already applies but no market surveillance authority has been notified. Both look like holes on a map, and they are not the same hole. We report each national position separately on this tracker, with its own sourcing and check date.

Last verified: August 3, 2026 against the primary sources listed above.