Housing construction in the kommune, last 8 quarters vs Norway
Housing construction in the address's kommune over the last four quarters, approved, started and completed dwellings, compared with the four before and with Norway. Kommune totals, not activity near the address.
Status right now
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
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
© SSB table 05889 (CC BY 4.0), CC BY 4.0
API warnings
The API returns these notes in warnings.
- Kommune-wide totals of dwellings (all building types), not activity near the address: a busy kommune says nothing about the street.
- SSB suppresses some small cells, so a small kommune's totals can read low, never high, and its trend is noisy. The trend compares the last four quarters with the four before, for the kommune and for Norway over the same quarters.
Provider-contract fields
8 of 16 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.
| Field | Type | Role | Demo |
|---|---|---|---|
| municipality_code | string | null | context | open |
| municipality_name | string | null | context | open |
| latest_quarter | string | null | context | open |
| approved_last_4_quarters | integer | null | value | open |
| started_last_4_quarters | integer | null | value | open |
| completed_last_4_quarters | integer | null | value | open |
| started_previous_4_quarters | integer | null | context | open |
| started_change_pct | number | null (%) | value | open |
| started_last_4_quarters_per_1000 | number | null | value | open |
| population | integer | null | context | open |
| norway_started_last_4_quarters | integer | null | context | open |
| norway_started_change_pct | number | null (%) | value | open |
| norway_started_last_4_quarters_per_1000 | number | null | context | open |
| trend_vs_norway | string | null | value | open |
| quarters | array<object> | null | value | open |
| updated_at | string | null | context | open |
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=building_activity_municipality'
# 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/building_activity_municipality?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.