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-06T21:44:56Z in 0.165 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:29564
name:
Nordtun
label:
Nordtun, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.769426
lon:
5.125651
Open the place page for this point
id:
NSR:StopPlace:60545
name:
Nordtun
label:
Nordtun, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.756061
lon:
11.387828
Open the place page for this point
id:
NSR:StopPlace:44910
name:
Nordtun
label:
Nordtun, Overhalla
category:
1 results
1. onstreetBus
municipality:
Overhalla
county:
Trøndelag
lat:
64.530676
lon:
12.130929
Open the place page for this point
id:
NSR:StopPlace:35206
name:
Nortun
label:
Nortun, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.160766
lon:
6.979437
Open the place page for this point
id:
NSR:StopPlace:70097
name:
Nordhus
label:
Nordhus, Sørreisa
category:
1 results
1. onstreetBus
municipality:
Sørreisa
county:
Troms
lat:
69.092955
lon:
18.340168
Open the place page for this point
id:
NSR:StopPlace:13455
name:
Nordrum
label:
Nordrum, Ringebu
category:
1 results
1. onstreetBus
municipality:
Ringebu
county:
Innlandet
lat:
61.550528
lon:
10.09054
Open the place page for this point
id:
NSR:StopPlace:56353
name:
Nordlund
label:
Nordlund, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.218884
lon:
18.682245
Open the place page for this point
id:
NSR:StopPlace:7767
name:
Nordhus
label:
Nordhus, Alvdal
category:
1 results
1. onstreetBus
municipality:
Alvdal
county:
Innlandet
lat:
62.097516
lon:
10.653823
Open the place page for this point
id:
NSR:StopPlace:56350
name:
Nordlund
label:
Nordlund, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.521887
lon:
16.69979
Open the place page for this point
id:
NSR:StopPlace:43152
name:
Nordaune
label:
Nordaune, Holtålen
category:
1 results
1. onstreetBus
municipality:
Holtålen
county:
Trøndelag
lat:
62.954684
lon:
11.248337
Open the place page for this point
id:
NSR:StopPlace:27442
name:
NorDan
label:
NorDan, Lund
category:
1 results
1. onstreetBus
municipality:
Lund
county:
Rogaland
lat:
58.460134
lon:
6.544113
Open the place page for this point
id:
NSR:StopPlace:40910
name:
Nordbu
label:
Nordbu, Rindal
category:
1 results
1. onstreetBus
municipality:
Rindal
county:
Trøndelag
lat:
63.050909
lon:
9.172659

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:29564
name:
Nordtun
label:
Nordtun, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.769426
lon:
5.125651
Open the place page for this point
id:
NSR:StopPlace:60545
name:
Nordtun
label:
Nordtun, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.756061
lon:
11.387828
Open the place page for this point
id:
NSR:StopPlace:44910
name:
Nordtun
label:
Nordtun, Overhalla
category:
1 results
1. onstreetBus
municipality:
Overhalla
county:
Trøndelag
lat:
64.530676
lon:
12.130929
Open the place page for this point
id:
NSR:StopPlace:35206
name:
Nortun
label:
Nortun, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.160766
lon:
6.979437
Open the place page for this point
id:
NSR:StopPlace:70097
name:
Nordhus
label:
Nordhus, Sørreisa
category:
1 results
1. onstreetBus
municipality:
Sørreisa
county:
Troms
lat:
69.092955
lon:
18.340168
Open the place page for this point
id:
NSR:StopPlace:13455
name:
Nordrum
label:
Nordrum, Ringebu
category:
1 results
1. onstreetBus
municipality:
Ringebu
county:
Innlandet
lat:
61.550528
lon:
10.09054
Open the place page for this point
id:
NSR:StopPlace:56353
name:
Nordlund
label:
Nordlund, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.218884
lon:
18.682245
Open the place page for this point
id:
NSR:StopPlace:7767
name:
Nordhus
label:
Nordhus, Alvdal
category:
1 results
1. onstreetBus
municipality:
Alvdal
county:
Innlandet
lat:
62.097516
lon:
10.653823
Open the place page for this point
id:
NSR:StopPlace:56350
name:
Nordlund
label:
Nordlund, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.521887
lon:
16.69979
Open the place page for this point
id:
NSR:StopPlace:43152
name:
Nordaune
label:
Nordaune, Holtålen
category:
1 results
1. onstreetBus
municipality:
Holtålen
county:
Trøndelag
lat:
62.954684
lon:
11.248337
Open the place page for this point
id:
NSR:StopPlace:27442
name:
NorDan
label:
NorDan, Lund
category:
1 results
1. onstreetBus
municipality:
Lund
county:
Rogaland
lat:
58.460134
lon:
6.544113
Open the place page for this point
id:
NSR:StopPlace:40910
name:
Nordbu
label:
Nordbu, Rindal
category:
1 results
1. onstreetBus
municipality:
Rindal
county:
Trøndelag
lat:
63.050909
lon:
9.172659

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.