Typical household energy use in the address's county
Typical household energy use in the address's county from SSB's energy survey: kWh per household, per m2 and per person, by energy source. A survey average to compare a bill or an energy certificate against.
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
- Creative Commons Attribution 4.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Publisher terms
Attribution and note
Shown from the contract in its original language.
© SSB 14578 and 14580 (Husholdningenes energibruk), CC BY 4.0
API warnings
The API returns these notes in warnings.
- An average over a sample of households in the county from SSB's energy survey, which runs every few years (survey_year says which); it is a baseline to compare a bill or an energy certificate against, not a measurement of this dwelling.
- Published only for the 2020-2023 counties: an address in Østfold, Akershus or Buskerud reads Viken, in Vestfold or Telemark reads Vestfold og Telemark, in Troms or Finnmark reads Troms og Finnmark. survey_region_name names the region actually used.
Provider-contract fields
10 of 17 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 |
|---|---|---|---|
| county_code | string | null | context | open |
| survey_region_code | string | null | context | open |
| survey_region_name | string | null | context | open |
| survey_year | integer | null (årstall) | context | open |
| kwh_per_household_total | number | null | value | open |
| kwh_per_household_electricity | number | null | value | open |
| kwh_per_household_oil | number | null | value | open |
| kwh_per_household_wood | number | null | value | open |
| kwh_per_household_gas_district_heating | number | null | value | open |
| electricity_share | number | null (andel) | value | open |
| kwh_per_m2 | number | null (m2) | value | open |
| kwh_per_person | number | null | value | open |
| dwelling_area_m2 | number | null (m2) | value | open |
| persons_per_household | number | null | value | open |
| norway_kwh_per_household_total | number | null | context | open |
| norway_kwh_per_m2 | number | null (m2) | context | open |
| updated_at | 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=household_energy_baseline'
# 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/household_energy_baseline?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.