Norway Company Lookup: Open Data, Limited Recombination

A Norway company lookup runs through Brønnøysundregistrene, the Brønnøysund Register Centre. The base register is Enhetsregisteret, which holds base data on legal persons and other units and assigns the organisasjonsnummer; Foretaksregisteret is the companies register. Access is through an open-data API and search at data.brreg.no. This guide covers what the API gives you, a statutory limit on what you may build from it, and two structural traps that catch anyone matching Norwegian records. If you need the Norwegian population rather than one company at a time, the Norway company directory covers the same registered units with industry, size and contact breakdowns attached, and the Norway business database is the same file described as a dataset.

Norway company lookup: the short version

• That a person is registered with a role — a board member, for example — is open public data.
• But if you want to build an overview of the roles one person holds across other entities, you may only show roles connected to commercial activity. A charity trusteeship may not be displayed alongside a directorship in an aksjeselskap. The reference given is § 9-1 enhetsregisterloven.
• The restriction is on aggregation, not access. Every individual fact stays open.
• The search is capped at 10,000 units per query with a default page size of 20 — and a documented endpoint downloads the complete dataset.

The rule is about what you build, not what you see

Norway publishes its register generously and then says something about it that almost no other register in this series says. From the Enhetsregisteret API documentation:

"Opplysninger om at en person er registrert med en rolle, som for eksempel styremedlem, er åpne offentlige data. Men ønsker du å sette opp en oversikt over hvilke roller en person har i andre virksomheter, har du kun lov å vise roller knyttet til næringsvirksomhet. Det betyr at personens registrerte rolle i en frivillig organisasjon ikke kan vises med personens roller i for eksempel et aksjeselskap. For aktuelt regelverk se § 9-1 i enhetsregisterloven."

Information that a person is registered with a role, such as a board member, is open public data. But if you wish to set up an overview of which roles a person holds in other undertakings, you are only permitted to show roles connected to commercial activity. This means that the person's registered role in a voluntary organisation cannot be shown together with the person's roles in, for example, a limited company. For the applicable rules, see § 9-1 of the enhetsregisterloven.

Make the distinction explicit, because it is the entire point and it is easy to blur. This restricts what you may build, not what you may see. Every individual fact remains open public data. You may look up the charity and find the trustee. You may look up the company and find the director. What the rule addresses is the act of combining them into a single view of one person — and even then it does not close the view, it narrows it to roles connected to næringsvirksomhet.

It is, in other words, a restriction placed at the point of recombination. The raw material stays open; the derived product is what the statute speaks to.

This page states the rule and its statutory reference and goes no further. It does not say what a reader may therefore do, does not interpret what counts as næringsvirksomhet, and does not speculate about how any of this applies outside Norway. Those are legal questions with real consequences, and a reader who needs them answered needs a Norwegian lawyer rather than a guide.

Two registers, two restrictions, and they do not line up

Two other European registers in this series place a limit on what may be done with data they give away freely, and the three limits sit on different axes entirely.

The Belgium company lookup guide covers a state whose open-data terms restrict purpose: "Personal data may not be reused for direct marketing purposes." The Czech Republic company lookup guide covers a state whose statute defines open data as information "jejichž způsob ani účel následného využití není omezen" — whose manner and purpose of subsequent use is not restricted at all. Norway restricts neither purpose nor manner but combination: the facts are open, and assembling certain of them into one view is what the statute reaches.

Three states, three different places to put a limit. This page does not rank them and does not suggest a trend — three registers is three registers, and drawing a direction from them would be inventing a pattern rather than reporting one. The practical conclusion is the narrow one: these are not stricter and looser versions of a single rule, so knowing one country's regime tells you nothing about the next.

What a Norwegian company register entry contains

