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-29T11:37:45Z in 0.147 seconds.

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:31476
name:
Geitle
label:
Geitle, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.638316
lon:
6.199443
Open the place page for this point
id:
NSR:StopPlace:11549
name:
Geitlegeret
label:
Geitlegeret, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.88092
lon:
9.416517
Open the place page for this point
id:
NSR:StopPlace:31710
name:
Geilen
label:
Geilen, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.254597
lon:
5.262848
Open the place page for this point
id:
NSR:StopPlace:25517
name:
Glitre
label:
Glitre, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.168678
lon:
7.946822
Open the place page for this point
id:
NSR:StopPlace:64217
name:
Geilen
label:
Geilen, Rauma
category:
1 results
1. onstreetBus
municipality:
Rauma
county:
Møre og Romsdal
lat:
62.499138
lon:
7.543198
Open the place page for this point
id:
NSR:StopPlace:60585
name:
Geita
label:
Geita, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.429796
lon:
9.965141
Open the place page for this point
id:
NSR:StopPlace:19266
name:
Gihle
label:
Gihle, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.240936
lon:
10.344634
Open the place page for this point
id:
NSR:StopPlace:3020
name:
Gimle
label:
Gimle, Moss
category:
1 results
1. onstreetBus
municipality:
Moss
county:
Østfold
lat:
59.433399
lon:
10.642884
Open the place page for this point
id:
NSR:StopPlace:16990
name:
Gihle
label:
Gihle, Ringerike
category:
1 results
1. onstreetBus
municipality:
Ringerike
county:
Buskerud
lat:
60.12425
lon:
10.28
Open the place page for this point
id:
NSR:StopPlace:48147
name:
Gimle
label:
Gimle, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.126376
lon:
13.85014
Open the place page for this point
id:
NSR:StopPlace:55895
name:
Gimle
label:
Gimle, Tromsø
category:
1 results
1. onstreetBus
municipality:
Tromsø
county:
Troms
lat:
69.682844
lon:
18.996788
Open the place page for this point
id:
NSR:StopPlace:13572
name:
Gimle
label:
Gimle, Østre Toten
category:
1 results
1. onstreetBus
municipality:
Østre Toten
county:
Innlandet
lat:
60.644995
lon:
10.888833
Open the place page for this point
id:
NSR:StopPlace:10791
name:
Gile
label:
Gile, Hamar
category:
1 results
1. onstreetBus
municipality:
Hamar
county:
Innlandet
lat:
60.796963
lon:
11.202828

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:31476
name:
Geitle
label:
Geitle, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.638316
lon:
6.199443
Open the place page for this point
id:
NSR:StopPlace:11549
name:
Geitlegeret
label:
Geitlegeret, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.88092
lon:
9.416517
Open the place page for this point
id:
NSR:StopPlace:31710
name:
Geilen
label:
Geilen, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.254597
lon:
5.262848
Open the place page for this point
id:
NSR:StopPlace:25517
name:
Glitre
label:
Glitre, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.168678
lon:
7.946822
Open the place page for this point
id:
NSR:StopPlace:64217
name:
Geilen
label:
Geilen, Rauma
category:
1 results
1. onstreetBus
municipality:
Rauma
county:
Møre og Romsdal
lat:
62.499138
lon:
7.543198
Open the place page for this point
id:
NSR:StopPlace:60585
name:
Geita
label:
Geita, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.429796
lon:
9.965141
Open the place page for this point
id:
NSR:StopPlace:19266
name:
Gihle
label:
Gihle, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.240936
lon:
10.344634
Open the place page for this point
id:
NSR:StopPlace:3020
name:
Gimle
label:
Gimle, Moss
category:
1 results
1. onstreetBus
municipality:
Moss
county:
Østfold
lat:
59.433399
lon:
10.642884
Open the place page for this point
id:
NSR:StopPlace:16990
name:
Gihle
label:
Gihle, Ringerike
category:
1 results
1. onstreetBus
municipality:
Ringerike
county:
Buskerud
lat:
60.12425
lon:
10.28
Open the place page for this point
id:
NSR:StopPlace:48147
name:
Gimle
label:
Gimle, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.126376
lon:
13.85014
Open the place page for this point
id:
NSR:StopPlace:55895
name:
Gimle
label:
Gimle, Tromsø
category:
1 results
1. onstreetBus
municipality:
Tromsø
county:
Troms
lat:
69.682844
lon:
18.996788
Open the place page for this point
id:
NSR:StopPlace:13572
name:
Gimle
label:
Gimle, Østre Toten
category:
1 results
1. onstreetBus
municipality:
Østre Toten
county:
Innlandet
lat:
60.644995
lon:
10.888833
Open the place page for this point
id:
NSR:StopPlace:10791
name:
Gile
label:
Gile, Hamar
category:
1 results
1. onstreetBus
municipality:
Hamar
county:
Innlandet
lat:
60.796963
lon:
11.202828

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.