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-30T06:08:51Z in 0.165 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:58232
name:
Reindal
label:
Reindal, Salangen
category:
1 results
1. onstreetBus
municipality:
Salangen
county:
Troms
lat:
68.839154
lon:
17.876301
Open the place page for this point
id:
NSR:StopPlace:56660
name:
Reindalen
label:
Reindalen, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.213774
lon:
17.818199
Open the place page for this point
id:
NSR:StopPlace:56773
name:
Reindalen
label:
Reindalen, Hammerfest
category:
1 results
1. onstreetBus
municipality:
Hammerfest
county:
Finnmark
lat:
70.692238
lon:
23.702005
Open the place page for this point
id:
NSR:StopPlace:41467
name:
Rendal
label:
Rendal, Heim
category:
1 results
1. onstreetBus
municipality:
Heim
county:
Trøndelag
lat:
63.170038
lon:
8.618399
Open the place page for this point
id:
NSR:StopPlace:19580
name:
Refsdal
label:
Refsdal, Kragerø
category:
1 results
1. onstreetBus
municipality:
Kragerø
county:
Telemark
lat:
58.902994
lon:
9.31675
Open the place page for this point
id:
NSR:StopPlace:37219
name:
Refsdal
label:
Refsdal, Vik
category:
1 results
1. onstreetBus
municipality:
Vik
county:
Vestland
lat:
61.033443
lon:
6.581762
Open the place page for this point
id:
NSR:StopPlace:21722
name:
Reddal
label:
Reddal, Grimstad
category:
1 results
1. onstreetBus
municipality:
Grimstad
county:
Agder
lat:
58.340942
lon:
8.458131
Open the place page for this point
id:
NSR:StopPlace:41429
name:
Rekdal
label:
Rekdal, Vestnes
category:
1 results
1. onstreetBus
municipality:
Vestnes
county:
Møre og Romsdal
lat:
62.648575
lon:
6.747833
Open the place page for this point
id:
NSR:StopPlace:56659
name:
Reinan
label:
Reinan, Skjervøy
category:
1 results
1. onstreetBus
municipality:
Skjervøy
county:
Troms
lat:
70.03245
lon:
20.561531
Open the place page for this point
id:
NSR:StopPlace:50539
name:
Rekdal
label:
Rekdal, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.324596
lon:
14.004436
Open the place page for this point
id:
NSR:StopPlace:34315
name:
Redal
label:
Redal, Sunnfjord
category:
1 results
1. onstreetBus
municipality:
Sunnfjord
county:
Vestland
lat:
61.49177
lon:
5.503933
Open the place page for this point
id:
NSR:StopPlace:45449
name:
Reina
label:
Reina, Steinkjer
category:
1 results
1. onstreetBus
municipality:
Steinkjer
county:
Trøndelag
lat:
64.0172
lon:
11.519673

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:58232
name:
Reindal
label:
Reindal, Salangen
category:
1 results
1. onstreetBus
municipality:
Salangen
county:
Troms
lat:
68.839154
lon:
17.876301
Open the place page for this point
id:
NSR:StopPlace:56660
name:
Reindalen
label:
Reindalen, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.213774
lon:
17.818199
Open the place page for this point
id:
NSR:StopPlace:56773
name:
Reindalen
label:
Reindalen, Hammerfest
category:
1 results
1. onstreetBus
municipality:
Hammerfest
county:
Finnmark
lat:
70.692238
lon:
23.702005
Open the place page for this point
id:
NSR:StopPlace:41467
name:
Rendal
label:
Rendal, Heim
category:
1 results
1. onstreetBus
municipality:
Heim
county:
Trøndelag
lat:
63.170038
lon:
8.618399
Open the place page for this point
id:
NSR:StopPlace:19580
name:
Refsdal
label:
Refsdal, Kragerø
category:
1 results
1. onstreetBus
municipality:
Kragerø
county:
Telemark
lat:
58.902994
lon:
9.31675
Open the place page for this point
id:
NSR:StopPlace:37219
name:
Refsdal
label:
Refsdal, Vik
category:
1 results
1. onstreetBus
municipality:
Vik
county:
Vestland
lat:
61.033443
lon:
6.581762
Open the place page for this point
id:
NSR:StopPlace:21722
name:
Reddal
label:
Reddal, Grimstad
category:
1 results
1. onstreetBus
municipality:
Grimstad
county:
Agder
lat:
58.340942
lon:
8.458131
Open the place page for this point
id:
NSR:StopPlace:41429
name:
Rekdal
label:
Rekdal, Vestnes
category:
1 results
1. onstreetBus
municipality:
Vestnes
county:
Møre og Romsdal
lat:
62.648575
lon:
6.747833
Open the place page for this point
id:
NSR:StopPlace:56659
name:
Reinan
label:
Reinan, Skjervøy
category:
1 results
1. onstreetBus
municipality:
Skjervøy
county:
Troms
lat:
70.03245
lon:
20.561531
Open the place page for this point
id:
NSR:StopPlace:50539
name:
Rekdal
label:
Rekdal, Vestvågøy
category:
1 results
1. onstreetBus
municipality:
Vestvågøy
county:
Nordland
lat:
68.324596
lon:
14.004436
Open the place page for this point
id:
NSR:StopPlace:34315
name:
Redal
label:
Redal, Sunnfjord
category:
1 results
1. onstreetBus
municipality:
Sunnfjord
county:
Vestland
lat:
61.49177
lon:
5.503933
Open the place page for this point
id:
NSR:StopPlace:45449
name:
Reina
label:
Reina, Steinkjer
category:
1 results
1. onstreetBus
municipality:
Steinkjer
county:
Trøndelag
lat:
64.0172
lon:
11.519673

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.