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-09-29T12:10:35Z in 0.146 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:26297
name:
Storevollen
label:
Storevollen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.824287
lon:
5.623491
Open the place page for this point
id:
NSR:StopPlace:43386
name:
Storvollen
label:
Storvollen, Osen
category:
1 results
1. onstreetBus
municipality:
Osen
county:
Trøndelag
lat:
64.271753
lon:
10.608982
Open the place page for this point
id:
NSR:StopPlace:54561
name:
Storvollen
label:
Storvollen, Karlsøy
category:
1 results
1. onstreetBus
municipality:
Karlsøy
county:
Troms
lat:
69.999942
lon:
19.831947
Open the place page for this point
id:
NSR:StopPlace:54563
name:
Storvollen
label:
Storvollen, Lyngen
category:
1 results
1. onstreetBus
municipality:
Lyngen
county:
Troms
lat:
69.890152
lon:
20.163908
Open the place page for this point
id:
NSR:StopPlace:48435
name:
Storvolleng
label:
Storvolleng, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.322166
lon:
14.834148
Open the place page for this point
id:
NSR:StopPlace:54557
name:
Storvollen
label:
Storvollen, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.993932
lon:
16.533155
Open the place page for this point
id:
NSR:StopPlace:43388
name:
Storvollen
label:
Storvollen, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.254939
lon:
10.440469
Open the place page for this point
id:
NSR:StopPlace:49843
name:
Storvollen
label:
Storvollen, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.315235
lon:
14.455766
Open the place page for this point
id:
NSR:StopPlace:50527
name:
Storvollen
label:
Storvollen, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.50429
lon:
14.915603
Open the place page for this point
id:
NSR:StopPlace:27372
name:
Storeholen
label:
Storeholen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.746017
lon:
5.593854
Open the place page for this point
id:
NSR:StopPlace:27368
name:
Storeholen
label:
Storeholen, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.781375
lon:
5.82541

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:26297
name:
Storevollen
label:
Storevollen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.824287
lon:
5.623491
Open the place page for this point
id:
NSR:StopPlace:43386
name:
Storvollen
label:
Storvollen, Osen
category:
1 results
1. onstreetBus
municipality:
Osen
county:
Trøndelag
lat:
64.271753
lon:
10.608982
Open the place page for this point
id:
NSR:StopPlace:54561
name:
Storvollen
label:
Storvollen, Karlsøy
category:
1 results
1. onstreetBus
municipality:
Karlsøy
county:
Troms
lat:
69.999942
lon:
19.831947
Open the place page for this point
id:
NSR:StopPlace:54563
name:
Storvollen
label:
Storvollen, Lyngen
category:
1 results
1. onstreetBus
municipality:
Lyngen
county:
Troms
lat:
69.890152
lon:
20.163908
Open the place page for this point
id:
NSR:StopPlace:48435
name:
Storvolleng
label:
Storvolleng, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.322166
lon:
14.834148
Open the place page for this point
id:
NSR:StopPlace:54557
name:
Storvollen
label:
Storvollen, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.993932
lon:
16.533155
Open the place page for this point
id:
NSR:StopPlace:43388
name:
Storvollen
label:
Storvollen, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.254939
lon:
10.440469
Open the place page for this point
id:
NSR:StopPlace:49843
name:
Storvollen
label:
Storvollen, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.315235
lon:
14.455766
Open the place page for this point
id:
NSR:StopPlace:50527
name:
Storvollen
label:
Storvollen, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.50429
lon:
14.915603
Open the place page for this point
id:
NSR:StopPlace:27372
name:
Storeholen
label:
Storeholen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.746017
lon:
5.593854
Open the place page for this point
id:
NSR:StopPlace:27368
name:
Storeholen
label:
Storeholen, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.781375
lon:
5.82541

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.