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-05T21:49:27Z in 0.214 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:40100
name:
Krikane
label:
Krikane, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.33816
lon:
7.54016
Open the place page for this point
id:
NSR:StopPlace:53620
name:
Krokan
label:
Krokan, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.678112
lon:
17.484825
Open the place page for this point
id:
NSR:StopPlace:63452
name:
Kriken
label:
Kriken, Luster
category:
1 results
1. onstreetBus
municipality:
Luster
county:
Vestland
lat:
61.534095
lon:
7.600383
Open the place page for this point
id:
NSR:StopPlace:20509
name:
Krokan
label:
Krokan, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
59.866698
lon:
8.473972
Open the place page for this point
id:
NSR:StopPlace:43332
name:
Krokan
label:
Krokan, Oppdal
category:
1 results
1. onstreetBus
municipality:
Oppdal
county:
Trøndelag
lat:
62.643735
lon:
9.822488
Open the place page for this point
id:
NSR:StopPlace:49174
name:
Krokan
label:
Krokan, Hamarøy
category:
1 results
1. onstreetBus
municipality:
Hamarøy
county:
Nordland
lat:
67.973918
lon:
15.984794
Open the place page for this point
id:
NSR:StopPlace:53604
name:
Kriken
label:
Kriken, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.216153
lon:
19.495892
Open the place page for this point
id:
NSR:StopPlace:53623
name:
Krokan
label:
Krokan, Storfjord
category:
1 results
1. onstreetBus
municipality:
Storfjord
county:
Troms
lat:
69.236798
lon:
19.837002
Open the place page for this point
id:
NSR:StopPlace:40102
name:
Kriken
label:
Kriken, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.505878
lon:
6.652421
Open the place page for this point
id:
NSR:StopPlace:45280
name:
Kriken
label:
Kriken, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.725192
lon:
11.806237
Open the place page for this point
id:
NSR:StopPlace:53606
name:
Kriken
label:
Kriken, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.763226
lon:
20.4839
Open the place page for this point
id:
NSR:StopPlace:59033
name:
Kriken
label:
Kriken, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.377684
lon:
6.160028

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:40100
name:
Krikane
label:
Krikane, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.33816
lon:
7.54016
Open the place page for this point
id:
NSR:StopPlace:53620
name:
Krokan
label:
Krokan, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.678112
lon:
17.484825
Open the place page for this point
id:
NSR:StopPlace:63452
name:
Kriken
label:
Kriken, Luster
category:
1 results
1. onstreetBus
municipality:
Luster
county:
Vestland
lat:
61.534095
lon:
7.600383
Open the place page for this point
id:
NSR:StopPlace:20509
name:
Krokan
label:
Krokan, Tinn
category:
1 results
1. onstreetBus
municipality:
Tinn
county:
Telemark
lat:
59.866698
lon:
8.473972
Open the place page for this point
id:
NSR:StopPlace:43332
name:
Krokan
label:
Krokan, Oppdal
category:
1 results
1. onstreetBus
municipality:
Oppdal
county:
Trøndelag
lat:
62.643735
lon:
9.822488
Open the place page for this point
id:
NSR:StopPlace:49174
name:
Krokan
label:
Krokan, Hamarøy
category:
1 results
1. onstreetBus
municipality:
Hamarøy
county:
Nordland
lat:
67.973918
lon:
15.984794
Open the place page for this point
id:
NSR:StopPlace:53604
name:
Kriken
label:
Kriken, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.216153
lon:
19.495892
Open the place page for this point
id:
NSR:StopPlace:53623
name:
Krokan
label:
Krokan, Storfjord
category:
1 results
1. onstreetBus
municipality:
Storfjord
county:
Troms
lat:
69.236798
lon:
19.837002
Open the place page for this point
id:
NSR:StopPlace:40102
name:
Kriken
label:
Kriken, Ålesund
category:
1 results
1. onstreetBus
municipality:
Ålesund
county:
Møre og Romsdal
lat:
62.505878
lon:
6.652421
Open the place page for this point
id:
NSR:StopPlace:45280
name:
Kriken
label:
Kriken, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.725192
lon:
11.806237
Open the place page for this point
id:
NSR:StopPlace:53606
name:
Kriken
label:
Kriken, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.763226
lon:
20.4839
Open the place page for this point
id:
NSR:StopPlace:59033
name:
Kriken
label:
Kriken, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.377684
lon:
6.160028

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.