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-01T22:03:40Z in 0.127 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:28892
name:
Ulset
label:
Ulset, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.473378
lon:
5.323219
Open the place page for this point
id:
NSR:StopPlace:39599
name:
Ulset
label:
Ulset, Hareid
category:
1 results
1. onstreetBus
municipality:
Hareid
county:
Møre og Romsdal
lat:
62.32738
lon:
6.016034
Open the place page for this point
id:
NSR:StopPlace:39594
name:
Ulset
label:
Ulset, Tingvoll
category:
1 results
1. onstreetBus
municipality:
Tingvoll
county:
Møre og Romsdal
lat:
63.032273
lon:
8.030717
Open the place page for this point
id:
NSR:StopPlace:61918
name:
Ulset
label:
Ulset, Tynset
category:
1 results
1. onstreetBus
municipality:
Tynset
county:
Innlandet
lat:
62.616664
lon:
10.254831
Open the place page for this point
id:
NSR:StopPlace:62537
name:
Ulset
label:
Ulset, Hareid
category:
1 results
1. onstreetBus
municipality:
Hareid
county:
Møre og Romsdal
lat:
62.323221
lon:
6.003696
Open the place page for this point
id:
NSR:StopPlace:41948
name:
Ulseth
label:
Ulseth, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.326393
lon:
10.482264
Open the place page for this point
id:
NSR:StopPlace:31109
name:
Ulsetåsen
label:
Ulsetåsen, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.46293
lon:
5.308513
Open the place page for this point
id:
NSR:StopPlace:7508
name:
Ulsetlykkja
label:
Ulsetlykkja, Tynset
category:
1 results
1. onstreetBus
municipality:
Tynset
county:
Innlandet
lat:
62.612428
lon:
10.257327
Open the place page for this point
id:
NSR:StopPlace:28899
name:
Ulsetstemma
label:
Ulsetstemma, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.479377
lon:
5.311647
Open the place page for this point
id:
NSR:StopPlace:41980
name:
Utset
label:
Utset, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.579797
lon:
9.13257
Open the place page for this point
id:
NSR:StopPlace:8642
name:
Unset
label:
Unset, Rendalen
category:
1 results
1. onstreetBus
municipality:
Rendalen
county:
Innlandet
lat:
61.96677
lon:
11.103214
Open the place page for this point
id:
NSR:StopPlace:46581
name:
Ugset
label:
Ugset, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.619134
lon:
11.374079

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:28892
name:
Ulset
label:
Ulset, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.473378
lon:
5.323219
Open the place page for this point
id:
NSR:StopPlace:39599
name:
Ulset
label:
Ulset, Hareid
category:
1 results
1. onstreetBus
municipality:
Hareid
county:
Møre og Romsdal
lat:
62.32738
lon:
6.016034
Open the place page for this point
id:
NSR:StopPlace:39594
name:
Ulset
label:
Ulset, Tingvoll
category:
1 results
1. onstreetBus
municipality:
Tingvoll
county:
Møre og Romsdal
lat:
63.032273
lon:
8.030717
Open the place page for this point
id:
NSR:StopPlace:61918
name:
Ulset
label:
Ulset, Tynset
category:
1 results
1. onstreetBus
municipality:
Tynset
county:
Innlandet
lat:
62.616664
lon:
10.254831
Open the place page for this point
id:
NSR:StopPlace:62537
name:
Ulset
label:
Ulset, Hareid
category:
1 results
1. onstreetBus
municipality:
Hareid
county:
Møre og Romsdal
lat:
62.323221
lon:
6.003696
Open the place page for this point
id:
NSR:StopPlace:41948
name:
Ulseth
label:
Ulseth, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.326393
lon:
10.482264
Open the place page for this point
id:
NSR:StopPlace:31109
name:
Ulsetåsen
label:
Ulsetåsen, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.46293
lon:
5.308513
Open the place page for this point
id:
NSR:StopPlace:7508
name:
Ulsetlykkja
label:
Ulsetlykkja, Tynset
category:
1 results
1. onstreetBus
municipality:
Tynset
county:
Innlandet
lat:
62.612428
lon:
10.257327
Open the place page for this point
id:
NSR:StopPlace:28899
name:
Ulsetstemma
label:
Ulsetstemma, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.479377
lon:
5.311647
Open the place page for this point
id:
NSR:StopPlace:41980
name:
Utset
label:
Utset, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.579797
lon:
9.13257
Open the place page for this point
id:
NSR:StopPlace:8642
name:
Unset
label:
Unset, Rendalen
category:
1 results
1. onstreetBus
municipality:
Rendalen
county:
Innlandet
lat:
61.96677
lon:
11.103214
Open the place page for this point
id:
NSR:StopPlace:46581
name:
Ugset
label:
Ugset, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.619134
lon:
11.374079

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.