A self-contained summary. Norway's base register is Enhetsregisteret, held by Brønnøysundregistrene, which holds base data on legal persons and other units and assigns the organisasjonsnummer, a nine-digit number uniquely identifying units; Foretaksregisteret is the companies register. Brønnøysundregistrene states that the service consists of several APIs, through which you can do a direct search, download entire datasets and retrieve updates. A hovedenhet is a unit at the top level of the registration structure — sole proprietorships, associations, companies, jointly-owned properties and others. An underenhet is at the lowest level, cannot exist alone, always has a connection to a hovedenhet, and has its own organisasjonsnummer. Information that a person is registered with a role, such as a board member, is open public data; but to set up an overview of which roles a person holds in other undertakings, only roles connected to commercial activity may be shown, so that a person's registered role in a voluntary organisation cannot be shown together with their roles in, for example, a limited company, with § 9-1 of the enhetsregisterloven given as the applicable rule. The search is paginated with a default page size of 20 units and the result set is limited to 10,000 units per query; a separate endpoint, enheter/lastned, downloads the complete dataset. Results can be sorted, for example by number of employees ascending. The documentation notes that a hovedenhet's superior unit in the public sector may have been deleted, and advises making a new request for the parent unit and checking whether slettedato is set. A separate fullmakt service requires a virksomhetssertifikat and standard client certificate authentication; credit information companies must sign a self-declaration after applying, and where an application is approved the applicant's organisation number is authorised for the lookup service that returns fødselsnummer.

The cap, and the sanctioned way past it

Norway documents both halves of the bulk question, which is rarer than it should be.

The search is paginated with a default page size of 20 units, and the documentation states plainly: "Resultatsettet er begrenset til 10 000 enheter per spørring." The result set is limited to 10,000 units per query. Results can also be sorted — the documentation's own example is sort=antallAnsatte,ASC, by employee count ascending.

Those are technical parameters of a documented API rather than prices, and they are reproduced here as the documentation states them.

The important part is what sits beside the cap. A separate endpoint, enheter/lastned, downloads the complete dataset. And Brønnøysundregistrene describes the whole arrangement: "The service consists of several APIs. You can do a direct search, download entire datasets and retrieve updates."

Search, bulk download, and an update feed — all documented, all official. Across this series, registers answer the "more than one company at a time" question in very different ways, and Norway's is the most generous answer recorded so far: the query cap is published, and so is the sanctioned route past it, in the same documentation. A reader does not have to guess whether bulk access is permitted or negotiate for it; the endpoint is in the docs.

Two numbers can mean one business

Anyone matching Norwegian records needs the structure before they need anything else, and it is a genuine trap.

A hovedenhet is a unit at the top level of the registration structure — sole proprietorships, associations, companies, jointly-owned properties and others. An underenhet is at the lowest level: it "kan ikke eksistere alene og har alltid knytning til en hovedenhet" — it cannot exist alone and always has a connection to a hovedenhet. And crucially, an underenhet has its own organisasjonsnummer.

So two organisation numbers can describe one business. A deduplication rule keyed on the organisasjonsnummer alone will treat a hovedenhet and its underenhet as two unrelated units, because on that key they are. The relationship is real and registered, but it is not visible in the identifier.

There is a second detail here of the kind that only turns up in real documentation rather than in summaries of it: "Det kan forekomme at en hovedenhets overordnede enhet i offentlig sektor er slettet." It can happen that a hovedenhet's superior unit in the public sector has been deleted. The documentation's advice is to make a new request for the parent unit and check whether slettedato is set — so a broken parent link is a state to test for rather than an error to treat as a data fault.

Where a Norway lookup stops

One service sits outside the open data entirely. The fullmakt service requires a virksomhetssertifikat and standard client certificate authentication. Credit information companies must sign a self-declaration after applying, and where an application is approved, the applicant's organisation number is authorised for the lookup service that returns fødselsnummer — the national identity number.

That is the boundary of Norwegian openness as the documentation draws it: base data and roles are open, a complete download is a documented endpoint, and the national identity number sits behind an application, a certificate and a declaration.

This page describes no field of an Enhetsregisteret record beyond what is above, and it does not describe what the næringskode classification is for. Neither was established from Brønnøysundregistrene's own pages on the date shown. NORWAY_REPORT.md flags the second one first, and explains why it matters more than it looks.

Where the question is a population rather than a company, a firmographic directory covers the same registered units with classification, size and contact data attached and queryable as a set; the Europe company directory breaks the European file down by market.

