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-30T23:24:15Z in 0.138 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:31129
name:
Velure
label:
Velure, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.332183
lon:
6.610309
Open the place page for this point
id:
NSR:StopPlace:31134
name:
Velure kro
label:
Velure kro, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.334813
lon:
6.618383
Open the place page for this point
id:
NSR:StopPlace:17892
name:
Veldre
label:
Veldre, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.05104
lon:
9.987229
Open the place page for this point
id:
NSR:StopPlace:1971
name:
Velund
label:
Velund, Rakkestad
category:
1 results
1. onstreetBus
municipality:
Rakkestad
county:
Østfold
lat:
59.255345
lon:
11.441782
Open the place page for this point
id:
NSR:StopPlace:37999
name:
Vestre
label:
Vestre, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.459253
lon:
6.877931
Open the place page for this point
id:
NSR:StopPlace:3180
name:
Vettre
label:
Vettre, Asker
category:
1 results
1. onstreetBus
municipality:
Asker
county:
Akershus
lat:
59.828352
lon:
10.471956
Open the place page for this point
id:
NSR:StopPlace:45841
name:
Vestre
label:
Vestre, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.469661
lon:
11.483419
Open the place page for this point
id:
NSR:StopPlace:42099
name:
Velve
label:
Velve, Selbu
category:
1 results
1. onstreetBus
municipality:
Selbu
county:
Trøndelag
lat:
63.205084
lon:
11.084065
Open the place page for this point
id:
NSR:StopPlace:37886
name:
Velle
label:
Velle, Sykkylven
category:
1 results
1. onstreetBus
municipality:
Sykkylven
county:
Møre og Romsdal
lat:
62.297881
lon:
6.631864
Open the place page for this point
id:
NSR:StopPlace:26307
name:
Velde
label:
Velde, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.350894
lon:
5.276554
Open the place page for this point
id:
NSR:StopPlace:22387
name:
Vere
label:
Vere, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.125151
lon:
6.609488
Open the place page for this point
id:
NSR:StopPlace:32780
name:
Vele
label:
Vele, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.592879
lon:
6.456884

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:31129
name:
Velure
label:
Velure, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.332183
lon:
6.610309
Open the place page for this point
id:
NSR:StopPlace:31134
name:
Velure kro
label:
Velure kro, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.334813
lon:
6.618383
Open the place page for this point
id:
NSR:StopPlace:17892
name:
Veldre
label:
Veldre, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
59.05104
lon:
9.987229
Open the place page for this point
id:
NSR:StopPlace:1971
name:
Velund
label:
Velund, Rakkestad
category:
1 results
1. onstreetBus
municipality:
Rakkestad
county:
Østfold
lat:
59.255345
lon:
11.441782
Open the place page for this point
id:
NSR:StopPlace:37999
name:
Vestre
label:
Vestre, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.459253
lon:
6.877931
Open the place page for this point
id:
NSR:StopPlace:3180
name:
Vettre
label:
Vettre, Asker
category:
1 results
1. onstreetBus
municipality:
Asker
county:
Akershus
lat:
59.828352
lon:
10.471956
Open the place page for this point
id:
NSR:StopPlace:45841
name:
Vestre
label:
Vestre, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.469661
lon:
11.483419
Open the place page for this point
id:
NSR:StopPlace:42099
name:
Velve
label:
Velve, Selbu
category:
1 results
1. onstreetBus
municipality:
Selbu
county:
Trøndelag
lat:
63.205084
lon:
11.084065
Open the place page for this point
id:
NSR:StopPlace:37886
name:
Velle
label:
Velle, Sykkylven
category:
1 results
1. onstreetBus
municipality:
Sykkylven
county:
Møre og Romsdal
lat:
62.297881
lon:
6.631864
Open the place page for this point
id:
NSR:StopPlace:26307
name:
Velde
label:
Velde, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.350894
lon:
5.276554
Open the place page for this point
id:
NSR:StopPlace:22387
name:
Vere
label:
Vere, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.125151
lon:
6.609488
Open the place page for this point
id:
NSR:StopPlace:32780
name:
Vele
label:
Vele, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.592879
lon:
6.456884

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.