Norway BRREG company data: Enhetsregisteret records as structured JSON
A pay-per-result API for Norwegian company data from BRREG and Enhetsregisteret: org number, NACE codes, employees, VAT status, addresses, and official status flags as clean JSON.
What the API returns
Each run writes one record per company to the default dataset. Field names below are the actual dataset schema of the Norway Company Registry (BRREG) Fresh Details actor.
| Field | Contents |
|---|---|
orgnr | Norwegian 9-digit organisation number |
name / historicalNames / companyForm | Identity, name history, and legal form |
nace1 / nace2 / nace3 / sectorCode | NACE industry codes and sector classification |
employees / incorporationDate / registrationDate | Headcount and registration dates |
businessAddress / postalAddress / municipality | Official addresses |
vatRegistered / foretaksregisteret / bankruptcy / underLiquidation | Registry status flags for compliance checks |
email / phone / homePage | Public contacts where registered |
subunits / subunitCount / parentOrgnr | Corporate structure links |
Official source, no API key needed
Brønnøysundregistrene (BRREG) / Enhetsregisteret. The data comes straight from the official Norwegian registers. No scraping of third-party aggregators, no proxy chain: Enhetsregisteret is keyless and open, which is why the actor can stay cheap and reliable at volume.
Pricing
$0.00125 per result found (volume tiers down to $0.0009), plus $0.05 per actor start. Pay-per-event pricing: pay for results, not for a subscription.
Norway Company Registry (BRREG) Fresh Details on the Apify Store
FAQ
Is BRREG data free in Norway?
Yes, Enhetsregisteret and the other Brønnøysund registers publish their data openly, without an API key. The actor packages that open data into deduplicated, per-org-number records with status flags so it can be piped into databases, CRM systems, or compliance checks.
How is the actor priced?
Pay per event: $0.00125 per result, with volume tiers down to $0.0009, plus $0.05 per run start. No subscription.
Does it cover branches and sub-units?
Yes. Records carry subunitCount, a subunits array, and parentOrgnr, so underenheter (sub-units) and their parents can be traversed from one query.