Employment in the address's kommune, and how it is moving against the country
Register-based employment in the address's kommune from SSB: residents in work, jobs located there, employment rate and workplace ratio, with trends against Norway.
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
- Publisher terms
Attribution and note
Shown from the contract in its original language.
© SSB 11618 (registerbasert sysselsetting), CC BY 4.0
API warnings
The API returns these notes in warnings.
- Register-based employment for the kommune: employed_by_residence counts people who live here and have a job anywhere; employed_by_workplace counts jobs located here. workplace_ratio above 1 means the kommune imports workers. Trends compare the latest year to the previous and to five years back, for the kommune and for Norway. Nothing here is about the address or its residents.
Provider-contract fields
7 of 12 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 |
|---|---|---|---|
| region_code | string | null | context | open |
| region_name | string | null | context | open |
| time_period | date | null | context | open |
| age_group | string | null | context | open |
| population | integer | null (personer) | value | open |
| employed_by_residence | integer | null (personer) | value | open |
| employed_by_workplace | integer | null (arbeidsplasser) | value | open |
| employment_rate | number | null (%) | value | open |
| workplace_ratio | number | null (forhold) | value | open |
| employment_rate_trend | object | null | value | open |
| jobs_trend | 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=employment_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/employment_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.