NVDB phase-A road segments within 5 km
Road stretches NVDB registers in phase A (anlegg) within 5 km, grouped by road number and kommune. Phase A is the source classification, not independent confirmation of active work at a specific site; the result has no project boundary, contractor, start date or completion date.
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: 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
- Stated in catalogue evidence
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 (NLOD 2.0)
API warnings
The API returns these notes in warnings.
- These are road stretches registered by NVDB in phase A (anlegg), grouped by road number and kommune. Phase A is source classification, not independent confirmation of active work at a specific site. Planned-phase records are not held, so an empty result says nothing about planned works.
- Each row is a grouping of road-network segments, not a project record or verified worksite. NVDB supplies no project boundary, contractor, construction start or completion date here. nvdb_first_registered and nvdb_last_registered are NVDB registration dates, not work dates. Distance is straight-line to the nearest segment.
Provider-contract fields
7 of 16 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 |
|---|---|---|---|
| project_key | string | null | context | open |
| name | string | null | value | open |
| phase | string | null | value | open |
| nearest_road_reference | string | null | value | open |
| road_category | string | null | context | open |
| road_category_name | string | null | context | open |
| road_number | integer | null | context | open |
| municipality_code | string | null | context | open |
| distance_m | integer | null (m) | value | open |
| ring | string | null | value | open |
| segments_within_5km | integer | null | context | open |
| length_within_5km_m | integer | null | value | open |
| nvdb_first_registered | string | null | value | open |
| nvdb_last_registered | string | null | context | open |
| map_url | string | null | context | open |
| updated_at | string | 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=road_projects_nearby'
# 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/road_projects_nearby?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.