Where the kommune's employed residents work
Where the kommune's employed residents work: share working in the home kommune, out-commuters, inbound commuters, jobs in the kommune and the top commute destinations, from SSB. Kommune figures, not anyone's commute at this 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
- Publisher terms
Attribution and note
Shown from the contract in its original language.
© SSB 03321 (Pendlingsstrømmer), CC BY 4.0
API warnings
The API returns these notes in warnings.
- Kommune figures for employed residents aged 15-74 in the fourth quarter, by where they live and where they work, not the commute of anyone at this address. A resident with several jobs is counted once, at the main one.
- top_commute_destinations lists the five kommuner outside the home kommune that most residents work in, each with its share of all employed residents. Kommuner are in the 2024 structure.
Provider-contract fields
7 of 11 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 |
| year | integer | null (årstall) | context | open |
| employed_residents | integer | null | value | open |
| working_in_home_kommune | integer | null | value | open |
| home_kommune_share | number | null (andel) | value | open |
| out_commuter_share | number | null (andel) | value | open |
| inbound_commuters | integer | null | value | open |
| jobs_in_kommune | integer | null | value | open |
| top_commute_destinations | 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=commuting'
# 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/commuting?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.