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-01T05:43:50Z in 0.164 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:26990
name:
Molaug
label:
Molaug, Gjesdal
category:
1 results
1. onstreetBus
municipality:
Gjesdal
county:
Rogaland
lat:
58.842871
lon:
6.350519
Open the place page for this point
id:
NSR:StopPlace:42802
name:
Moshaug
label:
Moshaug, Midtre Gauldal
category:
1 results
1. onstreetBus
municipality:
Midtre Gauldal
county:
Trøndelag
lat:
62.868319
lon:
10.239593
Open the place page for this point
id:
NSR:StopPlace:42754
name:
Moltun
label:
Moltun, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.560473
lon:
9.475501
Open the place page for this point
id:
NSR:StopPlace:22568
name:
Moland
label:
Moland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.342954
lon:
7.469093
Open the place page for this point
id:
NSR:StopPlace:22564
name:
Moland
label:
Moland, Vegårshei
category:
1 results
1. onstreetBus
municipality:
Vegårshei
county:
Agder
lat:
58.760202
lon:
8.85897
Open the place page for this point
id:
NSR:StopPlace:54732
name:
Moland
label:
Moland, Ibestad
category:
1 results
1. onstreetBus
municipality:
Ibestad
county:
Troms
lat:
68.889366
lon:
17.227114
Open the place page for this point
id:
NSR:StopPlace:22561
name:
Moland
label:
Moland, Risør
category:
1 results
1. onstreetBus
municipality:
Risør
county:
Agder
lat:
58.740145
lon:
9.031544
Open the place page for this point
id:
NSR:StopPlace:22570
name:
Moland
label:
Moland, Kvinesdal
category:
1 results
1. onstreetBus
municipality:
Kvinesdal
county:
Agder
lat:
58.605911
lon:
6.895771
Open the place page for this point
id:
NSR:StopPlace:18404
name:
Moland
label:
Moland, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.319847
lon:
10.157678
Open the place page for this point
id:
NSR:StopPlace:20391
name:
Moland
label:
Moland, Drangedal
category:
1 results
1. onstreetBus
municipality:
Drangedal
county:
Telemark
lat:
59.049439
lon:
9.176416
Open the place page for this point
id:
NSR:StopPlace:47153
name:
Moland
label:
Moland, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.238696
lon:
14.116595

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:26990
name:
Molaug
label:
Molaug, Gjesdal
category:
1 results
1. onstreetBus
municipality:
Gjesdal
county:
Rogaland
lat:
58.842871
lon:
6.350519
Open the place page for this point
id:
NSR:StopPlace:42802
name:
Moshaug
label:
Moshaug, Midtre Gauldal
category:
1 results
1. onstreetBus
municipality:
Midtre Gauldal
county:
Trøndelag
lat:
62.868319
lon:
10.239593
Open the place page for this point
id:
NSR:StopPlace:42754
name:
Moltun
label:
Moltun, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.560473
lon:
9.475501
Open the place page for this point
id:
NSR:StopPlace:22568
name:
Moland
label:
Moland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.342954
lon:
7.469093
Open the place page for this point
id:
NSR:StopPlace:22564
name:
Moland
label:
Moland, Vegårshei
category:
1 results
1. onstreetBus
municipality:
Vegårshei
county:
Agder
lat:
58.760202
lon:
8.85897
Open the place page for this point
id:
NSR:StopPlace:54732
name:
Moland
label:
Moland, Ibestad
category:
1 results
1. onstreetBus
municipality:
Ibestad
county:
Troms
lat:
68.889366
lon:
17.227114
Open the place page for this point
id:
NSR:StopPlace:22561
name:
Moland
label:
Moland, Risør
category:
1 results
1. onstreetBus
municipality:
Risør
county:
Agder
lat:
58.740145
lon:
9.031544
Open the place page for this point
id:
NSR:StopPlace:22570
name:
Moland
label:
Moland, Kvinesdal
category:
1 results
1. onstreetBus
municipality:
Kvinesdal
county:
Agder
lat:
58.605911
lon:
6.895771
Open the place page for this point
id:
NSR:StopPlace:18404
name:
Moland
label:
Moland, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.319847
lon:
10.157678
Open the place page for this point
id:
NSR:StopPlace:20391
name:
Moland
label:
Moland, Drangedal
category:
1 results
1. onstreetBus
municipality:
Drangedal
county:
Telemark
lat:
59.049439
lon:
9.176416
Open the place page for this point
id:
NSR:StopPlace:47153
name:
Moland
label:
Moland, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.238696
lon:
14.116595

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.