Skip to content

← All sections

Fire and burglary exposure indices for the address, with every factor shown

Rule-based 0-100 screening indices for fire and burglary exposure, not calibrated probabilities, expected losses, premiums or underwriting decisions. Every factor and input is listed; missing inputs add no points, so low coverage is not low exposure.

fire_and_burglary_indicators10 fields4 of these fields open in the demo
Source
Approach, composed from Matrikkel, SEFRAK, NVDB, BRREG, SSB, Politiloggen and KOSTRA fields
Geography
The address point
Reported stale after
30 days
Access
Requires an API key granted this section
Contract version
1
In packages
hazard_screen, fire_and_damage, calculations

Read about this data source →

Status right now

State
Stale
The clock used for combined section status is older than its limit. Data freshness is shown separately.
Last loaded
11 Apr 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

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

Model and method

How do fire and burglary risk factors stack up at the address?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Index
Declared maturity
Marked stable in the catalogue
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • Matrikkel
  • SEFRAK
  • NVDB
  • BRREG
  • SSB
  • police log
  • KOSTRA

Headline output fields

fire_index, burglary_index, fire_factors, burglary_factors, fire_coverage, burglary_coverage

Declared comparison basis

none: indices, not probabilities

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

API warnings

The API returns these notes in warnings.

  • Two 0-100 indices, higher is more exposed, each the sum of documented factor points (fire_factors, burglary_factors) over the inputs listed; a factor whose input is missing contributes 0, never a mid-scale default. The wood_walls fire factor scores only a unique SEFRAK observation matched to the selected building; the separate 500 m wall-material share is context, not a substitute building fact. They rank addresses against each other and are NOT probabilities: no open register holds fire or burglary outcomes per address to calibrate against (DSB and SSB publish per kommune, the police per district). fire_coverage and burglary_coverage are the share (0-1) of the 8 factors on each side that had a real observation rather than a missing input contributing 0 — a low-coverage index is thin evidence, not a low-exposure address. municipal_scope_inputs names the inputs keys (inside `inputs`) that are kommune-wide KOSTRA/SSB rates rather than this address's own history. method names the weighting version; a fitted model replaces it when a partner supplies claim outcomes.
  • fire_station_drive and police_distance are not observed since 13 Oct 2026: their only source was the proximity enrichment table, filled nationally once in March 2026, and a drive time or distance that old is thinner evidence than none. Each contributes 0, its input is null, and fire_coverage and burglary_coverage count it as missing, so neither share exceeds 0.88 until a live measurement replaces them.
  • The wood_walls input depends on a SEFRAK wall-material value. A bounded comparison of the official Geonorge WFS and Riksantikvaren OGC API found conflicting values, and the current value has not been source-adjudicated. Treat this component as an uncertain historical screening input, not verified present-day wall construction or an insurance rating.
  • inputs.theft_burglary_90d_5km counts Politiloggen theft and burglary messages whose named settlement, grunnkrets/bydel neighbourhood or postal area has its centre within 5 km of the address. Politiloggen gives no incident position; kommune-centroid-only messages are excluded. A neighbourhood centre is approximate and does not establish that the incident occurred within 5 km. inputs.police_log_match_share is the fraction of the kommune's own theft/burglary messages in the same 90 days matched by those same settlement, neighbourhood or postal methods. A zero count beside low matching coverage is missing placement evidence, not proof that no incidents occurred.

Provider-contract fields

6 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.

FieldTypeRoleDemo
fire_indexinteger | nullvalueopen
fire_factorsobject | nullvalue—
fire_coveragenumber | nullvalue—
burglary_indexinteger | nullvalueopen
burglary_factorsobject | nullvalue—
burglary_coveragenumber | nullvalue—
municipal_scope_inputsarray<string> | nullcontext—
inputsobject | nullcontext—
methodstring | nullcontextopen
computed_atstring | nullcontextopen

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_and_burglary_indicators'

# 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_and_burglary_indicators?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.