Household grid tariff (nettleie) of the grid company (NVE)
grid_tariffs22 fields22 of these fields open in the demo
Available with: trial key (open fields) · bought bundle or agreed plan (all fields) · Pricing
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.
- The tariff of the grid company, not this household's bill. Each record is one month and one of NVE's four example customers (customer_example gives the demanded power and yearly use, for example 4 kW in summer and 6 kW in winter and 20 000 kWh a year); the company's tariff is evaluated for that customer. A real bill depends on the household's own demanded power, consumption and meter, and adds the electricity price, the supplier's margin and, where they apply, the electricity tax and VAT: none of those are here, and neither is the price of the electricity itself.
- Two parts: the fixed charge (fastledd, fixed_charge_per_month_*, NOK per month), which varies with the customer's demanded power (power_step_from_kw to power_step_to_kw; 0 means the tariff has no power steps), and the energy charge (energiledd, energy_charge_ore_per_kwh_*, øre per kWh), which NVE gives as a monthly average weighted with Statnett's adjusted infeed profile because the charge can vary by hour, weekday and season. calculated_price_per_month_* is NVE's calculated monthly grid cost for the example customer (fixed charge plus energy charge times that month's share of the yearly use) in NOK, and calculated_ore_per_kwh_* the same cost per kWh. _excl is excluding and _incl including levies: has_vat and has_consumption_tax say which apply (VAT does not apply in Nord-Norge), so the two are equal where neither does.
- The company is found by organisation number through grid_company, so the tariff is only as exact as that match: an address near the border between two grid areas, or one NVE's generalised concession polygons do not place, gets no tariff rather than a guessed one. A company that operates in several counties reports one row per county; county_matches_address is true when the row is the address's own county's and false when it is another county the company reports for.
- One month per row from July 2022, newest first, as reported to NVE: the tariff in force on the first day of the month. A month that has not started is never served. Companies report in January and at each change, and NVE has not checked their conversions to its example customers. For one company (Arva AS) NVE writes some rows with an asterisk ("ARVA AS*") and others without, with different energy charges in the same month; NVE does not say what the asterisk means, so both are served, told apart by nve_company_marker ("*" or empty) and the name as NVE writes it, and neither is chosen for you.
- Licence: NLOD 2.0 (Norsk lisens for offentlige data), as stated for api.nve.no. Attribution: Norges vassdrags- og energidirektorat (NVE), Nettleietariffer; the grid companies report their tariffs to the Norwegian Energy Regulatory Authority (RME) and NVE has not verified their conversions.
Fields
16 of 22 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” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| grid_company_name | string | null | value | open |
| grid_company_org_number | string | null | context | open |
| tariff_month | date | null | value | open |
| tariff_group | string | null | context | open |
| customer_group | integer | null | value | open |
| customer_example | string | null | value | open |
| nve_company_marker | string | null | context | open |
| county_code | string | null | context | open |
| county_matches_address | boolean | null | context | open |
| has_vat | boolean | null | value | open |
| has_consumption_tax | boolean | null | value | open |
| power_step_from_kw | number | null | value | open |
| power_step_to_kw | number | null | value | open |
| fixed_charge_per_month_excl_nok | number | null (NOK) | value | open |
| fixed_charge_per_month_incl_nok | number | null (NOK) | value | open |
| energy_charge_ore_per_kwh_excl | number | null | value | open |
| energy_charge_ore_per_kwh_incl | number | null | value | open |
| calculated_price_per_month_excl_nok | number | null (NOK) | value | open |
| calculated_price_per_month_incl_nok | number | null (NOK) | value | open |
| calculated_ore_per_kwh_excl | number | null | value | open |
| calculated_ore_per_kwh_incl | number | null | value | 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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=grid_tariffs' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/grid_tariffs?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.