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.

Parameter	Requirement	JSON type	Description
`stop_place_id`	required	string	National Stop Register id from search_stops.
`number_of_departures`	optional	integer	Maximum estimated calls, 1-50.
`time_range_seconds`	optional	integer	Search window from now, 60-86400 seconds. Unit: seconds.
`limit`	optional	integer	Gateway page size; default 25, maximum 100.
`offset`	optional	integer	Number 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.

Result

Source: Entur. Retrieved 2026-10-22T13:24:52Z in 0.428 seconds.

id:

NSR:StopPlace:62339

name:

Lillestrøm stasjon

latitude:

59.952915

longitude:

11.045364

estimatedCalls:

10 results

realtime:
yes
aimedDepartureTime:
2026-10-22T15:25:00+02:00
expectedDepartureTime:
2026-10-22T15:25:00+02:00
destinationDisplay:
frontText:
Dal
quay:
id:
NSR:Quay:754
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:R13
name:
Drammen-Oslo S-Dal
publicCode:
R13
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:25:00+02:00
expectedDepartureTime:
2026-10-22T15:25:00+02:00
destinationDisplay:
frontText:
Asker
quay:
id:
NSR:Quay:102055
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:L1
name:
Spikkestad-Oslo S-Lillestrøm
publicCode:
L1
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:26:00+02:00
expectedDepartureTime:
2026-10-22T15:29:41+02:00
destinationDisplay:
frontText:
Skien
quay:
id:
NSR:Quay:756
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:RE11
name:
Eidsvoll-Oslo S-Skien
publicCode:
RE11
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:30:00+02:00
expectedDepartureTime:
2026-10-22T15:30:37+02:00
destinationDisplay:
frontText:
Oslo Lufthavn
quay:
id:
NSR:Quay:761
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
FLT:Line:FLY1
name:
FLY1
publicCode:
FLY1
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:35:00+02:00
expectedDepartureTime:
2026-10-22T15:35:00+02:00
destinationDisplay:
frontText:
Eidsvoll
quay:
id:
NSR:Quay:761
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:RE11
name:
Eidsvoll-Oslo S-Skien
publicCode:
RE11
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:36:00+02:00
expectedDepartureTime:
2026-10-22T15:36:00+02:00
destinationDisplay:
frontText:
Kongsberg
quay:
id:
NSR:Quay:754
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:R13
name:
Drammen-Oslo S-Dal
publicCode:
R13
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:40:00+02:00
expectedDepartureTime:
2026-10-22T15:40:00+02:00
destinationDisplay:
frontText:
Spikkestad
quay:
id:
NSR:Quay:747
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:L1
name:
Spikkestad-Oslo S-Lillestrøm
publicCode:
L1
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:43:00+02:00
expectedDepartureTime:
2026-10-22T15:43:00+02:00
destinationDisplay:
frontText:
Kongsvinger
quay:
id:
NSR:Quay:750
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:R14
name:
Asker-Oslo S-Kongsvinger
publicCode:
R14
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:45:00+02:00
expectedDepartureTime:
2026-10-22T15:45:28+02:00
destinationDisplay:
frontText:
Lillehammer
quay:
id:
NSR:Quay:754
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:RE10
name:
Drammen-Oslo S-Lillehammer
publicCode:
RE10
transportMode:
rail
realtime:
yes
aimedDepartureTime:
2026-10-22T15:46:00+02:00
expectedDepartureTime:
2026-10-22T15:46:00+02:00
destinationDisplay:
frontText:
Asker
quay:
id:
NSR:Quay:747
name:
Lillestrøm stasjon
serviceJourney:
journeyPattern:
line:
id:
VYG:Line:R14
name:
Asker-Oslo S-Kongsvinger
publicCode:
R14
transportMode:
rail

limit:

offset:

returned:

has_more_results:

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

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
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

Use the stop place ID for details, and distinguish scheduled times from real-time estimates.

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.