Skip to content

← All sections

Nearby traffic sensors and observations

Traffic sensors within 5 km of the address with their observed traffic: vehicles per hour, heavy-vehicle share, annual average daily traffic, peak hour and speed limit. A nearby sensor may sit on a road that does not serve the address.

traffic20 fields20 of these fields open in the demo
Source
Statens vegvesen
Geography
Around the address
Reported stale after
1 day
Access
Requires an API key granted this section
Contract version
2
In packages
traffic_and_sensors

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
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
329

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
Norsk lisens for offentlige data 2.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av Statens vegvesen

API warnings

The API returns these notes in warnings.

  • Sensors within 5 km by straight line from the address point. Proximity is geometric and does not establish that the sensor measures a road serving this address — the nearest sensor may be on a motorway the address cannot reach.
  • updated_at is import time, not the measurement interval, and this is not a live congestion feed. An empty section means no sensor within 5 km, which is the usual case away from main roads and says nothing about traffic there.
  • Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
  • walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Provider-contract fields

8 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.

FieldTypeRoleDemo
sensor_idstring | nullcontextopen
roadstring | nullcontextopen
road_categorystring | nullcontextopen
municipality_codestring | nullcontextopen
county_codestring | nullcontextopen
latnumber | nullcontextopen
lonnumber | nullcontextopen
vehicles_per_hourinteger | nullvalueopen
heavy_vehicle_pctnumber | null (%)valueopen
coverage_pctnumber | null (%)valueopen
avg_daily_volumeinteger | nullvalueopen
avg_daily_heavyinteger | nullvalueopen
peak_hourinteger | nullcontextopen
peak_hour_volumeinteger | nullvalueopen
road_speed_limitinteger | nullvalueopen
straight_line_distance_minteger | null (m)valueopen
updated_atstring | nullcontextopen
routeobjectcontextopen
walk_routeobjectcontextopen
cycle_routeobjectcontextopen

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

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