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-20T17:14:41Z in 0.124 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:22275
name:
Lølandsmo
label:
Lølandsmo, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.18822
lon:
7.346811
Open the place page for this point
id:
NSR:StopPlace:36686
name:
Løland indre
label:
Løland indre, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156662
lon:
5.404142
Open the place page for this point
id:
NSR:StopPlace:23914
name:
Løland
label:
Løland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.17512
lon:
7.34705
Open the place page for this point
id:
NSR:StopPlace:23733
name:
Loland
label:
Loland, Vennesla
category:
1 results
1. onstreetBus
municipality:
Vennesla
county:
Agder
lat:
58.285958
lon:
7.87693
Open the place page for this point
id:
NSR:StopPlace:23907
name:
Løland
label:
Løland, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.467649
lon:
8.272235
Open the place page for this point
id:
NSR:StopPlace:23912
name:
Løland
label:
Løland, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.392419
lon:
6.724309
Open the place page for this point
id:
NSR:StopPlace:27388
name:
Løland
label:
Løland, Suldal
category:
1 results
1. onstreetBus
municipality:
Suldal
county:
Rogaland
lat:
59.548528
lon:
6.337615
Open the place page for this point
id:
NSR:StopPlace:36683
name:
Løland
label:
Løland, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156277
lon:
5.398364
Open the place page for this point
id:
NSR:StopPlace:36690
name:
Løland bru
label:
Løland bru, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156281
lon:
5.376947
Open the place page for this point
id:
NSR:StopPlace:36688
name:
Løland ytre
label:
Løland ytre, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.158345
lon:
5.388986
Open the place page for this point
id:
NSR:StopPlace:23909
name:
Løland
label:
Løland, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.486079
lon:
8.12341
Open the place page for this point
id:
NSR:StopPlace:23917
name:
Løland bru
label:
Løland bru, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.170576
lon:
7.359575

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:22275
name:
Lølandsmo
label:
Lølandsmo, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.18822
lon:
7.346811
Open the place page for this point
id:
NSR:StopPlace:36686
name:
Løland indre
label:
Løland indre, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156662
lon:
5.404142
Open the place page for this point
id:
NSR:StopPlace:23914
name:
Løland
label:
Løland, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.17512
lon:
7.34705
Open the place page for this point
id:
NSR:StopPlace:23733
name:
Loland
label:
Loland, Vennesla
category:
1 results
1. onstreetBus
municipality:
Vennesla
county:
Agder
lat:
58.285958
lon:
7.87693
Open the place page for this point
id:
NSR:StopPlace:23907
name:
Løland
label:
Løland, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.467649
lon:
8.272235
Open the place page for this point
id:
NSR:StopPlace:23912
name:
Løland
label:
Løland, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.392419
lon:
6.724309
Open the place page for this point
id:
NSR:StopPlace:27388
name:
Løland
label:
Løland, Suldal
category:
1 results
1. onstreetBus
municipality:
Suldal
county:
Rogaland
lat:
59.548528
lon:
6.337615
Open the place page for this point
id:
NSR:StopPlace:36683
name:
Løland
label:
Løland, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156277
lon:
5.398364
Open the place page for this point
id:
NSR:StopPlace:36690
name:
Løland bru
label:
Løland bru, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.156281
lon:
5.376947
Open the place page for this point
id:
NSR:StopPlace:36688
name:
Løland ytre
label:
Løland ytre, Hyllestad
category:
1 results
1. onstreetBus
municipality:
Hyllestad
county:
Vestland
lat:
61.158345
lon:
5.388986
Open the place page for this point
id:
NSR:StopPlace:23909
name:
Løland
label:
Løland, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.486079
lon:
8.12341
Open the place page for this point
id:
NSR:StopPlace:23917
name:
Løland bru
label:
Løland bru, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.170576
lon:
7.359575

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.