get_disruptions

Cancellations and disruptions of individual train journeys, from Bane NOR's situation exchange feed.

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_disruptions/?hours_ahead=24&station={station}&train_number={train_number}&max_results=50&offset=0&limit=25

Replace {hours_ahead}, {station}, {train_number}, {max_results}, {offset} 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_disruptions?hours_ahead=24&station={station}&train_number={train_number}&max_results=50&offset=0&limit=25.

Parameter	Requirement	JSON type	Description
`hours_ahead`	optional	integer	Only situations starting within this many hours from now (default 24). The full feed carries ~a week of planned changes (thousands of records); keep this small unless you really want them all.
`station`	optional	union	Only situations touching this station code (e.g. "OSL").
`train_number`	optional	union	Only situations for this train number.
`max_results`	optional	integer	Page size (default 50). `total_count` is the number matching before paging.
`offset`	optional	integer	Skip this many matching situations (default 0). When the response is truncated it carries `next_offset`; pass that back as offset for the next page. Prefer narrowing with station, train_number or hours_ahead over paging through the national feed.
`limit`	optional	integer	Gateway page size; default 25, maximum 100.

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_disruptions?hours_ahead=24&station={station}&train_number={train_number}&max_results=50&offset=0&limit=25

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/banenor/get_disruptions?hours_ahead=24&station={station}&train_number={train_number}&max_results=50&offset=0&limit=25";
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_disruptions?hours_ahead=24&station={station}&train_number={train_number}&max_results=50&offset=0&limit=25"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "banenor",
  "operation": "get_disruptions",
  "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.

hours_ahead Type: integer. Only situations starting within this many hours from now (default 24). The full feed carries ~a week of planned changes (thousands of records); keep this small unless you really want them all.

station Type: string. Only situations touching this station code (e.g. "OSL").

train_number Type: string. Only situations for this train number.

max_results Type: integer. Page size (default 50). `total_count` is the number matching before paging.

offset Type: integer. Skip this many matching situations (default 0). When the response is truncated it carries `next_offset`; pass that back as offset for the next page. Prefer narrowing with station, train_number or hours_ahead over paging through the national feed.

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