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-29T22:53:29Z in 0.134 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:39369
name:
Linge
label:
Linge, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.289906
lon:
7.226806
Open the place page for this point
id:
NSR:StopPlace:46336
name:
Lingen
label:
Lingen, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.297867
lon:
11.208388
Open the place page for this point
id:
NSR:StopPlace:58657
name:
Linge ferjekai
label:
Linge ferjekai, Fjord
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.284376
lon:
7.187532
Open the place page for this point
id:
NSR:StopPlace:39374
name:
Linge ytre
label:
Linge ytre, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.286934
lon:
7.211703
Open the place page for this point
id:
NSR:StopPlace:33033
name:
Linga
label:
Linga, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.259225
lon:
6.074265
Open the place page for this point
id:
NSR:StopPlace:36225
name:
Lynge
label:
Lynge, Fjaler
category:
1 results
1. onstreetBus
municipality:
Fjaler
county:
Vestland
lat:
61.326735
lon:
5.407676
Open the place page for this point
id:
NSR:StopPlace:39072
name:
Lange
label:
Lange, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.715252
lon:
7.928917
Open the place page for this point
id:
NSR:StopPlace:27695
name:
Kompani Linges vei
label:
Kompani Linges vei, Stavanger
category:
1 results
1. onstreetBus
municipality:
Stavanger
county:
Rogaland
lat:
58.943919
lon:
5.665697
Open the place page for this point
id:
NSR:StopPlace:19450
name:
Brekke Lingelemveien
label:
Brekke Lingelemveien, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.172228
lon:
10.227541
Open the place page for this point
id:
NSR:StopPlace:42458
name:
Martin Linges veg
label:
Martin Linges veg, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.359636
lon:
10.368409
Open the place page for this point
id:
NSR:StopPlace:5872
name:
Martin Linges vei
label:
Martin Linges vei, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.880368
lon:
10.839845
Open the place page for this point
id:
NSR:StopPlace:19246
name:
Bergan Lingelemveien
label:
Bergan Lingelemveien, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.177201
lon:
10.234438

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:39369
name:
Linge
label:
Linge, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.289906
lon:
7.226806
Open the place page for this point
id:
NSR:StopPlace:46336
name:
Lingen
label:
Lingen, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.297867
lon:
11.208388
Open the place page for this point
id:
NSR:StopPlace:58657
name:
Linge ferjekai
label:
Linge ferjekai, Fjord
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.284376
lon:
7.187532
Open the place page for this point
id:
NSR:StopPlace:39374
name:
Linge ytre
label:
Linge ytre, Fjord
category:
1 results
1. onstreetBus
municipality:
Fjord
county:
Møre og Romsdal
lat:
62.286934
lon:
7.211703
Open the place page for this point
id:
NSR:StopPlace:33033
name:
Linga
label:
Linga, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.259225
lon:
6.074265
Open the place page for this point
id:
NSR:StopPlace:36225
name:
Lynge
label:
Lynge, Fjaler
category:
1 results
1. onstreetBus
municipality:
Fjaler
county:
Vestland
lat:
61.326735
lon:
5.407676
Open the place page for this point
id:
NSR:StopPlace:39072
name:
Lange
label:
Lange, Molde
category:
1 results
1. onstreetBus
municipality:
Molde
county:
Møre og Romsdal
lat:
62.715252
lon:
7.928917
Open the place page for this point
id:
NSR:StopPlace:27695
name:
Kompani Linges vei
label:
Kompani Linges vei, Stavanger
category:
1 results
1. onstreetBus
municipality:
Stavanger
county:
Rogaland
lat:
58.943919
lon:
5.665697
Open the place page for this point
id:
NSR:StopPlace:19450
name:
Brekke Lingelemveien
label:
Brekke Lingelemveien, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.172228
lon:
10.227541
Open the place page for this point
id:
NSR:StopPlace:42458
name:
Martin Linges veg
label:
Martin Linges veg, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.359636
lon:
10.368409
Open the place page for this point
id:
NSR:StopPlace:5872
name:
Martin Linges vei
label:
Martin Linges vei, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.880368
lon:
10.839845
Open the place page for this point
id:
NSR:StopPlace:19246
name:
Bergan Lingelemveien
label:
Bergan Lingelemveien, Sandefjord
category:
1 results
1. onstreetBus
municipality:
Sandefjord
county:
Vestfold
lat:
59.177201
lon:
10.234438

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.