Skip to content

← All sections

Traffic volume (ÅDT) on the nearest counted road stretches

Annual average daily traffic (ÅDT) and heavy-vehicle share on the nearest counted road stretches from NVDB. The nearest counted stretch is not necessarily the road the address fronts.

traffic_volume10 fields10 of these fields open in the demo
Source
Statens vegvesen NVDB
Geography
Around the address
Reported stale after
120 days
Access
Requires an API key granted this section
Contract version
1
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
15 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities with data
357

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 NVDB

API warnings

The API returns these notes in warnings.

  • NVDB objects imported by object type; distance is straight-line metres from the address point to the object's geometry (a line or area is met where it passes closest). Coverage is the object types and areas the pipeline has fetched.
  • ÅDT is Statens vegvesen's annual average daily traffic for the stretch, from counting or estimation as stated in basis; the nearest counted stretch is not necessarily the road the address fronts.

Provider-contract fields

4 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
nvdb_idinteger | nullcontextopen
object_type_namestring | nullcontextopen
road_referencestring | nullcontextopen
municipality_codestring | nullcontextopen
adt_totalinteger | nullvalueopen
heavy_vehicle_share_pctinteger | null (%)valueopen
adt_yearinteger | null (årstall)valueopen
basisstring | nullcontextopen
straight_line_distance_minteger | null (m)valueopen
created_atstring | 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=traffic_volume'

# 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_volume?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.