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-13T03:06:38Z in 0.161 seconds.

organization_id:
980886174
navn:
SOGNDAL SKISENTER DRIFT AS
organisasjonsform:
kode:
AS
beskrivelse:
Aksjeselskap
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/organisasjonsformer/AS
historiskeNavn:

1 results

  1. navn:
    HODLEKVE DRIFT AS
    fraDato:
    1999-07-16 18:23:15
    tilDato:
    2010-06-10 20:12:19
hjemmeside:
www.hodlekve.no
postadresse:
land:
Norge
landkode:
NO
postnummer:
6852
poststed:
SOGNDAL
adresse:

1 results

  1. Postboks 349
kommune:
SOGNDAL
kommunenummer:
4640
registreringsdatoEnhetsregisteret:
1999-07-16
registrertIMvaregisteret:
yes
naeringskode1:
kode:
93.110
beskrivelse:
Drift av idrettsanlegg
harRegistrertAntallAnsatte:
yes
registreringsdatoMerverdiavgiftsregisteret:
2004-03-01
registreringsdatoMerverdiavgiftsregisteretEnhetsregisteret:
2004-12-04
registreringsdatoAntallAnsatteEnhetsregisteret:
2026-07-15
registreringsdatoAntallAnsatteNAVAaregisteret:
2026-07-10
epostadresse:
post@hodlekve.no
telefon:
45 81 95 19
mobil:
416 37 034
forretningsadresse:
land:
Norge
landkode:
NO
postnummer:
6857
poststed:
SOGNDAL
adresse:

1 results

  1. Hodlekvevegen 151
kommune:
SOGNDAL
kommunenummer:
4640
stiftelsesdato:
1998-12-29
institusjonellSektorkode:
kode:
1520
beskrivelse:
Kommunalt eide aksjeselskaper mv.
registrertIForetaksregisteret:
yes
registrertIStiftelsesregisteret:
no
registrertIFrivillighetsregisteret:
no
sisteInnsendteAarsregnskap:
2025
konkurs:
no
underAvvikling:
no
underTvangsavviklingEllerTvangsopplosning:
no
maalform:
Bokmål
vedtektsdato:
2019-02-16
vedtektsfestetFormaal:

6 results

  1. Eige og drive anlegget Hodlekve, og å leggje til rette for idrett og
  2. friluftsliv. Anlegget omfattar skiheis og alpinanlegg, lysløype og
  3. langrennsanlegg og andre løyper. Selskapet skal ved si verksemd ikkje
  4. ha til føremål å skaffe aksjeeigarane økomomisk utbytte, og det skal
  5. ikkje utbetalast utbytte frå selskapet. Eit eventuelt overskot skal
  6. nyttast til å vidareutvikle anlegget.
aktivitet:

1 results

  1. Drift av skiheis og lysløyper.
registreringsdatoForetaksregisteret:
1999-07-16
registrertIPartiregisteret:
no
paategninger:

No results.

erIKonsern:
yes
kapital:
belop:
2671667.0
antallAksjer:
2672
type:
Aksjekapital
valuta:
NOK
innfortDato:
2019-05-13
_links:
self:
href:
https://data.brreg.no/enhetsregisteret/api/enheter/980886174
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.