Police-reported road accidents within 500 m, last five years
road_accidents17 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
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.
- Police-reported road traffic accidents with personal injury (the register behind Trine and SSB's road accident statistics), counted within 500 m straight-line distance of the address point over the five years to today. Not a risk score and not a forecast: a count of recorded accidents, which depends on traffic volume as much as on how dangerous a road is. Accidents without injury are not in the register.
- Severity is not served: NVDB's open read API withholds the severity properties (fatal, very serious, serious, slight) for every accident, so severity_status is not_published_at_point_level. Trine and SSB table 12044 publish severity only as kommune and county aggregates.
- Road users are counted per accident from the involved units: accidents_involving_pedestrians counts accidents with at least one pedestrian involved, and an accident with a car and a cyclist counts once under cyclists. The groups overlap and do not add up to accidents_total. accidents_by_type uses the register's own accident type (Ulykkestype).
- The register is revised when SSB publishes a year (normally May-June the following year), so the latest months are incomplete. accident_status accident_register_not_loaded means we hold no accidents at all and every count is null; no_accident_within_radius means the register is loaded and none was recorded within 500 m.
Fields
5 of 17 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| accident_status | string | null | context |
| radius_m | integer | null | context |
| window_from | date | null | context |
| window_to | date | null | context |
| accidents_total | integer | null | value |
| accidents_per_year | number | null (årstall) | value |
| accidents_involving_pedestrians | integer | null | value |
| accidents_involving_cyclists | integer | null | value |
| accidents_involving_motorcycles_mopeds | integer | null | context |
| accidents_involving_small_electric_vehicles | integer | null | context |
| accidents_involving_heavy_vehicles | integer | null | context |
| accidents_by_year | object | null | context |
| accidents_by_type | object | null | context |
| nearest_accident_distance_m | integer | null (m) | value |
| latest_accident_date | date | null | context |
| severity_status | string | null | context |
| fetched_at | timestamp | null | context |
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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=road_accidents' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/road_accidents?limit=25'
Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.