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-28T12:32:47Z in 0.286 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:10260
name:
Tjerne
label:
Tjerne, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.858569
lon:
10.767922
Open the place page for this point
id:
NSR:StopPlace:32397
name:
Tjernet
label:
Tjernet, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.35183
lon:
5.277927
Open the place page for this point
id:
NSR:StopPlace:2056
name:
Tjernes
label:
Tjernes, Rakkestad
category:
1 results
1. onstreetBus
municipality:
Rakkestad
county:
Østfold
lat:
59.385209
lon:
11.470815
Open the place page for this point
id:
NSR:StopPlace:52039
name:
Tjørna
label:
Tjørna, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.602534
lon:
16.688759
Open the place page for this point
id:
NSR:StopPlace:24158
name:
Tjenna
label:
Tjenna, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.4513
lon:
8.790617
Open the place page for this point
id:
NSR:StopPlace:24231
name:
Tjørve
label:
Tjørve, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.093018
lon:
6.605104
Open the place page for this point
id:
NSR:StopPlace:39255
name:
Tjelle
label:
Tjelle, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.768372
lon:
7.897852
Open the place page for this point
id:
NSR:StopPlace:8771
name:
Tjernli
label:
Tjernli, Engerdal
category:
1 results
1. onstreetBus
municipality:
Engerdal
county:
Innlandet
lat:
61.876947
lon:
12.150966
Open the place page for this point
id:
NSR:StopPlace:9325
name:
Tjennet
label:
Tjennet, Nord-Odal
category:
1 results
1. onstreetBus
municipality:
Nord-Odal
county:
Innlandet
lat:
60.374385
lon:
11.548438
Open the place page for this point
id:
NSR:StopPlace:32373
name:
Tjore
label:
Tjore, Alver
category:
1 results
1. onstreetBus
municipality:
Alver
county:
Vestland
lat:
60.6128
lon:
5.168432
Open the place page for this point
id:
NSR:StopPlace:24193
name:
Tjore
label:
Tjore, Grimstad
category:
1 results
1. onstreetBus
municipality:
Grimstad
county:
Agder
lat:
58.31737
lon:
8.521398
Open the place page for this point
id:
NSR:StopPlace:27865
name:
Tjørn
label:
Tjørn, Bjerkreim
category:
1 results
1. onstreetBus
municipality:
Bjerkreim
county:
Rogaland
lat:
58.592784
lon:
6.168338

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:10260
name:
Tjerne
label:
Tjerne, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.858569
lon:
10.767922
Open the place page for this point
id:
NSR:StopPlace:32397
name:
Tjernet
label:
Tjernet, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.35183
lon:
5.277927
Open the place page for this point
id:
NSR:StopPlace:2056
name:
Tjernes
label:
Tjernes, Rakkestad
category:
1 results
1. onstreetBus
municipality:
Rakkestad
county:
Østfold
lat:
59.385209
lon:
11.470815
Open the place page for this point
id:
NSR:StopPlace:52039
name:
Tjørna
label:
Tjørna, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.602534
lon:
16.688759
Open the place page for this point
id:
NSR:StopPlace:24158
name:
Tjenna
label:
Tjenna, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.4513
lon:
8.790617
Open the place page for this point
id:
NSR:StopPlace:24231
name:
Tjørve
label:
Tjørve, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.093018
lon:
6.605104
Open the place page for this point
id:
NSR:StopPlace:39255
name:
Tjelle
label:
Tjelle, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.768372
lon:
7.897852
Open the place page for this point
id:
NSR:StopPlace:8771
name:
Tjernli
label:
Tjernli, Engerdal
category:
1 results
1. onstreetBus
municipality:
Engerdal
county:
Innlandet
lat:
61.876947
lon:
12.150966
Open the place page for this point
id:
NSR:StopPlace:9325
name:
Tjennet
label:
Tjennet, Nord-Odal
category:
1 results
1. onstreetBus
municipality:
Nord-Odal
county:
Innlandet
lat:
60.374385
lon:
11.548438
Open the place page for this point
id:
NSR:StopPlace:32373
name:
Tjore
label:
Tjore, Alver
category:
1 results
1. onstreetBus
municipality:
Alver
county:
Vestland
lat:
60.6128
lon:
5.168432
Open the place page for this point
id:
NSR:StopPlace:24193
name:
Tjore
label:
Tjore, Grimstad
category:
1 results
1. onstreetBus
municipality:
Grimstad
county:
Agder
lat:
58.31737
lon:
8.521398
Open the place page for this point
id:
NSR:StopPlace:27865
name:
Tjørn
label:
Tjørn, Bjerkreim
category:
1 results
1. onstreetBus
municipality:
Bjerkreim
county:
Rogaland
lat:
58.592784
lon:
6.168338

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.