search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
`lang`	optional	string	Result language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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-11-13T15:48:33Z in 0.141 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:57942
name:
Gundershogget stasjon
label:
Gundershogget stasjon, Bærum
category:
1 results
1. railStation
municipality:
Bærum
county:
Akershus
lat:
59.981792
lon:
10.484025
Open the place page for this point
id:
NSR:StopPlace:64515
name:
Arlanda terminal 2-3
label:
Arlanda terminal 2-3, Sigtuna
category:
1 results
1. onstreetBus
municipality:
Sigtuna
county:
Stockholms län
lat:
59.644478
lon:
17.928942
Open the place page for this point
id:
NSR:StopPlace:51662
name:
Jamtli Stopp 2
label:
Jamtli Stopp 2, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.335458
lon:
14.294112
Open the place page for this point
id:
NSR:StopPlace:47810
name:
Rynesåsen Stopp 2
label:
Rynesåsen Stopp 2, Vefsn
category:
1 results
1. onstreetBus
municipality:
Vefsn
county:
Nordland
lat:
65.875288
lon:
13.180752
Open the place page for this point
id:
NSR:StopPlace:43373
name:
Storsand 2
label:
Storsand 2, Malvik
category:
1 results
1. onstreetBus
municipality:
Malvik
county:
Trøndelag
lat:
63.431285
lon:
10.707545
Open the place page for this point
id:
NSR:StopPlace:16996
name:
2. Strøm terrasse 5
label:
2. Strøm terrasse 5, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.737007
lon:
10.188476
Open the place page for this point
id:
NSR:StopPlace:17001
name:
2. Strøm terrasse 23
label:
2. Strøm terrasse 23, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.73413
lon:
10.191253
Open the place page for this point
id:
NSR:StopPlace:39736
name:
Stavdal 2
label:
Stavdal 2, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.375748
lon:
7.129148
Open the place page for this point
id:
NSR:StopPlace:18652
name:
Strand 2
label:
Strand 2, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.118033
lon:
9.907737
Open the place page for this point
id:
NSR:StopPlace:58995
name:
Steinsleppen 2
label:
Steinsleppen 2, Nordre Follo
category:
1 results
1. onstreetBus
municipality:
Nordre Follo
county:
Akershus
lat:
59.738812
lon:
10.827252
Open the place page for this point
id:
NSR:StopPlace:59599
name:
Stakkestadvegen 2
label:
Stakkestadvegen 2, Tysvær
category:
1 results
1. onstreetBus
municipality:
Tysvær
county:
Rogaland
lat:
59.424951
lon:
5.382311
Open the place page for this point
id:
NSR:StopPlace:64629
name:
Steintrøvegen 2
label:
Steintrøvegen 2, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.40098
lon:
10.4521

Show all fields in HTML

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:57942
name:
Gundershogget stasjon
label:
Gundershogget stasjon, Bærum
category:
1 results
1. railStation
municipality:
Bærum
county:
Akershus
lat:
59.981792
lon:
10.484025
Open the place page for this point
id:
NSR:StopPlace:64515
name:
Arlanda terminal 2-3
label:
Arlanda terminal 2-3, Sigtuna
category:
1 results
1. onstreetBus
municipality:
Sigtuna
county:
Stockholms län
lat:
59.644478
lon:
17.928942
Open the place page for this point
id:
NSR:StopPlace:51662
name:
Jamtli Stopp 2
label:
Jamtli Stopp 2, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.335458
lon:
14.294112
Open the place page for this point
id:
NSR:StopPlace:47810
name:
Rynesåsen Stopp 2
label:
Rynesåsen Stopp 2, Vefsn
category:
1 results
1. onstreetBus
municipality:
Vefsn
county:
Nordland
lat:
65.875288
lon:
13.180752
Open the place page for this point
id:
NSR:StopPlace:43373
name:
Storsand 2
label:
Storsand 2, Malvik
category:
1 results
1. onstreetBus
municipality:
Malvik
county:
Trøndelag
lat:
63.431285
lon:
10.707545
Open the place page for this point
id:
NSR:StopPlace:16996
name:
2. Strøm terrasse 5
label:
2. Strøm terrasse 5, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.737007
lon:
10.188476
Open the place page for this point
id:
NSR:StopPlace:17001
name:
2. Strøm terrasse 23
label:
2. Strøm terrasse 23, Drammen
category:
1 results
1. onstreetBus
municipality:
Drammen
county:
Buskerud
lat:
59.73413
lon:
10.191253
Open the place page for this point
id:
NSR:StopPlace:39736
name:
Stavdal 2
label:
Stavdal 2, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.375748
lon:
7.129148
Open the place page for this point
id:
NSR:StopPlace:18652
name:
Strand 2
label:
Strand 2, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.118033
lon:
9.907737
Open the place page for this point
id:
NSR:StopPlace:58995
name:
Steinsleppen 2
label:
Steinsleppen 2, Nordre Follo
category:
1 results
1. onstreetBus
municipality:
Nordre Follo
county:
Akershus
lat:
59.738812
lon:
10.827252
Open the place page for this point
id:
NSR:StopPlace:59599
name:
Stakkestadvegen 2
label:
Stakkestadvegen 2, Tysvær
category:
1 results
1. onstreetBus
municipality:
Tysvær
county:
Rogaland
lat:
59.424951
lon:
5.382311
Open the place page for this point
id:
NSR:StopPlace:64629
name:
Steintrøvegen 2
label:
Steintrøvegen 2, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.40098
lon:
10.4521

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.