Skip to content

← All sections

Inter-municipal fire service covering the address

The inter-municipal fire service whose area covers the address. Not every kommune organises its fire service this way, so an address outside every area is not an error.

fire_service_coverage7 fields7 of these fields open in the demo
Source
DSB Interkommunale brannvesen
Geography
The address point
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
In packages
fire_and_damage

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
12 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 12 Nov 2026
Newest record
12 Nov 2026
Municipalities with data
1

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
unverified
Declared redistribution
Not established
Catalogue basis
Unverified

API warnings

The API returns these notes in warnings.

  • Organisational coverage area of the inter-municipal fire service (IKS/samarbeid). Not every kommune runs its brannvesen this way: an address outside every polygon is not_found with reason not_in_inter_municipal_fire_service, meaning its kommune runs its own. The nearest inter-municipal service is never substituted.
  • Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.

Provider-contract fields

2 of 7 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullvalueopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
administrative_localitystring | nullcontextopen
straight_line_distance_minteger | null (m)contextopen
contains_addressboolean | nullvalueopen

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=fire_service_coverage'

# 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/fire_service_coverage?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.