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-02T22:05:44Z in 0.263 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:63482
name:
Røllend
label:
Røllend, Iveland
category:
1 results
1. onstreetBus
municipality:
Iveland
county:
Agder
lat:
58.417755
lon:
7.915666
Open the place page for this point
id:
NSR:StopPlace:28851
name:
Rolland
label:
Rolland, Osterøy
category:
1 results
1. onstreetBus
municipality:
Osterøy
county:
Vestland
lat:
60.4728
lon:
5.528577
Open the place page for this point
id:
NSR:StopPlace:33300
name:
Rødland
label:
Rødland, Alver
category:
1 results
1. onstreetBus
municipality:
Alver
county:
Vestland
lat:
60.68806
lon:
5.392469
Open the place page for this point
id:
NSR:StopPlace:60317
name:
Rosland
label:
Rosland, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.733218
lon:
5.599235
Open the place page for this point
id:
NSR:StopPlace:49484
name:
Røkland
label:
Røkland, Saltdal
category:
1 results
1. onstreetBus
municipality:
Saltdal
county:
Nordland
lat:
66.986466
lon:
15.318365
Open the place page for this point
id:
NSR:StopPlace:11537
name:
Røllång
label:
Røllång, Nord-Aurdal
category:
1 results
1. onstreetBus
municipality:
Nord-Aurdal
county:
Innlandet
lat:
61.011425
lon:
9.099641
Open the place page for this point
id:
NSR:StopPlace:25926
name:
Rødland
label:
Rødland, Eigersund
category:
1 results
1. onstreetBus
municipality:
Eigersund
county:
Rogaland
lat:
58.500459
lon:
6.238563
Open the place page for this point
id:
NSR:StopPlace:22008
name:
Rødland
label:
Rødland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.238973
lon:
7.317201
Open the place page for this point
id:
NSR:StopPlace:22009
name:
Rødland
label:
Rødland, Kvinesdal
category:
1 results
1. onstreetBus
municipality:
Kvinesdal
county:
Agder
lat:
58.31242
lon:
6.973435
Open the place page for this point
id:
NSR:StopPlace:28860
name:
Rødland
label:
Rødland, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.405821
lon:
5.449577
Open the place page for this point
id:
NSR:StopPlace:14778
name:
Roland
label:
Roland, Vestre Toten
category:
1 results
1. onstreetBus
municipality:
Vestre Toten
county:
Innlandet
lat:
60.708832
lon:
10.745633
Open the place page for this point
id:
NSR:StopPlace:21845
name:
Roland
label:
Roland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.096627
lon:
7.313492

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:63482
name:
Røllend
label:
Røllend, Iveland
category:
1 results
1. onstreetBus
municipality:
Iveland
county:
Agder
lat:
58.417755
lon:
7.915666
Open the place page for this point
id:
NSR:StopPlace:28851
name:
Rolland
label:
Rolland, Osterøy
category:
1 results
1. onstreetBus
municipality:
Osterøy
county:
Vestland
lat:
60.4728
lon:
5.528577
Open the place page for this point
id:
NSR:StopPlace:33300
name:
Rødland
label:
Rødland, Alver
category:
1 results
1. onstreetBus
municipality:
Alver
county:
Vestland
lat:
60.68806
lon:
5.392469
Open the place page for this point
id:
NSR:StopPlace:60317
name:
Rosland
label:
Rosland, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.733218
lon:
5.599235
Open the place page for this point
id:
NSR:StopPlace:49484
name:
Røkland
label:
Røkland, Saltdal
category:
1 results
1. onstreetBus
municipality:
Saltdal
county:
Nordland
lat:
66.986466
lon:
15.318365
Open the place page for this point
id:
NSR:StopPlace:11537
name:
Røllång
label:
Røllång, Nord-Aurdal
category:
1 results
1. onstreetBus
municipality:
Nord-Aurdal
county:
Innlandet
lat:
61.011425
lon:
9.099641
Open the place page for this point
id:
NSR:StopPlace:25926
name:
Rødland
label:
Rødland, Eigersund
category:
1 results
1. onstreetBus
municipality:
Eigersund
county:
Rogaland
lat:
58.500459
lon:
6.238563
Open the place page for this point
id:
NSR:StopPlace:22008
name:
Rødland
label:
Rødland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.238973
lon:
7.317201
Open the place page for this point
id:
NSR:StopPlace:22009
name:
Rødland
label:
Rødland, Kvinesdal
category:
1 results
1. onstreetBus
municipality:
Kvinesdal
county:
Agder
lat:
58.31242
lon:
6.973435
Open the place page for this point
id:
NSR:StopPlace:28860
name:
Rødland
label:
Rødland, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.405821
lon:
5.449577
Open the place page for this point
id:
NSR:StopPlace:14778
name:
Roland
label:
Roland, Vestre Toten
category:
1 results
1. onstreetBus
municipality:
Vestre Toten
county:
Innlandet
lat:
60.708832
lon:
10.745633
Open the place page for this point
id:
NSR:StopPlace:21845
name:
Roland
label:
Roland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.096627
lon:
7.313492

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.