Skip to content

← All sections

Public EV charging near the address

Public EV charging near the address from NOBIL: distance to the nearest and nearest fast station, counts of stations and charging points within 1 km and 5 km, and the highest power. Distances are straight-line, not driving distance.

ev_charging10 fields5 of these fields open in the demo
Source
NOBIL (Enova / Norsk elbilforening) · CC BY 4.0
Geography
The address point
Reported stale after
3 days
Access
Requires an API key granted this section
Contract version
1
In packages
traffic_and_sensors, 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
22 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

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
Stated in catalogue evidence
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© NOBIL (Enova / Norsk elbilforening) · CC BY 4.0, CC BY 4.0

API warnings

The API returns these notes in warnings.

  • Public charging stations in NOBIL, Norway's national register, by straight-line distance from the address point (not driving distance); stations more than ~30 km away are not considered. Fast means at least one connector of 50 kW or more, derived from each connector's published capacity text; a capacity NOBIL does not state is left out rather than guessed. Private and home chargers are not in the register.
  • available_now counts connectors whose most recent status on NOBIL's real-time stream was AVAILABLE within the last two hours. The stream reports changes only and not every operator reports to it, so available_now is null when no fresh known status exists. A numeric value counts only reporting connectors; it is not proof of complete station coverage.

Provider-contract fields

9 of 10 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
nearest_station_minteger | nullvalueopen
nearest_fast_station_minteger | nullvalueopen
stations_within_1kminteger | nullvalueopen
stations_within_5kminteger | nullvalueopen
fast_stations_within_5kminteger | nullvalueopen
charging_points_within_5kminteger | nullvalue—
fast_points_within_5kminteger | nullvalue—
max_kw_within_5kmnumber | nullvalue—
nearest_stationsarray<object> | nullvalue—
updated_atstring | nullcontext—

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=ev_charging'

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