Data quality pitfalls to avoid in Norway

Keying deduplication on the organisasjonsnummer alone. An underenhet has its own organisation number and cannot exist alone, so two numbers can describe one business.

Treating a missing parent unit as a data fault. The documentation notes a hovedenhet's superior public-sector unit may have been deleted, and advises re-requesting the parent and checking whether slettedato is set.

Assuming a role overview may show every role. Building an overview of one person's roles across undertakings may only show roles connected to commercial activity, per § 9-1 enhetsregisterloven.

Reading that rule as a restriction on access. It is not. Each individual fact remains open public data; what it reaches is the combined view.

Paginating past the cap instead of downloading. The result set is limited to 10,000 units per query, and a documented endpoint downloads the complete dataset.

Expecting fødselsnummer from the open API. It comes from a separate service requiring a virksomhetssertifikat, client certificate authentication, an application, and for credit information companies a signed self-declaration.

A repeatable Norway company lookup workflow

1. Establish whether a unit is a hovedenhet or an underenhet before matching anything.
2. Carry the hovedenhet relationship alongside the organisasjonsnummer, never instead of it.
3. Use enheter/lastned for the complete dataset rather than paginating toward the 10,000-unit cap.
4. Check slettedato on a parent unit when a link does not resolve.
5. Keep role data as individual facts, and take legal advice before building any cross-entity view of a person.
6. Treat fødselsnummer as out of scope unless you hold the certificate and approval the fullmakt service requires.

Frequently asked questions

Is Norwegian company data open?

Largely, yes. Brønnøysundregistrene states the service consists of several APIs through which you can do a direct search, download entire datasets and retrieve updates, and that information about a person holding a role is open public data.

Can I build a profile of everywhere a person sits on a board?

Only partly. The documentation states that to set up an overview of which roles a person holds in other undertakings, you may only show roles connected to commercial activity, citing § 9-1 of the enhetsregisterloven. This page states the rule and does not advise on applying it.

Does that mean the charity role is secret?

No. That a person is registered with a role is open public data. The restriction is on combining roles into one overview, not on the underlying facts.

How many results can one query return?

The result set is limited to 10,000 units per query, with a default page size of 20. A separate endpoint, enheter/lastned, downloads the complete dataset.

What is the difference between a hovedenhet and an underenhet?

A hovedenhet is at the top level of the registration structure. An underenhet is at the lowest level, cannot exist alone, always connects to a hovedenhet, and has its own organisasjonsnummer.

Why does a parent unit sometimes not resolve?

The documentation notes that a hovedenhet's superior unit in the public sector may have been deleted, and advises requesting the parent unit again and checking whether slettedato is set.

How do I get a fødselsnummer?

Through the fullmakt service, which requires a virksomhetssertifikat and standard client certificate authentication. Credit information companies must sign a self-declaration after applying, and approval authorises the applicant's organisation number for that lookup service.

Source Register

Every Norwegian sentence quoted above is the publisher's own wording, read on the date shown, carrying its characters as the documentation writes them, with an English gloss beside it rather than in place of it. Two figures appear in this page's prose — the 10,000-unit query limit and the page size of 20 — and both are technical parameters of a documented API attributed to that documentation, not prices or amounts. No fee, count or tariff appears anywhere.

This page does not advise on compliance with § 9-1, does not interpret næringsvirksomhet, and does not speculate about the rule's application outside Norway. It also does not describe the purpose of the næringskode classification, which was not sourced; NORWAY_REPORT.md flags that first, because it would pair directly with a neighbouring register that states it holds no industry codes at all.

The readings that are InfobelPRO's rather than Brønnøysundregistrene's: that the rule is best understood as sitting at the point of recombination rather than of access; that Norway's published cap plus published download endpoint is the most generous bulk answer recorded in this series so far; and that a deduplication key on the organisasjonsnummer alone will split a hovedenhet from its underenhet, because the relationship is registered but not visible in the identifier. Those are ours. The comparison with Belgium and the Czech Republic is a comparison of three published legal answers sitting on different axes, offered without ranking and without any claim of a trend.