search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
`lang`	optional	string	Result language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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-11-13T03:47:27Z in 0.000 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:8578
name:
Antona
label:
Antona, Sør-Odal
category:
1 results
1. onstreetBus
municipality:
Sør-Odal
county:
Innlandet
lat:
60.217389
lon:
11.637273
Open the place page for this point
id:
NSR:StopPlace:55245
name:
Anton Silsands vei
label:
Anton Silsands vei, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.239598
lon:
17.931145
Open the place page for this point
id:
NSR:StopPlace:5932
name:
Anton Tschudis vei
label:
Anton Tschudis vei, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.935423
lon:
10.815466
Open the place page for this point
id:
NSR:StopPlace:43488
name:
Anton Grevskotts veg
label:
Anton Grevskotts veg, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.403682
lon:
10.405697
Open the place page for this point
id:
NSR:StopPlace:28121
name:
Anton Brøggers gate
label:
Anton Brøggers gate, Stavanger
category:
1 results
1. onstreetBus
municipality:
Stavanger
county:
Rogaland
lat:
58.943202
lon:
5.686278
Open the place page for this point
id:
NSR:StopPlace:3988
name:
Anton Walles vei
label:
Anton Walles vei, Bærum
category:
1 results
1. onstreetBus
municipality:
Bærum
county:
Akershus
lat:
59.892698
lon:
10.531144
Open the place page for this point
id:
NSR:StopPlace:70279
name:
Antonbakken
label:
Antonbakken, Salangen
category:
1 results
1. onstreetBus
municipality:
Salangen
county:
Troms
lat:
68.892333
lon:
17.802785
Open the place page for this point
id:
NSR:StopPlace:24619
name:
Antonskleiva
label:
Antonskleiva, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.535816
lon:
8.803562
Open the place page for this point
id:
NSR:StopPlace:8576
name:
Antona nord
label:
Antona nord, Sør-Odal
category:
1 results
1. onstreetBus
municipality:
Sør-Odal
county:
Innlandet
lat:
60.219682
lon:
11.645255
Open the place page for this point
id:
NSR:StopPlace:64141
name:
St. Anton am Arlberg Terminal Ost
label:
St. Anton am Arlberg Terminal Ost
category:
1 results
1. onstreetBus
municipality:
not reported by source
county:
not reported by source
lat:
47.135131
lon:
10.274902
Open the place page for this point
id:
NSR:StopPlace:40418
name:
Aston
label:
Aston, Rauma
category:
1 results
1. onstreetBus
municipality:
Rauma
county:
Møre og Romsdal
lat:
62.57982
lon:
7.824652

Show all fields in HTML

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:8578
name:
Antona
label:
Antona, Sør-Odal
category:
1 results
1. onstreetBus
municipality:
Sør-Odal
county:
Innlandet
lat:
60.217389
lon:
11.637273
Open the place page for this point
id:
NSR:StopPlace:55245
name:
Anton Silsands vei
label:
Anton Silsands vei, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.239598
lon:
17.931145
Open the place page for this point
id:
NSR:StopPlace:5932
name:
Anton Tschudis vei
label:
Anton Tschudis vei, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.935423
lon:
10.815466
Open the place page for this point
id:
NSR:StopPlace:43488
name:
Anton Grevskotts veg
label:
Anton Grevskotts veg, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.403682
lon:
10.405697
Open the place page for this point
id:
NSR:StopPlace:28121
name:
Anton Brøggers gate
label:
Anton Brøggers gate, Stavanger
category:
1 results
1. onstreetBus
municipality:
Stavanger
county:
Rogaland
lat:
58.943202
lon:
5.686278
Open the place page for this point
id:
NSR:StopPlace:3988
name:
Anton Walles vei
label:
Anton Walles vei, Bærum
category:
1 results
1. onstreetBus
municipality:
Bærum
county:
Akershus
lat:
59.892698
lon:
10.531144
Open the place page for this point
id:
NSR:StopPlace:70279
name:
Antonbakken
label:
Antonbakken, Salangen
category:
1 results
1. onstreetBus
municipality:
Salangen
county:
Troms
lat:
68.892333
lon:
17.802785
Open the place page for this point
id:
NSR:StopPlace:24619
name:
Antonskleiva
label:
Antonskleiva, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.535816
lon:
8.803562
Open the place page for this point
id:
NSR:StopPlace:8576
name:
Antona nord
label:
Antona nord, Sør-Odal
category:
1 results
1. onstreetBus
municipality:
Sør-Odal
county:
Innlandet
lat:
60.219682
lon:
11.645255
Open the place page for this point
id:
NSR:StopPlace:64141
name:
St. Anton am Arlberg Terminal Ost
label:
St. Anton am Arlberg Terminal Ost
category:
1 results
1. onstreetBus
municipality:
not reported by source
county:
not reported by source
lat:
47.135131
lon:
10.274902
Open the place page for this point
id:
NSR:StopPlace:40418
name:
Aston
label:
Aston, Rauma
category:
1 results
1. onstreetBus
municipality:
Rauma
county:
Møre og Romsdal
lat:
62.57982
lon:
7.824652

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.