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-03T18:07:06Z in 0.731 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:24371
name:
Kvastad
label:
Kvastad, Tvedestrand
category:
1 results
1. onstreetBus
municipality:
Tvedestrand
county:
Agder
lat:
58.569203
lon:
8.892274
Open the place page for this point
id:
NSR:StopPlace:24365
name:
Kvastad nord
label:
Kvastad nord, Tvedestrand
category:
1 results
1. onstreetBus
municipality:
Tvedestrand
county:
Agder
lat:
58.572556
lon:
8.888572
Open the place page for this point
id:
NSR:StopPlace:27887
name:
Kvæstad
label:
Kvæstad, Suldal
category:
1 results
1. onstreetBus
municipality:
Suldal
county:
Rogaland
lat:
59.455908
lon:
6.384165
Open the place page for this point
id:
NSR:StopPlace:36735
name:
Kvalstad
label:
Kvalstad, Kinn
category:
1 results
1. onstreetBus
municipality:
Kinn
county:
Vestland
lat:
61.479277
lon:
5.089687
Open the place page for this point
id:
NSR:StopPlace:40302
name:
Kvistad
label:
Kvistad, Ørsta
category:
1 results
1. onstreetBus
municipality:
Ørsta
county:
Møre og Romsdal
lat:
62.194704
lon:
6.417224
Open the place page for this point
id:
NSR:StopPlace:20578
name:
Kvestad
label:
Kvestad, Porsgrunn
category:
1 results
1. onstreetBus
municipality:
Porsgrunn
county:
Telemark
lat:
59.13701
lon:
9.72987
Open the place page for this point
id:
NSR:StopPlace:45429
name:
Kvistad
label:
Kvistad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.814772
lon:
11.465001
Open the place page for this point
id:
NSR:StopPlace:50175
name:
Kvikstad
label:
Kvikstad, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.230706
lon:
14.914002
Open the place page for this point
id:
NSR:StopPlace:5087
name:
Kvakestad
label:
Kvakestad, Nordre Follo
category:
1 results
1. onstreetBus
municipality:
Nordre Follo
county:
Akershus
lat:
59.736884
lon:
10.842036
Open the place page for this point
id:
NSR:StopPlace:45209
name:
Kvelstad
label:
Kvelstad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.771559
lon:
11.701137
Open the place page for this point
id:
NSR:StopPlace:13618
name:
Kvikstad
label:
Kvikstad, Østre Toten
category:
1 results
1. onstreetBus
municipality:
Østre Toten
county:
Innlandet
lat:
60.611486
lon:
10.770274

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:24371
name:
Kvastad
label:
Kvastad, Tvedestrand
category:
1 results
1. onstreetBus
municipality:
Tvedestrand
county:
Agder
lat:
58.569203
lon:
8.892274
Open the place page for this point
id:
NSR:StopPlace:24365
name:
Kvastad nord
label:
Kvastad nord, Tvedestrand
category:
1 results
1. onstreetBus
municipality:
Tvedestrand
county:
Agder
lat:
58.572556
lon:
8.888572
Open the place page for this point
id:
NSR:StopPlace:27887
name:
Kvæstad
label:
Kvæstad, Suldal
category:
1 results
1. onstreetBus
municipality:
Suldal
county:
Rogaland
lat:
59.455908
lon:
6.384165
Open the place page for this point
id:
NSR:StopPlace:36735
name:
Kvalstad
label:
Kvalstad, Kinn
category:
1 results
1. onstreetBus
municipality:
Kinn
county:
Vestland
lat:
61.479277
lon:
5.089687
Open the place page for this point
id:
NSR:StopPlace:40302
name:
Kvistad
label:
Kvistad, Ørsta
category:
1 results
1. onstreetBus
municipality:
Ørsta
county:
Møre og Romsdal
lat:
62.194704
lon:
6.417224
Open the place page for this point
id:
NSR:StopPlace:20578
name:
Kvestad
label:
Kvestad, Porsgrunn
category:
1 results
1. onstreetBus
municipality:
Porsgrunn
county:
Telemark
lat:
59.13701
lon:
9.72987
Open the place page for this point
id:
NSR:StopPlace:45429
name:
Kvistad
label:
Kvistad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.814772
lon:
11.465001
Open the place page for this point
id:
NSR:StopPlace:50175
name:
Kvikstad
label:
Kvikstad, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.230706
lon:
14.914002
Open the place page for this point
id:
NSR:StopPlace:5087
name:
Kvakestad
label:
Kvakestad, Nordre Follo
category:
1 results
1. onstreetBus
municipality:
Nordre Follo
county:
Akershus
lat:
59.736884
lon:
10.842036
Open the place page for this point
id:
NSR:StopPlace:45209
name:
Kvelstad
label:
Kvelstad, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.771559
lon:
11.701137
Open the place page for this point
id:
NSR:StopPlace:13618
name:
Kvikstad
label:
Kvikstad, Østre Toten
category:
1 results
1. onstreetBus
municipality:
Østre Toten
county:
Innlandet
lat:
60.611486
lon:
10.770274

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.