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-04T14:32:45Z in 0.579 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:8090
name:
Olestad
label:
Olestad, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
61.118142
lon:
10.672422
Open the place page for this point
id:
NSR:StopPlace:11915
name:
Olstad
label:
Olstad, Vestre Slidre
category:
1 results
1. onstreetBus
municipality:
Vestre Slidre
county:
Innlandet
lat:
61.117648
lon:
8.956383
Open the place page for this point
id:
NSR:StopPlace:12104
name:
Olstad
label:
Olstad, Øystre Slidre
category:
1 results
1. onstreetBus
municipality:
Øystre Slidre
county:
Innlandet
lat:
61.077134
lon:
9.147907
Open the place page for this point
id:
NSR:StopPlace:34136
name:
Olstad
label:
Olstad, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.19969
lon:
7.239143
Open the place page for this point
id:
NSR:StopPlace:17056
name:
Olstad
label:
Olstad, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.700162
lon:
10.229432
Open the place page for this point
id:
NSR:StopPlace:23830
name:
Olstad
label:
Olstad, Åmli
category:
1 results
1. onstreetBus
municipality:
Åmli
county:
Agder
lat:
58.805147
lon:
8.503792
Open the place page for this point
id:
NSR:StopPlace:12579
name:
Olstad
label:
Olstad, Øyer
category:
1 results
1. onstreetBus
municipality:
Øyer
county:
Innlandet
lat:
61.290982
lon:
10.392787
Open the place page for this point
id:
NSR:StopPlace:13478
name:
Olstad
label:
Olstad, Nordre Land
category:
1 results
1. onstreetBus
municipality:
Nordre Land
county:
Innlandet
lat:
60.954758
lon:
10.120063
Open the place page for this point
id:
NSR:StopPlace:13733
name:
Olstad
label:
Olstad, Gjøvik
category:
1 results
1. onstreetBus
municipality:
Gjøvik
county:
Innlandet
lat:
60.861384
lon:
10.645674
Open the place page for this point
id:
NSR:StopPlace:20899
name:
Olesrud
label:
Olesrud, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
60.119127
lon:
8.715417
Open the place page for this point
id:
NSR:StopPlace:18771
name:
Olumstad
label:
Olumstad, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.454309
lon:
10.286049

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:8090
name:
Olestad
label:
Olestad, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
61.118142
lon:
10.672422
Open the place page for this point
id:
NSR:StopPlace:11915
name:
Olstad
label:
Olstad, Vestre Slidre
category:
1 results
1. onstreetBus
municipality:
Vestre Slidre
county:
Innlandet
lat:
61.117648
lon:
8.956383
Open the place page for this point
id:
NSR:StopPlace:12104
name:
Olstad
label:
Olstad, Øystre Slidre
category:
1 results
1. onstreetBus
municipality:
Øystre Slidre
county:
Innlandet
lat:
61.077134
lon:
9.147907
Open the place page for this point
id:
NSR:StopPlace:34136
name:
Olstad
label:
Olstad, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.19969
lon:
7.239143
Open the place page for this point
id:
NSR:StopPlace:17056
name:
Olstad
label:
Olstad, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.700162
lon:
10.229432
Open the place page for this point
id:
NSR:StopPlace:23830
name:
Olstad
label:
Olstad, Åmli
category:
1 results
1. onstreetBus
municipality:
Åmli
county:
Agder
lat:
58.805147
lon:
8.503792
Open the place page for this point
id:
NSR:StopPlace:12579
name:
Olstad
label:
Olstad, Øyer
category:
1 results
1. onstreetBus
municipality:
Øyer
county:
Innlandet
lat:
61.290982
lon:
10.392787
Open the place page for this point
id:
NSR:StopPlace:13478
name:
Olstad
label:
Olstad, Nordre Land
category:
1 results
1. onstreetBus
municipality:
Nordre Land
county:
Innlandet
lat:
60.954758
lon:
10.120063
Open the place page for this point
id:
NSR:StopPlace:13733
name:
Olstad
label:
Olstad, Gjøvik
category:
1 results
1. onstreetBus
municipality:
Gjøvik
county:
Innlandet
lat:
60.861384
lon:
10.645674
Open the place page for this point
id:
NSR:StopPlace:20899
name:
Olesrud
label:
Olesrud, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
60.119127
lon:
8.715417
Open the place page for this point
id:
NSR:StopPlace:18771
name:
Olumstad
label:
Olumstad, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.454309
lon:
10.286049

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.