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-09-24T05:24:53Z in 0.190 seconds.

id:

NSR:StopPlace:9679

name:

Brumunddal sentrum

latitude:

60.883208

longitude:

10.941235

estimatedCalls:

10 results

realtime:
yes
aimedDepartureTime:
2026-09-24T07:25:00+02:00
expectedDepartureTime:
2026-09-24T07:25:00+02:00
destinationDisplay:
frontText:
Moelv
quay:
id:
NSR:Quay:16577
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:605
name:
Gjøvik - Moelv - Brumunddal
publicCode:
605
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-24T07:25:00+02:00
expectedDepartureTime:
2026-09-24T07:25:00+02:00
destinationDisplay:
frontText:
Stange vgs.
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:616
name:
Brumunddal - Stange vgs.
publicCode:
616
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-24T07:26:00+02:00
expectedDepartureTime:
2026-09-24T07:26:00+02:00
destinationDisplay:
frontText:
Nybygda
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:635
name:
Brumunddal-Nybygda-Brumunddal
publicCode:
635
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-24T07:30:00+02:00
expectedDepartureTime:
2026-09-24T07:30:00+02:00
destinationDisplay:
frontText:
Rudshøgda
quay:
id:
NSR:Quay:16577
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:615
name:
Brumunddal-Rudshøgda-Moelv
publicCode:
615
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-24T07:30:00+02:00
expectedDepartureTime:
2026-09-24T07:30:00+02:00
destinationDisplay:
frontText:
Kylstad skole
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:645
name:
Brmunddal-Nybygda-Hamar
publicCode:
645
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-24T07:30:00+02:00
expectedDepartureTime:
2026-09-24T07:30:09+02:00
destinationDisplay:
frontText:
Storhamar v.g. skole
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:612
name:
Moelv - Hersoug - Brumunddal
publicCode:
612
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-24T07:30:00+02:00
expectedDepartureTime:
2026-09-24T07:30:32+02:00
destinationDisplay:
frontText:
Fossum
quay:
id:
NSR:Quay:16577
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:23
name:
Stange-Hamar-Brumunddal
publicCode:
B23
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-24T07:33:00+02:00
expectedDepartureTime:
2026-09-24T07:33:00+02:00
destinationDisplay:
frontText:
Hamar
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:23
name:
Stange-Hamar-Brumunddal
publicCode:
B23
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-24T07:35:00+02:00
expectedDepartureTime:
2026-09-24T07:35:00+02:00
destinationDisplay:
frontText:
Hamar - Stange
quay:
id:
NSR:Quay:16574
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:23
name:
Stange-Hamar-Brumunddal
publicCode:
B23
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-24T07:36:00+02:00
expectedDepartureTime:
2026-09-24T07:36:00+02:00
destinationDisplay:
frontText:
Gaupen skole
quay:
id:
NSR:Quay:100570
name:
Brumunddal sentrum
serviceJourney:
journeyPattern:
line:
id:
INN:Line:613
name:
Brumunddal - Gaupen
publicCode:
613
transportMode:
bus

limit:

offset:

returned:

has_more_results:

truncated:

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.