search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 10; lang: string, optional, default 'no'; 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/search_stops/?query={query}&limit=10&lang=no&offset=0

Replace {query}, {limit}, {lang} 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/search_stops?query={query}&limit=10&lang=no&offset=0. Open this exact request as JSON.

Parameter	Requirement	JSON type	Description
`query`	required	string	Stop name or place, e.g. "Oslo S".
`limit`	optional	integer	Maximum hits, 1-100. Unit: items.
`lang`	optional	string	Result language, normally "no" or "en".
`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/search_stops?query={query}&limit=10&lang=no&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/entur/search_stops?query={query}&limit=10&lang=no&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/search_stops?query={query}&limit=10&lang=no&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "entur",
  "operation": "search_stops",
  "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-04T02:51:51Z in 1.207 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:5294
name:
Vaslestad
label:
Vaslestad, Enebakk
category:
1 results
1. onstreetBus
municipality:
Enebakk
county:
Akershus
lat:
59.792518
lon:
11.183599
Open the place page for this point
id:
NSR:StopPlace:37020
name:
Vallestad
label:
Vallestad, Kinn
category:
1 results
1. onstreetBus
municipality:
Kinn
county:
Vestland
lat:
61.512688
lon:
4.965149
Open the place page for this point
id:
NSR:StopPlace:37412
name:
Vallestad
label:
Vallestad, Sunnfjord
category:
1 results
1. onstreetBus
municipality:
Sunnfjord
county:
Vestland
lat:
61.360992
lon:
6.224263
Open the place page for this point
id:
NSR:StopPlace:35238
name:
Vatlestad
label:
Vatlestad, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.206457
lon:
7.00381
Open the place page for this point
id:
NSR:StopPlace:17799
name:
Valmestad
label:
Valmestad, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.392635
lon:
10.115311
Open the place page for this point
id:
NSR:StopPlace:16766
name:
Valstad
label:
Valstad, Lier
category:
1 results
1. onstreetBus
municipality:
Lier
county:
Buskerud
lat:
59.89366
lon:
10.278739
Open the place page for this point
id:
NSR:StopPlace:15464
name:
Vangestad
label:
Vangestad, Flesberg
category:
1 results
1. onstreetBus
municipality:
Flesberg
county:
Buskerud
lat:
59.85215
lon:
9.49412
Open the place page for this point
id:
NSR:StopPlace:45538
name:
Valstad
label:
Valstad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.767076
lon:
11.549729
Open the place page for this point
id:
NSR:StopPlace:45578
name:
Valstad
label:
Valstad, Steinkjer
category:
1 results
1. onstreetBus
municipality:
Steinkjer
county:
Trøndelag
lat:
64.051511
lon:
11.606766
Open the place page for this point
id:
NSR:StopPlace:42044
name:
Valstad
label:
Valstad, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.156297
lon:
9.654087
Open the place page for this point
id:
NSR:StopPlace:6696
name:
Valstad
label:
Valstad, Nes
category:
1 results
1. onstreetBus
municipality:
Nes
county:
Akershus
lat:
60.244299
lon:
11.352061

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:5294
name:
Vaslestad
label:
Vaslestad, Enebakk
category:
1 results
1. onstreetBus
municipality:
Enebakk
county:
Akershus
lat:
59.792518
lon:
11.183599
Open the place page for this point
id:
NSR:StopPlace:37020
name:
Vallestad
label:
Vallestad, Kinn
category:
1 results
1. onstreetBus
municipality:
Kinn
county:
Vestland
lat:
61.512688
lon:
4.965149
Open the place page for this point
id:
NSR:StopPlace:37412
name:
Vallestad
label:
Vallestad, Sunnfjord
category:
1 results
1. onstreetBus
municipality:
Sunnfjord
county:
Vestland
lat:
61.360992
lon:
6.224263
Open the place page for this point
id:
NSR:StopPlace:35238
name:
Vatlestad
label:
Vatlestad, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.206457
lon:
7.00381
Open the place page for this point
id:
NSR:StopPlace:17799
name:
Valmestad
label:
Valmestad, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.392635
lon:
10.115311
Open the place page for this point
id:
NSR:StopPlace:16766
name:
Valstad
label:
Valstad, Lier
category:
1 results
1. onstreetBus
municipality:
Lier
county:
Buskerud
lat:
59.89366
lon:
10.278739
Open the place page for this point
id:
NSR:StopPlace:15464
name:
Vangestad
label:
Vangestad, Flesberg
category:
1 results
1. onstreetBus
municipality:
Flesberg
county:
Buskerud
lat:
59.85215
lon:
9.49412
Open the place page for this point
id:
NSR:StopPlace:45538
name:
Valstad
label:
Valstad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.767076
lon:
11.549729
Open the place page for this point
id:
NSR:StopPlace:45578
name:
Valstad
label:
Valstad, Steinkjer
category:
1 results
1. onstreetBus
municipality:
Steinkjer
county:
Trøndelag
lat:
64.051511
lon:
11.606766
Open the place page for this point
id:
NSR:StopPlace:42044
name:
Valstad
label:
Valstad, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.156297
lon:
9.654087
Open the place page for this point
id:
NSR:StopPlace:6696
name:
Valstad
label:
Valstad, Nes
category:
1 results
1. onstreetBus
municipality:
Nes
county:
Akershus
lat:
60.244299
lon:
11.352061

limit:

offset:

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