search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
`lang`	optional	string	Result language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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-11-13T02:04:38Z in 0.228 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:42893
name:
Myrind
label:
Myrind, Skaun
category:
1 results
1. onstreetBus
municipality:
Skaun
county:
Trøndelag
lat:
63.268758
lon:
10.018968
Open the place page for this point
id:
NSR:StopPlace:56777
name:
Meland
label:
Meland, Hammerfest
category:
1 results
1. onstreetBus
municipality:
Hammerfest
county:
Finnmark
lat:
70.67957
lon:
23.639032
Open the place page for this point
id:
NSR:StopPlace:30234
name:
Meland
label:
Meland, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.76618
lon:
6.471049
Open the place page for this point
id:
NSR:StopPlace:26863
name:
Meling
label:
Meling, Strand
category:
1 results
1. onstreetBus
municipality:
Strand
county:
Rogaland
lat:
58.942785
lon:
6.023238
Open the place page for this point
id:
NSR:StopPlace:26852
name:
Meland
label:
Meland, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.790851
lon:
5.656182
Open the place page for this point
id:
NSR:StopPlace:34951
name:
Meland
label:
Meland, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.315504
lon:
6.576352
Open the place page for this point
id:
NSR:StopPlace:22407
name:
Meland
label:
Meland, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.506142
lon:
7.161853
Open the place page for this point
id:
NSR:StopPlace:40341
name:
Mevold
label:
Mevold, Aukra
category:
1 results
1. onstreetBus
municipality:
Aukra
county:
Møre og Romsdal
lat:
62.762349
lon:
6.999338
Open the place page for this point
id:
NSR:StopPlace:34863
name:
Meland
label:
Meland, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.932013
lon:
6.922156
Open the place page for this point
id:
NSR:StopPlace:30231
name:
Meland
label:
Meland, Etne
category:
1 results
1. onstreetBus
municipality:
Etne
county:
Vestland
lat:
59.639319
lon:
5.900675
Open the place page for this point
id:
NSR:StopPlace:26855
name:
Meland
label:
Meland, Vindafjord
category:
1 results
1. onstreetBus
municipality:
Vindafjord
county:
Rogaland
lat:
59.490599
lon:
5.554793
Open the place page for this point
id:
NSR:StopPlace:47834
name:
Mevik
label:
Mevik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
66.945225
lon:
13.734632

Show all fields in HTML

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:42893
name:
Myrind
label:
Myrind, Skaun
category:
1 results
1. onstreetBus
municipality:
Skaun
county:
Trøndelag
lat:
63.268758
lon:
10.018968
Open the place page for this point
id:
NSR:StopPlace:56777
name:
Meland
label:
Meland, Hammerfest
category:
1 results
1. onstreetBus
municipality:
Hammerfest
county:
Finnmark
lat:
70.67957
lon:
23.639032
Open the place page for this point
id:
NSR:StopPlace:30234
name:
Meland
label:
Meland, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.76618
lon:
6.471049
Open the place page for this point
id:
NSR:StopPlace:26863
name:
Meling
label:
Meling, Strand
category:
1 results
1. onstreetBus
municipality:
Strand
county:
Rogaland
lat:
58.942785
lon:
6.023238
Open the place page for this point
id:
NSR:StopPlace:26852
name:
Meland
label:
Meland, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.790851
lon:
5.656182
Open the place page for this point
id:
NSR:StopPlace:34951
name:
Meland
label:
Meland, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.315504
lon:
6.576352
Open the place page for this point
id:
NSR:StopPlace:22407
name:
Meland
label:
Meland, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.506142
lon:
7.161853
Open the place page for this point
id:
NSR:StopPlace:40341
name:
Mevold
label:
Mevold, Aukra
category:
1 results
1. onstreetBus
municipality:
Aukra
county:
Møre og Romsdal
lat:
62.762349
lon:
6.999338
Open the place page for this point
id:
NSR:StopPlace:34863
name:
Meland
label:
Meland, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.932013
lon:
6.922156
Open the place page for this point
id:
NSR:StopPlace:30231
name:
Meland
label:
Meland, Etne
category:
1 results
1. onstreetBus
municipality:
Etne
county:
Vestland
lat:
59.639319
lon:
5.900675
Open the place page for this point
id:
NSR:StopPlace:26855
name:
Meland
label:
Meland, Vindafjord
category:
1 results
1. onstreetBus
municipality:
Vindafjord
county:
Rogaland
lat:
59.490599
lon:
5.554793
Open the place page for this point
id:
NSR:StopPlace:47834
name:
Mevik
label:
Mevik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
66.945225
lon:
13.734632

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.