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-03T12:55:11Z in 0.164 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:34754
name:
Vegtun
label:
Vegtun, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.893408
lon:
6.611522
Open the place page for this point
id:
NSR:StopPlace:62172
name:
Veltun
label:
Veltun, Seljord
category:
1 results
1. onstreetBus
municipality:
Seljord
county:
Telemark
lat:
59.642772
lon:
8.379878
Open the place page for this point
id:
NSR:StopPlace:52844
name:
Veitun
label:
Veitun, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.756529
lon:
20.524446
Open the place page for this point
id:
NSR:StopPlace:2382
name:
Vesten
label:
Vesten, Fredrikstad
category:
1 results
1. onstreetBus
municipality:
Fredrikstad
county:
Østfold
lat:
59.258551
lon:
11.062041
Open the place page for this point
id:
NSR:StopPlace:17911
name:
Verdun
label:
Verdun, Færder
category:
1 results
1. onstreetBus
municipality:
Færder
county:
Vestfold
lat:
59.209773
lon:
10.455486
Open the place page for this point
id:
NSR:StopPlace:37854
name:
Vegsund
label:
Vegsund, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.435333
lon:
6.358642
Open the place page for this point
id:
NSR:StopPlace:53083
name:
Vårtun
label:
Vårtun, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.548183
lon:
16.628486
Open the place page for this point
id:
NSR:StopPlace:44659
name:
Valtun
label:
Valtun, Frosta
category:
1 results
1. onstreetBus
municipality:
Frosta
county:
Trøndelag
lat:
63.557111
lon:
10.68628
Open the place page for this point
id:
NSR:StopPlace:10803
name:
Vårtun
label:
Vårtun, Hamar
category:
1 results
1. onstreetBus
municipality:
Hamar
county:
Innlandet
lat:
60.868595
lon:
11.128022
Open the place page for this point
id:
NSR:StopPlace:30882
name:
Veiten
label:
Veiten, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.392784
lon:
5.321607
Open the place page for this point
id:
NSR:StopPlace:17961
name:
Vetan
label:
Vetan, Færder
category:
1 results
1. onstreetBus
municipality:
Færder
county:
Vestfold
lat:
59.175174
lon:
10.430277
Open the place page for this point
id:
NSR:StopPlace:35076
name:
Veten
label:
Veten, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.182432
lon:
6.774174

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:34754
name:
Vegtun
label:
Vegtun, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.893408
lon:
6.611522
Open the place page for this point
id:
NSR:StopPlace:62172
name:
Veltun
label:
Veltun, Seljord
category:
1 results
1. onstreetBus
municipality:
Seljord
county:
Telemark
lat:
59.642772
lon:
8.379878
Open the place page for this point
id:
NSR:StopPlace:52844
name:
Veitun
label:
Veitun, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.756529
lon:
20.524446
Open the place page for this point
id:
NSR:StopPlace:2382
name:
Vesten
label:
Vesten, Fredrikstad
category:
1 results
1. onstreetBus
municipality:
Fredrikstad
county:
Østfold
lat:
59.258551
lon:
11.062041
Open the place page for this point
id:
NSR:StopPlace:17911
name:
Verdun
label:
Verdun, Færder
category:
1 results
1. onstreetBus
municipality:
Færder
county:
Vestfold
lat:
59.209773
lon:
10.455486
Open the place page for this point
id:
NSR:StopPlace:37854
name:
Vegsund
label:
Vegsund, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.435333
lon:
6.358642
Open the place page for this point
id:
NSR:StopPlace:53083
name:
Vårtun
label:
Vårtun, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.548183
lon:
16.628486
Open the place page for this point
id:
NSR:StopPlace:44659
name:
Valtun
label:
Valtun, Frosta
category:
1 results
1. onstreetBus
municipality:
Frosta
county:
Trøndelag
lat:
63.557111
lon:
10.68628
Open the place page for this point
id:
NSR:StopPlace:10803
name:
Vårtun
label:
Vårtun, Hamar
category:
1 results
1. onstreetBus
municipality:
Hamar
county:
Innlandet
lat:
60.868595
lon:
11.128022
Open the place page for this point
id:
NSR:StopPlace:30882
name:
Veiten
label:
Veiten, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.392784
lon:
5.321607
Open the place page for this point
id:
NSR:StopPlace:17961
name:
Vetan
label:
Vetan, Færder
category:
1 results
1. onstreetBus
municipality:
Færder
county:
Vestfold
lat:
59.175174
lon:
10.430277
Open the place page for this point
id:
NSR:StopPlace:35076
name:
Veten
label:
Veten, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.182432
lon:
6.774174

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.