Registered address units

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

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

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.

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” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
unit_id	string \| null	context	—
unit_number	string \| null	value	open
floor_number	integer \| null	value	open
unit_type	string \| null	value	open
municipality_code	string \| null	context	—
imported_at	string \| null	context	—

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=address_units"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "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.