Insured water and natural damage in the municipality
Insured water and natural-damage claims in the address's kommune by year and claim type: number of claims and compensation, from DSB and Finans Norge. Public aggregates, not the loss history of any property.
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
- Norsk lisens for offentlige data 2.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av DSB / Finans Norge Forsikringsdrift · NLOD
API warnings
The API returns these notes in warnings.
- Public DSB aggregates, not property-level loss history. Only exact source municipality codes are matched; historical boundary/code changes may fragment the series. Groups below five claims are withheld: absent means none reported or suppressed, never a known zero. Reporting before July 2022 is incomplete, so 2022 is not a full-year trend baseline. Current-year figures are provisional and all estimates may be revised. Compensation is estimated nominal NOK excluding deductibles; zero and negative amounts may be valid. Provider updates monthly; fetched_at is retrieval time, not publication time. NP=natural damage, VA=water damage, AB=interruption/accommodation costs. No fire claims, per-policy risk denominator or individual cause data are supplied. Attribute DSB under NLOD.
Provider-contract fields
2 of 12 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 |
|---|---|---|---|
| reporting_year | integer | null (year) | context | open |
| period_is_partial | boolean | null | context | open |
| municipality_code | string | null | context | open |
| municipality_name | string | null | context | open |
| claim_type | string | null | context | open |
| claim_type_name | string | null | context | open |
| nature_event_code | string | null | context | open |
| nature_event_name | string | null | context | open |
| claim_count | integer | null (claims) | value | open |
| compensation_nok | number | null (NOK) | value | open |
| snapshot_hash | string | null | context | open |
| fetched_at | timestamp | 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=insurance_claims'
# 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/insurance_claims?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.