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-03T01:37:12Z in 1.692 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:22240
name:
Sandstø
label:
Sandstø, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.428121
lon:
8.69945
Open the place page for this point
id:
NSR:StopPlace:31015
name:
Sandstå
label:
Sandstå, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.260319
lon:
6.623533
Open the place page for this point
id:
NSR:StopPlace:41979
name:
Sandstad
label:
Sandstad, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.521735
lon:
9.104842
Open the place page for this point
id:
NSR:StopPlace:41982
name:
Sandstad
label:
Sandstad, Ørland
category:
1 results
1. onstreetBus
municipality:
Ørland
county:
Trøndelag
lat:
63.804622
lon:
9.663256
Open the place page for this point
id:
NSR:StopPlace:52652
name:
Sandstad
label:
Sandstad, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
68.915184
lon:
18.988959
Open the place page for this point
id:
NSR:StopPlace:51256
name:
Sandstad
label:
Sandstad, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
66.944864
lon:
13.717565
Open the place page for this point
id:
NSR:StopPlace:44232
name:
Sandstad
label:
Sandstad, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.507236
lon:
13.693396
Open the place page for this point
id:
NSR:StopPlace:50802
name:
Sandmo
label:
Sandmo, Fauske
category:
1 results
1. onstreetBus
municipality:
Fauske
county:
Nordland
lat:
67.374127
lon:
15.307992
Open the place page for this point
id:
NSR:StopPlace:44915
name:
Sandmo
label:
Sandmo, Overhalla
category:
1 results
1. onstreetBus
municipality:
Overhalla
county:
Trøndelag
lat:
64.462327
lon:
11.66001
Open the place page for this point
id:
NSR:StopPlace:52602
name:
Sandmo
label:
Sandmo, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.325439
lon:
19.411278
Open the place page for this point
id:
NSR:StopPlace:70135
name:
Sandmo
label:
Sandmo, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.319455
lon:
18.543726
Open the place page for this point
id:
NSR:StopPlace:17724
name:
Sando
label:
Sando, Holmestrand
category:
1 results
1. onstreetBus
municipality:
Holmestrand
county:
Vestfold
lat:
59.540341
lon:
10.311365

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:22240
name:
Sandstø
label:
Sandstø, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.428121
lon:
8.69945
Open the place page for this point
id:
NSR:StopPlace:31015
name:
Sandstå
label:
Sandstå, Ullensvang
category:
1 results
1. onstreetBus
municipality:
Ullensvang
county:
Vestland
lat:
60.260319
lon:
6.623533
Open the place page for this point
id:
NSR:StopPlace:41979
name:
Sandstad
label:
Sandstad, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.521735
lon:
9.104842
Open the place page for this point
id:
NSR:StopPlace:41982
name:
Sandstad
label:
Sandstad, Ørland
category:
1 results
1. onstreetBus
municipality:
Ørland
county:
Trøndelag
lat:
63.804622
lon:
9.663256
Open the place page for this point
id:
NSR:StopPlace:52652
name:
Sandstad
label:
Sandstad, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
68.915184
lon:
18.988959
Open the place page for this point
id:
NSR:StopPlace:51256
name:
Sandstad
label:
Sandstad, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
66.944864
lon:
13.717565
Open the place page for this point
id:
NSR:StopPlace:44232
name:
Sandstad
label:
Sandstad, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.507236
lon:
13.693396
Open the place page for this point
id:
NSR:StopPlace:50802
name:
Sandmo
label:
Sandmo, Fauske
category:
1 results
1. onstreetBus
municipality:
Fauske
county:
Nordland
lat:
67.374127
lon:
15.307992
Open the place page for this point
id:
NSR:StopPlace:44915
name:
Sandmo
label:
Sandmo, Overhalla
category:
1 results
1. onstreetBus
municipality:
Overhalla
county:
Trøndelag
lat:
64.462327
lon:
11.66001
Open the place page for this point
id:
NSR:StopPlace:52602
name:
Sandmo
label:
Sandmo, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.325439
lon:
19.411278
Open the place page for this point
id:
NSR:StopPlace:70135
name:
Sandmo
label:
Sandmo, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.319455
lon:
18.543726
Open the place page for this point
id:
NSR:StopPlace:17724
name:
Sando
label:
Sando, Holmestrand
category:
1 results
1. onstreetBus
municipality:
Holmestrand
county:
Vestfold
lat:
59.540341
lon:
10.311365

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.