get_entity

Get the current official Enhetsregister record for a 9-digit organisation number.

Signature: get_entity(organization_id: string, required; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/brreg/get_entity/?organization_id={organization_id}&limit=25&offset=0

Replace {organization_id} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_entity?organization_id={organization_id}&limit=25&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
organization_idrequiredstring
limitoptionalintegerGateway page size; default 25, maximum 100.
offsetoptionalintegerNumber of list items to skip; default 0.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_entity?organization_id={organization_id}&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_entity?organization_id={organization_id}&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/brreg/get_entity?organization_id={organization_id}&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "brreg",
  "operation": "get_entity",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string

Result

Source: Brønnøysund Register Centre. Retrieved 2026-09-11T18:26:28Z in 1.168 seconds.

organization_id:
989657992
navn:
ALBATROSS SERVICES AS
organisasjonsform:
kode:
AS
beskrivelse:
Aksjeselskap
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
historiskeNavn:

5 results

  1. navn:
    RK OFFSHORE & KLIMA AS
    fraDato:
    2006-04-04 20:30:55
    tilDato:
    2007-11-17 15:01:37
  2. navn:
    RK OFFSHORE AS
    fraDato:
    2007-11-17 15:01:37
    tilDato:
    2012-10-18 08:53:31
  3. navn:
    ALBATROSS ELEKTRO & HVAC AS
    fraDato:
    2012-10-18 08:53:31
    tilDato:
    2013-01-21 20:32:18
  4. navn:
    ALBATROSS ELECTRO & HVAC AS
    fraDato:
    2013-01-21 20:32:18
    tilDato:
    2014-07-24 15:57:36
  5. navn:
    ALBATROSS INDUSTRIES AS
    fraDato:
    2014-07-24 15:57:36
    tilDato:
    2024-01-05 15:05:56
registreringsdatoEnhetsregisteret:
2006-04-04
registrertIMvaregisteret:
yes
naeringskode1:
kode:
30.110
beskrivelse:
Bygging av sivile skip og flytende materiell
antallAnsatte:
16
harRegistrertAntallAnsatte:
yes
registreringsdatoMerverdiavgiftsregisteret:
2006-03-01
registreringsdatoMerverdiavgiftsregisteretEnhetsregisteret:
2006-05-31
registreringsdatoAntallAnsatteEnhetsregisteret:
2026-07-15
registreringsdatoAntallAnsatteNAVAaregisteret:
2026-07-10
epostadresse:
post@albatross-industries.no
forretningsadresse:
land:
Norge
landkode:
NO
postnummer:
4055
poststed:
SOLA
adresse:

1 results

  1. Arabergvegen 4A
kommune:
SOLA
kommunenummer:
1124
stiftelsesdato:
2006-03-22
institusjonellSektorkode:
kode:
2100
beskrivelse:
Private aksjeselskaper mv.
registrertIForetaksregisteret:
yes
registrertIStiftelsesregisteret:
no
registrertIFrivillighetsregisteret:
no
sisteInnsendteAarsregnskap:
2025
konkurs:
no
underAvvikling:
no
underTvangsavviklingEllerTvangsopplosning:
no
maalform:
Bokmål
vedtektsdato:
2023-12-06
vedtektsfestetFormaal:

4 results

  1. Teknisk entreprenør innen offshore og marine, både i form av
  2. installasjon, service og vedlikehold, herunder leverin av bearbeidede
  3. metaller, delvis og komplett fabrikkert, samt hva som herved naturlig
  4. står i forbindelse.
aktivitet:

5 results

  1. Reparasjon og vedlikehold av skip og båter, 25.620 Bearbeiding av
  2. metaller Selskapets virksomhet er teknisk entreprenør innen offshore
  3. og marine, både i form av installasjon, service og vedlikehold,
  4. herunder levering av bearbeidede metaller, delvis og komplett
  5. fabrikkert, samt hva som herved naturlig står i forbindelse.
registreringsdatoForetaksregisteret:
2006-04-04
registrertIPartiregisteret:
no
paategninger:

No results.

erIKonsern:
no
kapital:
belop:
200000.0
antallAksjer:
200000
type:
Aksjekapital
valuta:
NOK
innfortDato:
2021-01-19
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/989657992
respons_klasse:
Enhet
Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the get_entity lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.