Grid company and grid area (Elhub)
The grid company (nettselskap) and grid area serving the address, found by matching NVE's concession polygon to Elhub's register, with the match basis stated.
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: 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.
API warnings
The API returns these notes in warnings.
- The grid company is found by organisation number: NVE's concession polygon at the address names the holder (concession_holder_org_number), and Elhub's register names the grid owner with that number (grid_company_*). Nothing is matched on names. elhub_match says why a step stopped: no_unambiguous_concession_polygon (the address lies outside NVE's generalised polygons and the nearest one is either over 2 km away or not clearly nearer than another holder's), or concession_holder_not_an_active_elhub_grid_owner (NVE's layer still names a company since merged into another; the successor is not inferred).
- concession_match is inside_concession_polygon, or nearest_concession_polygon with concession_distance_m when NVE's coastline generalisation left the address just outside every polygon; the nearest is used only within 2 km and when no other holder's polygon lies within 1 km beyond it.
- A grid company can operate several grid areas (nettområder). grid_area_id is set only when the company has one active grid area, or exactly one of them lies in the price zone of NVE's elspot polygon at the address (nve_price_zone); otherwise grid_area_resolution is ambiguous and candidate_grid_areas lists the company's active areas. price_area follows the grid area, or the company when all its areas share one price area, or NVE's elspot zone at the address when the company has a grid area in that zone (price_area_resolution says which); otherwise it is null. The tariff (nettleie) is not included.
- Grid areas and grid owners: Elhub energy data (Elhub AS), Norsk lisens for offentlige data (NLOD). Concession polygons and price zones: NVE, NLOD.
Provider-contract fields
6 of 20 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 |
|---|---|---|---|
| concession_holder_name | string | null | context | open |
| concession_holder_org_number | string | null | context | open |
| concession_holder_type | string | null | context | open |
| concession_match | string | null | context | open |
| concession_distance_m | integer | null (m) | context | open |
| elhub_match | string | null | context | open |
| grid_company_name | string | null | value | open |
| grid_company_org_number | string | null | value | open |
| active_grid_areas | integer | null | context | open |
| grid_area_id | string | null | value | open |
| grid_area_name | string | null | value | open |
| grid_area_eic | string | null | context | open |
| grid_company_gln | string | null | context | open |
| grid_area_resolution | string | null | context | open |
| candidate_grid_areas | array<object> | null | value | open |
| price_area | string | null | value | open |
| price_area_resolution | string | null | context | open |
| price_area_eic | string | null | context | open |
| nve_price_zone | string | null | context | 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 --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=grid_company'
# 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/grid_company?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.