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-23T12:31:43Z in 0.168 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:61597
name:
Ratvika
label:
Ratvika, Åfjord
category:
1 results
1. onstreetBus
municipality:
Åfjord
county:
Trøndelag
lat:
63.974165
lon:
9.993128
Open the place page for this point
id:
NSR:StopPlace:41644
name:
Ramvika
label:
Ramvika, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.529762
lon:
9.428493
Open the place page for this point
id:
NSR:StopPlace:56650
name:
Ravika
label:
Ravika, Lyngen
category:
1 results
1. onstreetBus
municipality:
Lyngen
county:
Troms
lat:
69.827166
lon:
19.959515
Open the place page for this point
id:
NSR:StopPlace:63456
name:
Raudvika
label:
Raudvika, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.500911
lon:
9.186298
Open the place page for this point
id:
NSR:StopPlace:41637
name:
Ramsvika
label:
Ramsvika, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.751334
lon:
10.087491
Open the place page for this point
id:
NSR:StopPlace:41333
name:
Ramsvika
label:
Ramsvika, Aure
category:
1 results
1. onstreetBus
municipality:
Aure
county:
Møre og Romsdal
lat:
63.325474
lon:
8.534514
Open the place page for this point
id:
NSR:StopPlace:44420
name:
Ramsvika
label:
Ramsvika, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.514376
lon:
11.485691
Open the place page for this point
id:
NSR:StopPlace:41361
name:
Ranvik
label:
Ranvik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.7419
lon:
7.758468
Open the place page for this point
id:
NSR:StopPlace:15513
name:
Ranvik
label:
Ranvik, Flesberg
category:
1 results
1. onstreetBus
municipality:
Flesberg
county:
Buskerud
lat:
59.846844
lon:
9.570619
Open the place page for this point
id:
NSR:StopPlace:17465
name:
Ranvik
label:
Ranvik, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.117086
lon:
10.219745
Open the place page for this point
id:
NSR:StopPlace:41357
name:
Ranvik
label:
Ranvik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.744316
lon:
7.771409
Open the place page for this point
id:
NSR:StopPlace:50323
name:
Ravik
label:
Ravik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
67.122167
lon:
14.150925

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:61597
name:
Ratvika
label:
Ratvika, Åfjord
category:
1 results
1. onstreetBus
municipality:
Åfjord
county:
Trøndelag
lat:
63.974165
lon:
9.993128
Open the place page for this point
id:
NSR:StopPlace:41644
name:
Ramvika
label:
Ramvika, Orkland
category:
1 results
1. onstreetBus
municipality:
Orkland
county:
Trøndelag
lat:
63.529762
lon:
9.428493
Open the place page for this point
id:
NSR:StopPlace:56650
name:
Ravika
label:
Ravika, Lyngen
category:
1 results
1. onstreetBus
municipality:
Lyngen
county:
Troms
lat:
69.827166
lon:
19.959515
Open the place page for this point
id:
NSR:StopPlace:63456
name:
Raudvika
label:
Raudvika, Hitra
category:
1 results
1. onstreetBus
municipality:
Hitra
county:
Trøndelag
lat:
63.500911
lon:
9.186298
Open the place page for this point
id:
NSR:StopPlace:41637
name:
Ramsvika
label:
Ramsvika, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.751334
lon:
10.087491
Open the place page for this point
id:
NSR:StopPlace:41333
name:
Ramsvika
label:
Ramsvika, Aure
category:
1 results
1. onstreetBus
municipality:
Aure
county:
Møre og Romsdal
lat:
63.325474
lon:
8.534514
Open the place page for this point
id:
NSR:StopPlace:44420
name:
Ramsvika
label:
Ramsvika, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.514376
lon:
11.485691
Open the place page for this point
id:
NSR:StopPlace:41361
name:
Ranvik
label:
Ranvik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.7419
lon:
7.758468
Open the place page for this point
id:
NSR:StopPlace:15513
name:
Ranvik
label:
Ranvik, Flesberg
category:
1 results
1. onstreetBus
municipality:
Flesberg
county:
Buskerud
lat:
59.846844
lon:
9.570619
Open the place page for this point
id:
NSR:StopPlace:17465
name:
Ranvik
label:
Ranvik, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.117086
lon:
10.219745
Open the place page for this point
id:
NSR:StopPlace:41357
name:
Ranvik
label:
Ranvik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.744316
lon:
7.771409
Open the place page for this point
id:
NSR:StopPlace:50323
name:
Ravik
label:
Ravik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
67.122167
lon:
14.150925

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.