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-09-29T21:41:33Z in 0.140 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:7919
name:
Ryeng
label:
Ryeng, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.187995
lon:
10.261003
Open the place page for this point
id:
NSR:StopPlace:52295
name:
Ryeng
label:
Ryeng, Storfjord
category:
1 results
1. onstreetBus
municipality:
Storfjord
county:
Troms
lat:
69.258005
lon:
19.985431
Open the place page for this point
id:
NSR:StopPlace:52298
name:
Ryeng bru
label:
Ryeng bru, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
68.969095
lon:
18.926605
Open the place page for this point
id:
NSR:StopPlace:58248
name:
Ryen
label:
Ryen, Oslo
category:
2 results
1. metroStation
2. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.895516
lon:
10.804785
Open the place page for this point
id:
NSR:StopPlace:70090
name:
Rydeng
label:
Rydeng, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.240466
lon:
18.350574
Open the place page for this point
id:
NSR:StopPlace:10193
name:
Ryen
label:
Ryen, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.890254
lon:
10.844886
Open the place page for this point
id:
NSR:StopPlace:52264
name:
Rydeng
label:
Rydeng, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.923265
lon:
21.228291
Open the place page for this point
id:
NSR:StopPlace:6961
name:
Ryen
label:
Ryen, Tolga
category:
1 results
1. onstreetBus
municipality:
Tolga
county:
Innlandet
lat:
62.415684
lon:
10.907302
Open the place page for this point
id:
NSR:StopPlace:7927
name:
Ryen
label:
Ryen, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.172576
lon:
10.205682
Open the place page for this point
id:
NSR:StopPlace:21941
name:
Ryen
label:
Ryen, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.220329
lon:
8.109645
Open the place page for this point
id:
NSR:StopPlace:13195
name:
Ryen
label:
Ryen, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.711364
lon:
9.451241
Open the place page for this point
id:
NSR:StopPlace:41839
name:
Ryen
label:
Ryen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.740215
lon:
11.324608

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:7919
name:
Ryeng
label:
Ryeng, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.187995
lon:
10.261003
Open the place page for this point
id:
NSR:StopPlace:52295
name:
Ryeng
label:
Ryeng, Storfjord
category:
1 results
1. onstreetBus
municipality:
Storfjord
county:
Troms
lat:
69.258005
lon:
19.985431
Open the place page for this point
id:
NSR:StopPlace:52298
name:
Ryeng bru
label:
Ryeng bru, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
68.969095
lon:
18.926605
Open the place page for this point
id:
NSR:StopPlace:58248
name:
Ryen
label:
Ryen, Oslo
category:
2 results
1. metroStation
2. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.895516
lon:
10.804785
Open the place page for this point
id:
NSR:StopPlace:70090
name:
Rydeng
label:
Rydeng, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.240466
lon:
18.350574
Open the place page for this point
id:
NSR:StopPlace:10193
name:
Ryen
label:
Ryen, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.890254
lon:
10.844886
Open the place page for this point
id:
NSR:StopPlace:52264
name:
Rydeng
label:
Rydeng, Nordreisa
category:
1 results
1. onstreetBus
municipality:
Nordreisa
county:
Troms
lat:
69.923265
lon:
21.228291
Open the place page for this point
id:
NSR:StopPlace:6961
name:
Ryen
label:
Ryen, Tolga
category:
1 results
1. onstreetBus
municipality:
Tolga
county:
Innlandet
lat:
62.415684
lon:
10.907302
Open the place page for this point
id:
NSR:StopPlace:7927
name:
Ryen
label:
Ryen, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.172576
lon:
10.205682
Open the place page for this point
id:
NSR:StopPlace:21941
name:
Ryen
label:
Ryen, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.220329
lon:
8.109645
Open the place page for this point
id:
NSR:StopPlace:13195
name:
Ryen
label:
Ryen, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.711364
lon:
9.451241
Open the place page for this point
id:
NSR:StopPlace:41839
name:
Ryen
label:
Ryen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.740215
lon:
11.324608

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.