Nearest toll stations with list prices
toll_stations_nearby31 fields26 of these fields open in the demo
Available with: trial key (open fields) · bought bundle or agreed plan (all fields) · Pricing
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- The ten nearest toll stations within 15 km of the address, straight line in EPSG:25833, nearest first. A toll station near the address says nothing about whether any trip from the address passes it or what a trip costs: the route decides, and so do the vehicle, the AutoPASS agreement, the hourly rule and the time of day.
- Prices are the operator's published list prices per passage in NOK as held in NVDB: price_small_vehicle_nok for a light vehicle, price_large_vehicle_nok for a heavy one, price_small_ev_nok for a zero-emission light vehicle where NVDB states one. rush_* apply only inside the stated morning and afternoon windows (HH:MM, local time). A price of 0 in the register is served as absent. Reference prices, not a quote: discounts, subscriptions, passage groups and charge caps are not modelled.
- There is no passage count in this section and none is published openly: SSB has no toll-passage table, the toll companies publish no counts, and Statens vegvesen's traffic counters are not tied to toll stations. Station positions are as registered in NVDB; position_accuracy_m gives the registered accuracy where NVDB states one, and many stations are only placed to within hundreds of metres. Ferry charging points (station_type Ferjeinnkrevingspunkt) and toll points on local or private roads are included and labelled by station_type.
- Licence: NLOD 2.0 (Norsk lisens for offentlige data), published by Statens vegvesen through NVDB. Attribution: Statens vegvesen, NVDB. Station and price data are maintained by the toll operators and the road owners and can lag a decision by weeks.
Fields
13 of 31 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” return values to anonymous callers; the rest require a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| nvdb_id | integer | null | context | — |
| station_id | integer | null | context | — |
| name | string | null | value | open |
| facility_name | string | null | value | open |
| station_type | string | null | value | open |
| owner | string | null | context | open |
| price_small_vehicle_nok | number | null (NOK) | value | open |
| price_large_vehicle_nok | number | null (NOK) | value | open |
| price_small_ev_nok | number | null (NOK) | value | open |
| rush_price_small_vehicle_nok | number | null (NOK) | value | open |
| rush_price_large_vehicle_nok | number | null (NOK) | value | open |
| rush_morning_from | string | null | context | open |
| rush_morning_to | string | null | context | open |
| rush_afternoon_from | string | null | context | open |
| rush_afternoon_to | string | null | context | open |
| time_differentiated | boolean | null | value | open |
| hourly_rule | string | null | value | open |
| hourly_rule_minutes | integer | null (min) | context | open |
| free_with_hc_tag | boolean | null | value | open |
| charge_direction | string | null | value | open |
| established_year | integer | null (årstall) | context | open |
| approved_until_year | integer | null (årstall) | context | open |
| status | string | null | context | open |
| info_url | string | null | context | — |
| municipality_code | string | null | context | open |
| position_accuracy_m | number | null | context | open |
| latitude | number | null | context | open |
| longitude | number | null | context | open |
| straight_line_distance_m | integer | null (m) | value | open |
| nvdb_modified | string | null | context | — |
| fetched_at | string | null | context | — |
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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=toll_stations_nearby' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/toll_stations_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.