Estimated fire-service response time from the nearest staffed fire station, against the § 22 requirement
fire_response_time18 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.
- Estimate, not the fire service's own response plan or a guaranteed arrival time: free-flow driving on the road graph plus an assumed turnout time. Real response depends on which crew is available, weather, traffic, the 110 centre's handling and road conditions; the brannvesen's own risk and vulnerability analysis is the authority.
- Method fire-response-v1. Candidates are the 5 nearest DSB fire stations by straight line plus the nearest full-time (24h_kasernert) station; each is routed by car (OSRM, OpenStreetMap, no live traffic) and given a turnout time by station_manning: 1.5 min for 24h_kasernert, 5 min for ikke_kasernert (part-time on call, 4-6 min is the usual range), dagkasernert (crewed in the daytime only) and unknown. estimated_response_minutes is the fastest drive + turnout; drive_minutes and turnout_minutes are its parts. Stations further than 100 km are not considered: no candidate leaves the figures null.
- Requirement: brann- og redningsvesenforskriften § 22 (in force 1 March 2022, replacing dimensjoneringsforskriften § 4-8) says utrykningstid shall not exceed 20 minutes to fires in tettsteder and should not exceed 30 minutes outside them. settlement_type is tettsted when the address register names a tettsted (SSB urban settlement) for the address. The 10-minute requirement for dense buildings with rapid fire spread, hospitals, care homes and concentrated business areas cannot be read from our data: within_10_minutes is shown for information and requirement_minutes is never 10.
- Licences: DSB brannstasjoner (open data, DSB); routing on OpenStreetMap data, ODbL, © OpenStreetMap contributors.
- validation lists each figure the model is checked by, against the reference named in it. value null with status not_yet_computed means the check has not been run on the data yet; it is not a pass.
Fields
4 of 18 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 |
|---|---|---|
| estimated_response_minutes | number | null (min) | value |
| within_requirement | boolean | null | value |
| requirement_minutes | integer | null (min) | value |
| settlement_type | string | null | context |
| within_10_minutes | boolean | null (min) | context |
| drive_minutes | number | null (min) | context |
| turnout_minutes | number | null (min) | context |
| drive_distance_m | integer | null (m) | context |
| station_id | string | null | context |
| station_name | string | null | value |
| station_manning | string | null | context |
| fire_department | string | null | context |
| candidates_routed | integer | null | context |
| method | string | null | context |
| method_version | string | null | context |
| inputs | object | null | context |
| validation | array<object> | null | context |
| computed_at | string | 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=fire_response_time' # 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/fire_response_time?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.