get_station_board

Live departure/arrival board for one Norwegian railway station, straight from Bane NOR - the data shown on the physical station screens.

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.

https://allemannsdata.com/wiki/kilder/banenor/get_station_board/?station={station}&direction=all&minutes_ahead=120&line={line}&destination={destination}&operator={operator}&max_trains=20&include_formation=false&limit=25&offset=0

Replace {station}, {direction}, {minutes_ahead}, {line}, {destination}, {operator}, {max_trains}, {include_formation} 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/banenor/get_station_board?station={station}&direction=all&minutes_ahead=120&line={line}&destination={destination}&operator={operator}&max_trains=20&include_formation=false&limit=25&offset=0.

Parameter	Requirement	JSON type	Description
`station`	required	string	Bane NOR station code, e.g. "OSL" (Oslo S), "BRG" (Bergen), "TND" (Trondheim S). Use lookup_station to find a code. Unknown codes error.
`direction`	optional	string	"all" (default), "departures" or "arrivals".
`minutes_ahead`	optional	integer	Window from now, in minutes (default 120).
`line`	optional	union	Only this line, e.g. "L2", "R12", "FLY1". Exact match.
`destination`	optional	union	Only trains whose final stop is this station NAME (e.g. "Skien", not "SKN").
`operator`	optional	union	Only this operator code, e.g. "VY", "VYG", "FLY", "GAG", "SJN".
`max_trains`	optional	integer	Cap on trains returned (default 20), applied upstream to the trains departing/arriving next.
`include_formation`	optional	boolean	Also return train formation per train where reported: wagon order and types, open/closed state, on-board services (bicycle, quiet, wheelchair, bistro, wlan, ...) and automatic passenger-count occupancy. Verbose; off by default.
`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/banenor/get_station_board?station={station}&direction=all&minutes_ahead=120&line={line}&destination={destination}&operator={operator}&max_trains=20&include_formation=false&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/banenor/get_station_board?station={station}&direction=all&minutes_ahead=120&line={line}&destination={destination}&operator={operator}&max_trains=20&include_formation=false&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/banenor/get_station_board?station={station}&direction=all&minutes_ahead=120&line={line}&destination={destination}&operator={operator}&max_trains=20&include_formation=false&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "banenor",
  "operation": "get_station_board",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "..."}
}

Form for manual use

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

station (required) Type: string. Bane NOR station code, e.g. "OSL" (Oslo S), "BRG" (Bergen), "TND" (Trondheim S). Use lookup_station to find a code. Unknown codes error.

direction Type: string. "all" (default), "departures" or "arrivals".

minutes_ahead Type: integer. Window from now, in minutes (default 120).

line Type: string. Only this line, e.g. "L2", "R12", "FLY1". Exact match.

destination Type: string. Only trains whose final stop is this station NAME (e.g. "Skien", not "SKN").

operator Type: string. Only this operator code, e.g. "VY", "VYG", "FLY", "GAG", "SJN".

max_trains Type: integer. Cap on trains returned (default 20), applied upstream to the trains departing/arriving next.

include_formation Type: yes/no. Also return train formation per train where reported: wagon order and types, open/closed state, on-board services (bicycle, quiet, wheelchair, bistro, wlan, ...) and automatic passenger-count occupancy. Verbose; off by default.

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_station_board 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

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.