Reported road traffic accidents in the address's kommune, fylke and the country
Annual road traffic accidents with persons killed and injured for the address's kommune, its fylke and Norway, from SSB. Annual totals for the area, never incidents at or 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
- Publisher terms
Attribution and note
Shown from the contract in its original language.
© SSB 12044, CC BY 4.0
API warnings
The API returns these notes in warnings.
- Annual totals for the address's kommune, its fylke and Norway, never incidents at or near the address. A kommune re-coded in the 2020 or 2024 reforms is followed across its codes (region_code says which code carried each year); a merged kommune's pre-merger years are those of the kommune that kept the name.
- killed and injured are null where the collected rows do not carry them.
Provider-contract fields
4 of 10 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 |
|---|---|---|---|
| table_id | string | null | context | open |
| region_code | string | null | context | open |
| region_name | string | null | context | open |
| region_scope | string | null | context | — |
| time_period | string | null | context | open |
| accidents | integer | null | value | open |
| accidents_trend | object | null | value | open |
| killed | integer | null | value | open |
| injured | integer | 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=traffic_accidents'
# 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/traffic_accidents?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.