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-13T18:21:46Z in 0.138 seconds.

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:11767
name:
Lyseng
label:
Lyseng, Vestre Slidre
category:
1 results
1. onstreetBus
municipality:
Vestre Slidre
county:
Innlandet
lat:
61.016228
lon:
9.060118
Open the place page for this point
id:
NSR:StopPlace:47200
name:
Løding
label:
Løding, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.307895
lon:
14.734663
Open the place page for this point
id:
NSR:StopPlace:22306
name:
Løyning
label:
Løyning, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.295191
lon:
6.745171
Open the place page for this point
id:
NSR:StopPlace:29314
name:
Lykling
label:
Lykling, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.703949
lon:
5.191025
Open the place page for this point
id:
NSR:StopPlace:27400
name:
Løyning
label:
Løyning, Eigersund
category:
1 results
1. onstreetBus
municipality:
Eigersund
county:
Rogaland
lat:
58.430565
lon:
5.9604
Open the place page for this point
id:
NSR:StopPlace:32075
name:
Løning
label:
Løning, Kvinnherad
category:
1 results
1. onstreetBus
municipality:
Kvinnherad
county:
Vestland
lat:
59.994207
lon:
5.78049
Open the place page for this point
id:
NSR:StopPlace:48049
name:
Lading
label:
Lading, Leirfjord
category:
1 results
1. onstreetBus
municipality:
Leirfjord
county:
Nordland
lat:
66.011851
lon:
12.950282
Open the place page for this point
id:
NSR:StopPlace:48507
name:
Løding
label:
Løding, Hamarøy
category:
1 results
1. onstreetBus
municipality:
Hamarøy
county:
Nordland
lat:
68.078984
lon:
15.495854
Open the place page for this point
id:
NSR:StopPlace:54689
name:
Lysvang
label:
Lysvang, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.407174
lon:
17.843805
Open the place page for this point
id:
NSR:StopPlace:5556
name:
Lysne
label:
Lysne, Frogn
category:
1 results
1. onstreetBus
municipality:
Frogn
county:
Akershus
lat:
59.665877
lon:
10.635624
Open the place page for this point
id:
NSR:StopPlace:45550
name:
Lyng
label:
Lyng, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.777807
lon:
11.582047
Open the place page for this point
id:
NSR:StopPlace:27330
name:
Lyng
label:
Lyng, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.179787
lon:
5.191051
Open the place page for this point
id:
NSR:StopPlace:44699
name:
Lyng
label:
Lyng, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.696406
lon:
10.68632

Show all fields in HTML

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:11767
name:
Lyseng
label:
Lyseng, Vestre Slidre
category:
1 results
1. onstreetBus
municipality:
Vestre Slidre
county:
Innlandet
lat:
61.016228
lon:
9.060118
Open the place page for this point
id:
NSR:StopPlace:47200
name:
Løding
label:
Løding, Bodø
category:
1 results
1. onstreetBus
municipality:
Bodø
county:
Nordland
lat:
67.307895
lon:
14.734663
Open the place page for this point
id:
NSR:StopPlace:22306
name:
Løyning
label:
Løyning, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.295191
lon:
6.745171
Open the place page for this point
id:
NSR:StopPlace:29314
name:
Lykling
label:
Lykling, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.703949
lon:
5.191025
Open the place page for this point
id:
NSR:StopPlace:27400
name:
Løyning
label:
Løyning, Eigersund
category:
1 results
1. onstreetBus
municipality:
Eigersund
county:
Rogaland
lat:
58.430565
lon:
5.9604
Open the place page for this point
id:
NSR:StopPlace:32075
name:
Løning
label:
Løning, Kvinnherad
category:
1 results
1. onstreetBus
municipality:
Kvinnherad
county:
Vestland
lat:
59.994207
lon:
5.78049
Open the place page for this point
id:
NSR:StopPlace:48049
name:
Lading
label:
Lading, Leirfjord
category:
1 results
1. onstreetBus
municipality:
Leirfjord
county:
Nordland
lat:
66.011851
lon:
12.950282
Open the place page for this point
id:
NSR:StopPlace:48507
name:
Løding
label:
Løding, Hamarøy
category:
1 results
1. onstreetBus
municipality:
Hamarøy
county:
Nordland
lat:
68.078984
lon:
15.495854
Open the place page for this point
id:
NSR:StopPlace:54689
name:
Lysvang
label:
Lysvang, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.407174
lon:
17.843805
Open the place page for this point
id:
NSR:StopPlace:5556
name:
Lysne
label:
Lysne, Frogn
category:
1 results
1. onstreetBus
municipality:
Frogn
county:
Akershus
lat:
59.665877
lon:
10.635624
Open the place page for this point
id:
NSR:StopPlace:45550
name:
Lyng
label:
Lyng, Verdal
category:
1 results
1. onstreetBus
municipality:
Verdal
county:
Trøndelag
lat:
63.777807
lon:
11.582047
Open the place page for this point
id:
NSR:StopPlace:27330
name:
Lyng
label:
Lyng, Karmøy
category:
1 results
1. onstreetBus
municipality:
Karmøy
county:
Rogaland
lat:
59.179787
lon:
5.191051
Open the place page for this point
id:
NSR:StopPlace:44699
name:
Lyng
label:
Lyng, Indre Fosen
category:
1 results
1. onstreetBus
municipality:
Indre Fosen
county:
Trøndelag
lat:
63.696406
lon:
10.68632

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.