Skip to content

← All sections

Electricity use in the municipality (Elhub)

Electricity use in the address's kommune from Elhub open data: private, business and industry kWh over twelve months and private use per metering point, against Norway. Kommune totals, not this household's consumption.

electricity_consumption15 fields15 of these fields open in the demo
Source
Elhub energy data (Elhub AS)
Geography
Municipality
Reported stale after
45 days
Access
Requires an approved pilot customer and named section access
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
18 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 17 Nov 2026
Newest record
17 Nov 2026
Municipalities with data
358

Measured 19 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: approved pilot customer and named section access

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.

Elhub energy data: reuse terms for the aggregates not confirmed. Pending legal review.

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

  • Kommune totals from Elhub's open data, not this household's consumption: there is no public per-meter data. private_kwh_per_metering_point_12m is the kommune's private (household) kWh over the last twelve published months divided by the mean number of private metering points; one household can have several meters, a cabin kommune's private meters include cabins, and the figure reflects climate, heating mix and dwelling size together. Elhub publishes with about two weeks' lag and revises recent months.
  • Months are calendar months in Norwegian time. Annual fields are null unless that consumer group has twelve consecutive full months with all expected hours (including daylight-saving changes). *_complete_months reports complete months per group; months_covered counts stored months across groups and does not prove annual coverage. Monthly ratios are null for incomplete months. The Norway comparison requires complete private periods for every municipality represented in the stored window; an entirely absent municipality cannot be detected from this source snapshot. fetched_at is the oldest contributing import time. period_end is the latest stored month.

Provider-contract fields

6 of 15 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
municipality_codestring | nullcontextopen
period_startdate | nullcontextopen
period_enddate | nullcontextopen
months_coveredinteger | nullcontextopen
private_complete_monthsinteger | nullcontextopen
business_complete_monthsinteger | nullcontextopen
industry_complete_monthsinteger | nullcontextopen
private_kwh_12mnumber | null (kWh)valueopen
private_metering_pointsnumber | nullvalueopen
private_kwh_per_metering_point_12mnumber | nullvalueopen
norway_private_kwh_per_metering_point_12mnumber | nullcontextopen
business_kwh_12mnumber | null (kWh)valueopen
industry_kwh_12mnumber | null (kWh)valueopen
private_monthly_kwh_per_metering_pointarray<object> | nullvalueopen
fetched_attimestamp | 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=electricity_consumption'

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