Skip to content

← All sections

Registered address units

Registered address units at the address, such as H0101, with unit type and floor. A unit number is assigned only where a building holds more than one unit, so a single-unit home has none.

address_units6 fields3 of these fields open in the demo
Source
Kartverket address register
Geography
The address point
Reported stale after
30 days
Access
Requires an API key granted this section
Contract version
1

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
358

Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.

Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

Source terms and reuse

These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.

Declared licence or terms
Creative Commons Attribution 4.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© Kartverket address register, CC BY 4.0

API warnings

The API returns these notes in warnings.

  • Registered unit identifiers only. A unit number (H0101) is assigned ONLY where a building holds more than one unit, so for a single-unit home its absence is the register working as designed — not a gap in our ingestion. Measured 18 Sep 2026 across 3,457,839 rows: 2,237,036 addresses hold exactly one unit and carry no number; 241,103 hold several (5.06 on average) and are numbered; 8 are anomalous (2 multi-unit without numbers, 6 partially numbered). Absence of units still never proves a single-unit property — an address we never ingested looks the same.

Provider-contract fields

3 of 6 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

FieldTypeRoleDemo
unit_idstring | nullcontext—
unit_numberstring | nullvalueopen
floor_numberinteger | nullvalueopen
unit_typestring | nullvalueopen
municipality_codestring | nullcontext—
imported_atstring | nullcontext—

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643?include=address_units'

# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/address_units?limit=25'

Try it now

This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.