Radon susceptibility at the address point
Radon susceptibility class at the address point from the NGU/DSA radon aktsomhet map. It is a screening class from geology and measurements, not a measured radon level for the building.
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 NGU/DSA national radon aktsomhet map
API warnings
The API returns these notes in warnings.
- Screening class from geology, airborne uranium surveys and indoor-air measurements, not a measured radon level for this building. aktsomhet_grad is the source's class code — megetHøy, høy, middels, lav or usikker — and aktsomhet_grad_navn its Norwegian name. megetHøy and høy mean measurement is recommended. usikker is a class the source assigns where its data does not support one; it is not low risk. An address with no record lies outside every mapped polygon, which is also unknown, never low.
- National aktsomhet map version 2 (NGU/DSA, September 2026), NLOD. megetHøy is the 2014 map's 'særlig høy'; middels and lav split its 'moderat til lav'. The class is modelled from the share of indoor measurements above 100 Bq/m³, uranium surveys and geology; the level in a building depends on construction and must be measured. Where polygons overlap at the point the highest class answers, and usikker ranks above lav.
Provider-contract fields
1 of 3 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 |
|---|---|---|---|
| aktsomhet_grad | string | null | context | open |
| aktsomhet_grad_navn | string | null | value | open |
| datauttaksdato | string | 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=radon'
# 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/radon?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.