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-03T22:26:07Z in 0.246 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:47142
name:
Følvik
label:
Følvik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
67.136384
lon:
14.203302
Open the place page for this point
id:
NSR:StopPlace:19070
name:
Foldvik
label:
Foldvik, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
58.996038
lon:
9.968604
Open the place page for this point
id:
NSR:StopPlace:39089
name:
Flovik
label:
Flovik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.693073
lon:
7.402553
Open the place page for this point
id:
NSR:StopPlace:62930
name:
Frøvik
label:
Frøvik, Leka
category:
1 results
1. ferryStop
municipality:
Leka
county:
Trøndelag
lat:
65.068907
lon:
11.671142
Open the place page for this point
id:
NSR:StopPlace:894
name:
Fløvik
label:
Fløvik, Marker
category:
1 results
1. onstreetBus
municipality:
Marker
county:
Østfold
lat:
59.402386
lon:
11.669709
Open the place page for this point
id:
NSR:StopPlace:25311
name:
Færvik
label:
Færvik, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.455282
lon:
8.816991
Open the place page for this point
id:
NSR:StopPlace:34911
name:
Folven
label:
Folven, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.918
lon:
7.175397
Open the place page for this point
id:
NSR:StopPlace:46209
name:
Frøvik
label:
Frøvik, Leka
category:
1 results
1. onstreetBus
municipality:
Leka
county:
Trøndelag
lat:
65.070038
lon:
11.669258
Open the place page for this point
id:
NSR:StopPlace:44857
name:
Fjølvika
label:
Fjølvika, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.584435
lon:
10.189696
Open the place page for this point
id:
NSR:StopPlace:46024
name:
Fjølvika
label:
Fjølvika, Nærøysund
category:
1 results
1. onstreetBus
municipality:
Nærøysund
county:
Trøndelag
lat:
65.014661
lon:
11.711249
Open the place page for this point
id:
NSR:StopPlace:55578
name:
Foldvika
label:
Foldvika, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.692964
lon:
17.424259
Open the place page for this point
id:
NSR:StopPlace:36902
name:
Frivik
label:
Frivik, Høyanger
category:
1 results
1. onstreetBus
municipality:
Høyanger
county:
Vestland
lat:
61.165102
lon:
5.866522

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:47142
name:
Følvik
label:
Følvik, Gildeskål
category:
1 results
1. onstreetBus
municipality:
Gildeskål
county:
Nordland
lat:
67.136384
lon:
14.203302
Open the place page for this point
id:
NSR:StopPlace:19070
name:
Foldvik
label:
Foldvik, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
58.996038
lon:
9.968604
Open the place page for this point
id:
NSR:StopPlace:39089
name:
Flovik
label:
Flovik, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.693073
lon:
7.402553
Open the place page for this point
id:
NSR:StopPlace:62930
name:
Frøvik
label:
Frøvik, Leka
category:
1 results
1. ferryStop
municipality:
Leka
county:
Trøndelag
lat:
65.068907
lon:
11.671142
Open the place page for this point
id:
NSR:StopPlace:894
name:
Fløvik
label:
Fløvik, Marker
category:
1 results
1. onstreetBus
municipality:
Marker
county:
Østfold
lat:
59.402386
lon:
11.669709
Open the place page for this point
id:
NSR:StopPlace:25311
name:
Færvik
label:
Færvik, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.455282
lon:
8.816991
Open the place page for this point
id:
NSR:StopPlace:34911
name:
Folven
label:
Folven, Stryn
category:
1 results
1. onstreetBus
municipality:
Stryn
county:
Vestland
lat:
61.918
lon:
7.175397
Open the place page for this point
id:
NSR:StopPlace:46209
name:
Frøvik
label:
Frøvik, Leka
category:
1 results
1. onstreetBus
municipality:
Leka
county:
Trøndelag
lat:
65.070038
lon:
11.669258
Open the place page for this point
id:
NSR:StopPlace:44857
name:
Fjølvika
label:
Fjølvika, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.584435
lon:
10.189696
Open the place page for this point
id:
NSR:StopPlace:46024
name:
Fjølvika
label:
Fjølvika, Nærøysund
category:
1 results
1. onstreetBus
municipality:
Nærøysund
county:
Trøndelag
lat:
65.014661
lon:
11.711249
Open the place page for this point
id:
NSR:StopPlace:55578
name:
Foldvika
label:
Foldvika, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.692964
lon:
17.424259
Open the place page for this point
id:
NSR:StopPlace:36902
name:
Frivik
label:
Frivik, Høyanger
category:
1 results
1. onstreetBus
municipality:
Høyanger
county:
Vestland
lat:
61.165102
lon:
5.866522

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.