Skip to content

← All sections

District heating concession area at the address

District-heating concession area at the address, with operator, facility and licensed capacity. Inside one, the kommune can require connection for new buildings; whether this address is connected is not included.

district_heating_area11 fields11 of these fields open in the demo
Source
NVE Fjernvarme konsesjonsområder
Geography
The address point
Reported stale after
400 days
Access
Requires an API key granted this section
Contract version
1
In packages
energy_and_power

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
17 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 17 Nov 2026
Newest record
17 Nov 2026
Municipalities with data
56

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.

  • Inside a concession area the kommune can require new buildings to connect to district heating (plan- og bygningsloven § 27-5); whether this particular address is connected, and at what price, is not in the layer.
  • 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 11 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
operatorstring | nullcontextopen
facilitystring | nullcontextopen
municipality_namesstring | nullcontextopen
licensed_capacity_mwnumber | null (MW)contextopen
concession_urlstring | 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=district_heating_area'

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