Skip to content

← All sections

Nearest public transport stops with observed service

Nearest public transport stops within 3 km with observed service over a stated window: departures, distinct lines, average delay and cancelled departures, from Entur's live departure feed.

public_transport16 fields16 of these fields open in the demo
Source
Entur SIRI-ET (national real-time), aggregated by Approach
Geography
Around the address
Reported stale after
2 days
Access
Requires an API key granted this section
Contract version
2
In packages
neighbourhood_life, 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
not measured
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
330

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 Entur SIRI-ET (national real-time), aggregated by Approach

API warnings

The API returns these notes in warnings.

  • Departures observed in Entur's national real-time feed (SIRI-ET, every monitored journey) over the stated window (window_from to window_to), rolled up from platform to stop and aggregated per stop at refresh time. Only journeys an operator reports in real time are counted, so a stop served solely by unmonitored departures reads low or absent; not a complete timetable or a service guarantee.
  • Limited to stops within 3 km: an address with no observed stop that close gets no record, not a stop from another town. transit_stops carries the full national stop register for positions. Straight-line UTM33 distance, not walking distance.
  • 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

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

FieldTypeRoleDemo
stop_idstring | nullcontextopen
stop_namestring | nullcontextopen
transport_modesarray<string> | nullvalueopen
latnumber | nullcontextopen
lonnumber | nullcontextopen
straight_line_distance_mnumber | null (m)valueopen
observed_departuresinteger | nullvalueopen
distinct_linesinteger | nullvalueopen
avg_delay_minnumber | null (min)contextopen
cancelled_departuresinteger | nullcontextopen
window_fromstring | nullcontextopen
window_tostring | nullcontextopen
refreshed_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=public_transport'

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