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-01T06:16:54Z in 0.239 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:64461
name:
Rotemo
label:
Rotemo, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
59.906127
lon:
8.712455
Open the place page for this point
id:
NSR:StopPlace:21906
name:
Rotemo
label:
Rotemo, Valle
category:
1 results
1. onstreetBus
municipality:
Valle
county:
Agder
lat:
59.239723
lon:
7.479263
Open the place page for this point
id:
NSR:StopPlace:52056
name:
Rognmo
label:
Rognmo, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.121764
lon:
19.11092
Open the place page for this point
id:
NSR:StopPlace:41810
name:
Rottem
label:
Rottem, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.465136
lon:
9.198979
Open the place page for this point
id:
NSR:StopPlace:45481
name:
Rotmoen
label:
Rotmoen, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.72012
lon:
11.83882
Open the place page for this point
id:
NSR:StopPlace:52059
name:
Rognmo
label:
Rognmo, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.619439
lon:
21.294415
Open the place page for this point
id:
NSR:StopPlace:49936
name:
Rognmo
label:
Rognmo, Narvik
category:
1 results
1. onstreetBus
municipality:
Narvik
county:
Nordland
lat:
68.410436
lon:
16.652595
Open the place page for this point
id:
NSR:StopPlace:44849
name:
Roten
label:
Roten, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.59395
lon:
10.207264
Open the place page for this point
id:
NSR:StopPlace:44264
name:
Rødmo
label:
Rødmo, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.134083
lon:
14.088214
Open the place page for this point
id:
NSR:StopPlace:37772
name:
Røtet
label:
Røtet, Surnadal
category:
1 results
1. onstreetBus
municipality:
Surnadal
county:
Møre og Romsdal
lat:
62.983624
lon:
8.656851
Open the place page for this point
id:
NSR:StopPlace:44911
name:
Rømo
label:
Rømo, Stjørdal
category:
1 results
1. onstreetBus
municipality:
Stjørdal
county:
Trøndelag
lat:
63.513174
lon:
11.084553
Open the place page for this point
id:
NSR:StopPlace:8772
name:
Rotnemoen
label:
Rotnemoen, Torsby
category:
1 results
1. onstreetBus
municipality:
Torsby
county:
Värmlands län
lat:
60.280989
lon:
12.504544

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:64461
name:
Rotemo
label:
Rotemo, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
59.906127
lon:
8.712455
Open the place page for this point
id:
NSR:StopPlace:21906
name:
Rotemo
label:
Rotemo, Valle
category:
1 results
1. onstreetBus
municipality:
Valle
county:
Agder
lat:
59.239723
lon:
7.479263
Open the place page for this point
id:
NSR:StopPlace:52056
name:
Rognmo
label:
Rognmo, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.121764
lon:
19.11092
Open the place page for this point
id:
NSR:StopPlace:41810
name:
Rottem
label:
Rottem, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.465136
lon:
9.198979
Open the place page for this point
id:
NSR:StopPlace:45481
name:
Rotmoen
label:
Rotmoen, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.72012
lon:
11.83882
Open the place page for this point
id:
NSR:StopPlace:52059
name:
Rognmo
label:
Rognmo, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.619439
lon:
21.294415
Open the place page for this point
id:
NSR:StopPlace:49936
name:
Rognmo
label:
Rognmo, Narvik
category:
1 results
1. onstreetBus
municipality:
Narvik
county:
Nordland
lat:
68.410436
lon:
16.652595
Open the place page for this point
id:
NSR:StopPlace:44849
name:
Roten
label:
Roten, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.59395
lon:
10.207264
Open the place page for this point
id:
NSR:StopPlace:44264
name:
Rødmo
label:
Rødmo, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.134083
lon:
14.088214
Open the place page for this point
id:
NSR:StopPlace:37772
name:
Røtet
label:
Røtet, Surnadal
category:
1 results
1. onstreetBus
municipality:
Surnadal
county:
Møre og Romsdal
lat:
62.983624
lon:
8.656851
Open the place page for this point
id:
NSR:StopPlace:44911
name:
Rømo
label:
Rømo, Stjørdal
category:
1 results
1. onstreetBus
municipality:
Stjørdal
county:
Trøndelag
lat:
63.513174
lon:
11.084553
Open the place page for this point
id:
NSR:StopPlace:8772
name:
Rotnemoen
label:
Rotnemoen, Torsby
category:
1 results
1. onstreetBus
municipality:
Torsby
county:
Värmlands län
lat:
60.280989
lon:
12.504544

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.