Allemannsdata Wiki
Manual search

get_departures

Get planned and real-time departures from an Entur stop place.

Signature: get_departures(stop_place_id: string, required; number_of_departures: integer, optional, default 10; time_range_seconds: integer, seconds, optional, default 7200; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/entur/get_departures/?stop_place_id={stop_place_id}&number_of_departures=10&time_range_seconds=7200&limit=25&offset=0

Replace {stop_place_id}, {number_of_departures}, {time_range_seconds} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/entur/get_departures?stop_place_id={stop_place_id}&number_of_departures=10&time_range_seconds=7200&limit=25&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
stop_place_idrequiredstringNational Stop Register id from search_stops.
number_of_departuresoptionalintegerMaximum estimated calls, 1-50.
time_range_secondsoptionalintegerSearch window from now, 60-86400 seconds. Unit: seconds.
limitoptionalintegerGateway page size; default 25, maximum 100.
offsetoptionalintegerNumber of list items to skip; default 0.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/entur/get_departures?stop_place_id={stop_place_id}&number_of_departures=10&time_range_seconds=7200&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/entur/get_departures?stop_place_id={stop_place_id}&number_of_departures=10&time_range_seconds=7200&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/entur/get_departures?stop_place_id={stop_place_id}&number_of_departures=10&time_range_seconds=7200&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "entur",
  "operation": "get_departures",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string. National Stop Register id from search_stops.
Type: integer. Maximum estimated calls, 1-50.
Type: integer. Search window from now, 60-86400 seconds. Unit: seconds.

Result

Source: Entur. Retrieved 2026-09-24T04:22:13Z in 0.130 seconds.

Open the place page for this point

id:
NSR:StopPlace:43708
name:
Evjen
latitude:
63.289924
longitude:
9.842491
estimatedCalls:

10 results

  1. realtime:
    yes
    aimedDepartureTime:
    2026-09-24T06:27:00+02:00
    expectedDepartureTime:
    2026-09-24T06:28:32+02:00
    destinationDisplay:
    frontText:
    Trondheim S via Orkanger skysst.
    quay:
    id:
    NSR:Quay:75033
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_310
    name:
    Trondheim - Orkanger - Fannrem
    publicCode:
    310
    transportMode:
    bus
  2. realtime:
    yes
    aimedDepartureTime:
    2026-09-24T06:23:00+02:00
    expectedDepartureTime:
    2026-09-24T06:30:59+02:00
    destinationDisplay:
    frontText:
    Orkanger skysstasjon
    quay:
    id:
    NSR:Quay:75033
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_460
    name:
    Orkanger - Meldal - Berkåk
    publicCode:
    460
    transportMode:
    bus
  3. realtime:
    yes
    aimedDepartureTime:
    2026-09-24T06:37:00+02:00
    expectedDepartureTime:
    2026-09-24T06:41:14+02:00
    destinationDisplay:
    frontText:
    Fannrem stasjon
    quay:
    id:
    NSR:Quay:75032
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_310
    name:
    Trondheim - Orkanger - Fannrem
    publicCode:
    310
    transportMode:
    bus
  4. realtime:
    yes
    aimedDepartureTime:
    2026-09-24T06:42:00+02:00
    expectedDepartureTime:
    2026-09-24T06:42:00+02:00
    destinationDisplay:
    frontText:
    Trondheim S via Orkanger skysst.
    quay:
    id:
    NSR:Quay:75033
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_310
    name:
    Trondheim - Orkanger - Fannrem
    publicCode:
    310
    transportMode:
    bus
  5. realtime:
    no
    aimedDepartureTime:
    2026-09-24T06:44:00+02:00
    expectedDepartureTime:
    2026-09-24T06:44:00+02:00
    destinationDisplay:
    frontText:
    Kyrksæterøra via Orkanger
    quay:
    id:
    NSR:Quay:75033
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_5702
    name:
    Kyrksæterøra - Orkanger
    publicCode:
    5702
    transportMode:
    bus
  6. realtime:
    no
    aimedDepartureTime:
    2026-09-24T06:52:00+02:00
    expectedDepartureTime:
    2026-09-24T06:52:00+02:00
    destinationDisplay:
    frontText:
    Berkåk st. via Løkken og Meldal
    quay:
    id:
    NSR:Quay:75032
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_460
    name:
    Orkanger - Meldal - Berkåk
    publicCode:
    460
    transportMode:
    bus
  7. realtime:
    no
    aimedDepartureTime:
    2026-09-24T06:52:00+02:00
    expectedDepartureTime:
    2026-09-24T06:52:00+02:00
    destinationDisplay:
    frontText:
    Meldal vgs via Solbu og Løkken
    quay:
    id:
    NSR:Quay:75032
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_460
    name:
    Orkanger - Meldal - Berkåk
    publicCode:
    460
    transportMode:
    bus
  8. realtime:
    no
    aimedDepartureTime:
    2026-09-24T06:52:00+02:00
    expectedDepartureTime:
    2026-09-24T06:52:00+02:00
    destinationDisplay:
    frontText:
    Meldal vgs via Løkken st.
    quay:
    id:
    NSR:Quay:75032
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_460
    name:
    Orkanger - Meldal - Berkåk
    publicCode:
    460
    transportMode:
    bus
  9. realtime:
    yes
    aimedDepartureTime:
    2026-09-24T06:52:00+02:00
    expectedDepartureTime:
    2026-09-24T06:52:31+02:00
    destinationDisplay:
    frontText:
    Meldal vgs via Løkken st.
    quay:
    id:
    NSR:Quay:75032
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_460
    name:
    Orkanger - Meldal - Berkåk
    publicCode:
    460
    transportMode:
    bus
  10. realtime:
    no
    aimedDepartureTime:
    2026-09-24T06:57:00+02:00
    expectedDepartureTime:
    2026-09-24T06:57:00+02:00
    destinationDisplay:
    frontText:
    Trondheim S via Orkanger skysst.
    quay:
    id:
    NSR:Quay:75033
    name:
    Evjen
    serviceJourney:
    journeyPattern:
    line:
    id:
    ATB:Line:2_310
    name:
    Trondheim - Orkanger - Fannrem
    publicCode:
    310
    transportMode:
    bus
limit:
25
offset:
0
returned:
10
has_more_results:
no
truncated:
no
Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the get_departures lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.

AI agent? Read the complete navigation and programming guide.