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-04T07:23:52Z in 0.514 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:26489
name:
Vikse
label:
Vikse, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.479058
lon:
5.293517
Open the place page for this point
id:
NSR:StopPlace:30611
name:
Vikse skule snuplass
label:
Vikse skule snuplass, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.498123
lon:
5.298958
Open the place page for this point
id:
NSR:StopPlace:30605
name:
Vikse skule
label:
Vikse skule, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.498116
lon:
5.299649
Open the place page for this point
id:
NSR:StopPlace:63741
name:
Viksevegen 11
label:
Viksevegen 11, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.475017
lon:
5.297293
Open the place page for this point
id:
NSR:StopPlace:27448
name:
Viksevegen
label:
Viksevegen, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.473467
lon:
5.296892
Open the place page for this point
id:
NSR:StopPlace:32367
name:
Viksehoden kryss
label:
Viksehoden kryss, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.623397
lon:
6.501079
Open the place page for this point
id:
NSR:StopPlace:30621
name:
Nordre Vikse
label:
Nordre Vikse, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.496475
lon:
5.292403
Open the place page for this point
id:
NSR:StopPlace:15311
name:
Vik Senter
label:
Vik Senter, Hole
category:
1 results
1. onstreetBus
municipality:
Hole
county:
Buskerud
lat:
60.07737
lon:
10.281485
Open the place page for this point
id:
NSR:StopPlace:38130
name:
Vike
label:
Vike, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.569637
lon:
8.181266
Open the place page for this point
id:
NSR:StopPlace:11875
name:
Vike
label:
Vike, Lom
category:
1 results
1. onstreetBus
municipality:
Lom
county:
Innlandet
lat:
61.846821
lon:
8.537428
Open the place page for this point
id:
NSR:StopPlace:12702
name:
Vike
label:
Vike, Øyer
category:
1 results
1. onstreetBus
municipality:
Øyer
county:
Innlandet
lat:
61.335282
lon:
10.269162

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:26489
name:
Vikse
label:
Vikse, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.479058
lon:
5.293517
Open the place page for this point
id:
NSR:StopPlace:30611
name:
Vikse skule snuplass
label:
Vikse skule snuplass, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.498123
lon:
5.298958
Open the place page for this point
id:
NSR:StopPlace:30605
name:
Vikse skule
label:
Vikse skule, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.498116
lon:
5.299649
Open the place page for this point
id:
NSR:StopPlace:63741
name:
Viksevegen 11
label:
Viksevegen 11, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.475017
lon:
5.297293
Open the place page for this point
id:
NSR:StopPlace:27448
name:
Viksevegen
label:
Viksevegen, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.473467
lon:
5.296892
Open the place page for this point
id:
NSR:StopPlace:32367
name:
Viksehoden kryss
label:
Viksehoden kryss, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.623397
lon:
6.501079
Open the place page for this point
id:
NSR:StopPlace:30621
name:
Nordre Vikse
label:
Nordre Vikse, Sveio
category:
1 results
1. onstreetBus
municipality:
Sveio
county:
Vestland
lat:
59.496475
lon:
5.292403
Open the place page for this point
id:
NSR:StopPlace:15311
name:
Vik Senter
label:
Vik Senter, Hole
category:
1 results
1. onstreetBus
municipality:
Hole
county:
Buskerud
lat:
60.07737
lon:
10.281485
Open the place page for this point
id:
NSR:StopPlace:38130
name:
Vike
label:
Vike, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.569637
lon:
8.181266
Open the place page for this point
id:
NSR:StopPlace:11875
name:
Vike
label:
Vike, Lom
category:
1 results
1. onstreetBus
municipality:
Lom
county:
Innlandet
lat:
61.846821
lon:
8.537428
Open the place page for this point
id:
NSR:StopPlace:12702
name:
Vike
label:
Vike, Øyer
category:
1 results
1. onstreetBus
municipality:
Øyer
county:
Innlandet
lat:
61.335282
lon:
10.269162

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.