search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; 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=25&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=25&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. Through this API: default 25, maximum 100.
`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=25&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=25&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=25&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-11-03T04:21:58Z in 0.140 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:27104
name:
Solåsveien
label:
Solåsveien, Gjesdal
category:
1 results
1. onstreetBus
municipality:
Gjesdal
county:
Rogaland
lat:
58.76733
lon:
5.863899
Open the place page for this point
id:
NSR:StopPlace:53960
name:
Solåsveien
label:
Solåsveien, Bardu
category:
1 results
1. onstreetBus
municipality:
Bardu
county:
Troms
lat:
68.860501
lon:
18.339067
Open the place page for this point
id:
NSR:StopPlace:27097
name:
Solåsvegen
label:
Solåsvegen, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.154413
lon:
5.265512
Open the place page for this point
id:
NSR:StopPlace:27057
name:
Solavegen
label:
Solavegen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.776336
lon:
5.630729
Open the place page for this point
id:
NSR:StopPlace:4653
name:
Solliveien
label:
Solliveien, Nittedal
category:
1 results
1. onstreetBus
municipality:
Nittedal
county:
Akershus
lat:
60.05216
lon:
10.874739
Open the place page for this point
id:
NSR:StopPlace:2780
name:
Soldatveien
label:
Soldatveien, Halden
category:
1 results
1. onstreetBus
municipality:
Halden
county:
Østfold
lat:
59.104183
lon:
11.403229
Open the place page for this point
id:
NSR:StopPlace:48490
name:
Solliveien
label:
Solliveien, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.294635
lon:
14.431304
Open the place page for this point
id:
NSR:StopPlace:18498
name:
Solliveien
label:
Solliveien, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.016655
lon:
10.018528
Open the place page for this point
id:
NSR:StopPlace:3589
name:
Solliveien
label:
Solliveien, Bærum
category:
1 results
1. onstreetBus
municipality:
Bærum
county:
Akershus
lat:
59.913836
lon:
10.632783
Open the place page for this point
id:
NSR:StopPlace:23321
name:
Solliveien
label:
Solliveien, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.121882
lon:
7.947185
Open the place page for this point
id:
NSR:StopPlace:27118
name:
Somaveien
label:
Somaveien, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.863572
lon:
5.699616
Open the place page for this point
id:
NSR:StopPlace:18517
name:
Solveien
label:
Solveien, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.256813
lon:
10.409047

Show all fields in HTML

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:27104
name:
Solåsveien
label:
Solåsveien, Gjesdal
category:
1 results
1. onstreetBus
municipality:
Gjesdal
county:
Rogaland
lat:
58.76733
lon:
5.863899
Open the place page for this point
id:
NSR:StopPlace:53960
name:
Solåsveien
label:
Solåsveien, Bardu
category:
1 results
1. onstreetBus
municipality:
Bardu
county:
Troms
lat:
68.860501
lon:
18.339067
Open the place page for this point
id:
NSR:StopPlace:27097
name:
Solåsvegen
label:
Solåsvegen, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.154413
lon:
5.265512
Open the place page for this point
id:
NSR:StopPlace:27057
name:
Solavegen
label:
Solavegen, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.776336
lon:
5.630729
Open the place page for this point
id:
NSR:StopPlace:4653
name:
Solliveien
label:
Solliveien, Nittedal
category:
1 results
1. onstreetBus
municipality:
Nittedal
county:
Akershus
lat:
60.05216
lon:
10.874739
Open the place page for this point
id:
NSR:StopPlace:2780
name:
Soldatveien
label:
Soldatveien, Halden
category:
1 results
1. onstreetBus
municipality:
Halden
county:
Østfold
lat:
59.104183
lon:
11.403229
Open the place page for this point
id:
NSR:StopPlace:48490
name:
Solliveien
label:
Solliveien, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.294635
lon:
14.431304
Open the place page for this point
id:
NSR:StopPlace:18498
name:
Solliveien
label:
Solliveien, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.016655
lon:
10.018528
Open the place page for this point
id:
NSR:StopPlace:3589
name:
Solliveien
label:
Solliveien, Bærum
category:
1 results
1. onstreetBus
municipality:
Bærum
county:
Akershus
lat:
59.913836
lon:
10.632783
Open the place page for this point
id:
NSR:StopPlace:23321
name:
Solliveien
label:
Solliveien, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.121882
lon:
7.947185
Open the place page for this point
id:
NSR:StopPlace:27118
name:
Somaveien
label:
Somaveien, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.863572
lon:
5.699616
Open the place page for this point
id:
NSR:StopPlace:18517
name:
Solveien
label:
Solveien, Tønsberg
category:
1 results
1. onstreetBus
municipality:
Tønsberg
county:
Vestfold
lat:
59.256813
lon:
10.409047

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.