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-03T10:05:10Z in 0.644 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:28954
name:
Lyssand
label:
Lyssand, Bjørnafjorden
category:
1 results
1. onstreetBus
municipality:
Bjørnafjorden
county:
Vestland
lat:
60.195024
lon:
5.483988
Open the place page for this point
id:
NSR:StopPlace:3852
name:
Lysgård
label:
Lysgård, Hurdal
category:
1 results
1. onstreetBus
municipality:
Hurdal
county:
Akershus
lat:
60.480582
lon:
11.017964
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:11638
name:
Lysgard
label:
Lysgard, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.789907
lon:
9.457667
Open the place page for this point
id:
NSR:StopPlace:4260
name:
Lystad
label:
Lystad, Lillestrøm
category:
1 results
1. onstreetBus
municipality:
Lillestrøm
county:
Akershus
lat:
59.968042
lon:
11.218441
Open the place page for this point
id:
NSR:StopPlace:4999
name:
Lystad
label:
Lystad, Ullensaker
category:
1 results
1. onstreetBus
municipality:
Ullensaker
county:
Akershus
lat:
60.106592
lon:
11.138817
Open the place page for this point
id:
NSR:StopPlace:23872
name:
Lysgård
label:
Lysgård, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.144531
lon:
7.847343
Open the place page for this point
id:
NSR:StopPlace:1740
name:
Lystad
label:
Lystad, Skiptvet
category:
1 results
1. onstreetBus
municipality:
Skiptvet
county:
Østfold
lat:
59.448578
lon:
11.128367
Open the place page for this point
id:
NSR:StopPlace:54687
name:
Lystad
label:
Lystad, Bardu
category:
1 results
1. onstreetBus
municipality:
Bardu
county:
Troms
lat:
68.993676
lon:
18.528735
Open the place page for this point
id:
NSR:StopPlace:3754
name:
Lystad
label:
Lystad, Nannestad
category:
1 results
1. onstreetBus
municipality:
Nannestad
county:
Akershus
lat:
60.249055
lon:
11.030209
Open the place page for this point
id:
NSR:StopPlace:39452
name:
Lystad
label:
Lystad, Ørsta
category:
1 results
1. onstreetBus
municipality:
Ørsta
county:
Møre og Romsdal
lat:
62.215246
lon:
6.019404
Open the place page for this point
id:
NSR:StopPlace:39455
name:
Lystad
label:
Lystad, Aure
category:
1 results
1. onstreetBus
municipality:
Aure
county:
Møre og Romsdal
lat:
63.147034
lon:
8.028419

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:28954
name:
Lyssand
label:
Lyssand, Bjørnafjorden
category:
1 results
1. onstreetBus
municipality:
Bjørnafjorden
county:
Vestland
lat:
60.195024
lon:
5.483988
Open the place page for this point
id:
NSR:StopPlace:3852
name:
Lysgård
label:
Lysgård, Hurdal
category:
1 results
1. onstreetBus
municipality:
Hurdal
county:
Akershus
lat:
60.480582
lon:
11.017964
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:11638
name:
Lysgard
label:
Lysgard, Sel
category:
1 results
1. onstreetBus
municipality:
Sel
county:
Innlandet
lat:
61.789907
lon:
9.457667
Open the place page for this point
id:
NSR:StopPlace:4260
name:
Lystad
label:
Lystad, Lillestrøm
category:
1 results
1. onstreetBus
municipality:
Lillestrøm
county:
Akershus
lat:
59.968042
lon:
11.218441
Open the place page for this point
id:
NSR:StopPlace:4999
name:
Lystad
label:
Lystad, Ullensaker
category:
1 results
1. onstreetBus
municipality:
Ullensaker
county:
Akershus
lat:
60.106592
lon:
11.138817
Open the place page for this point
id:
NSR:StopPlace:23872
name:
Lysgård
label:
Lysgård, Kristiansand
category:
1 results
1. onstreetBus
municipality:
Kristiansand
county:
Agder
lat:
58.144531
lon:
7.847343
Open the place page for this point
id:
NSR:StopPlace:1740
name:
Lystad
label:
Lystad, Skiptvet
category:
1 results
1. onstreetBus
municipality:
Skiptvet
county:
Østfold
lat:
59.448578
lon:
11.128367
Open the place page for this point
id:
NSR:StopPlace:54687
name:
Lystad
label:
Lystad, Bardu
category:
1 results
1. onstreetBus
municipality:
Bardu
county:
Troms
lat:
68.993676
lon:
18.528735
Open the place page for this point
id:
NSR:StopPlace:3754
name:
Lystad
label:
Lystad, Nannestad
category:
1 results
1. onstreetBus
municipality:
Nannestad
county:
Akershus
lat:
60.249055
lon:
11.030209
Open the place page for this point
id:
NSR:StopPlace:39452
name:
Lystad
label:
Lystad, Ørsta
category:
1 results
1. onstreetBus
municipality:
Ørsta
county:
Møre og Romsdal
lat:
62.215246
lon:
6.019404
Open the place page for this point
id:
NSR:StopPlace:39455
name:
Lystad
label:
Lystad, Aure
category:
1 results
1. onstreetBus
municipality:
Aure
county:
Møre og Romsdal
lat:
63.147034
lon:
8.028419

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.