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-04T19:13:54Z in 0.163 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:3953
name:
Langton
label:
Langton, Hurdal
category:
1 results
1. onstreetBus
municipality:
Hurdal
county:
Akershus
lat:
60.340448
lon:
11.093026
Open the place page for this point
id:
NSR:StopPlace:13903
name:
Langmoen
label:
Langmoen, Lillehammer
category:
1 results
1. onstreetBus
municipality:
Lillehammer
county:
Innlandet
lat:
61.152904
lon:
10.380602
Open the place page for this point
id:
NSR:StopPlace:57864
name:
Langmoen
label:
Langmoen, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.156878
lon:
19.177153
Open the place page for this point
id:
NSR:StopPlace:9685
name:
Langmoen
label:
Langmoen, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.886334
lon:
10.935509
Open the place page for this point
id:
NSR:StopPlace:42720
name:
Langlo
label:
Langlo, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.367252
lon:
10.111483
Open the place page for this point
id:
NSR:StopPlace:47516
name:
Langmo
label:
Langmo, Vefsn
category:
1 results
1. onstreetBus
municipality:
Vefsn
county:
Nordland
lat:
65.912827
lon:
13.294319
Open the place page for this point
id:
NSR:StopPlace:39128
name:
Langøy
label:
Langøy, Averøy
category:
1 results
1. onstreetBus
municipality:
Averøy
county:
Møre og Romsdal
lat:
63.063648
lon:
7.497077
Open the place page for this point
id:
NSR:StopPlace:42706
name:
Langen
label:
Langen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.600474
lon:
11.674492
Open the place page for this point
id:
NSR:StopPlace:39086
name:
Langlo
label:
Langlo, Stranda
category:
1 results
1. onstreetBus
municipality:
Stranda
county:
Møre og Romsdal
lat:
62.308605
lon:
6.907572
Open the place page for this point
id:
NSR:StopPlace:42709
name:
Langen
label:
Langen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.434091
lon:
11.850456
Open the place page for this point
id:
NSR:StopPlace:16203
name:
Lauton
label:
Lauton, Asker
category:
1 results
1. onstreetBus
municipality:
Asker
county:
Akershus
lat:
59.7179
lon:
10.3182
Open the place page for this point
id:
NSR:StopPlace:35666
name:
Langø
label:
Langø, Stad
category:
1 results
1. onstreetBus
municipality:
Stad
county:
Vestland
lat:
61.937313
lon:
5.857541

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:3953
name:
Langton
label:
Langton, Hurdal
category:
1 results
1. onstreetBus
municipality:
Hurdal
county:
Akershus
lat:
60.340448
lon:
11.093026
Open the place page for this point
id:
NSR:StopPlace:13903
name:
Langmoen
label:
Langmoen, Lillehammer
category:
1 results
1. onstreetBus
municipality:
Lillehammer
county:
Innlandet
lat:
61.152904
lon:
10.380602
Open the place page for this point
id:
NSR:StopPlace:57864
name:
Langmoen
label:
Langmoen, Balsfjord
category:
1 results
1. onstreetBus
municipality:
Balsfjord
county:
Troms
lat:
69.156878
lon:
19.177153
Open the place page for this point
id:
NSR:StopPlace:9685
name:
Langmoen
label:
Langmoen, Ringsaker
category:
1 results
1. onstreetBus
municipality:
Ringsaker
county:
Innlandet
lat:
60.886334
lon:
10.935509
Open the place page for this point
id:
NSR:StopPlace:42720
name:
Langlo
label:
Langlo, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.367252
lon:
10.111483
Open the place page for this point
id:
NSR:StopPlace:47516
name:
Langmo
label:
Langmo, Vefsn
category:
1 results
1. onstreetBus
municipality:
Vefsn
county:
Nordland
lat:
65.912827
lon:
13.294319
Open the place page for this point
id:
NSR:StopPlace:39128
name:
Langøy
label:
Langøy, Averøy
category:
1 results
1. onstreetBus
municipality:
Averøy
county:
Møre og Romsdal
lat:
63.063648
lon:
7.497077
Open the place page for this point
id:
NSR:StopPlace:42706
name:
Langen
label:
Langen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.600474
lon:
11.674492
Open the place page for this point
id:
NSR:StopPlace:39086
name:
Langlo
label:
Langlo, Stranda
category:
1 results
1. onstreetBus
municipality:
Stranda
county:
Møre og Romsdal
lat:
62.308605
lon:
6.907572
Open the place page for this point
id:
NSR:StopPlace:42709
name:
Langen
label:
Langen, Røros
category:
1 results
1. onstreetBus
municipality:
Røros
county:
Trøndelag
lat:
62.434091
lon:
11.850456
Open the place page for this point
id:
NSR:StopPlace:16203
name:
Lauton
label:
Lauton, Asker
category:
1 results
1. onstreetBus
municipality:
Asker
county:
Akershus
lat:
59.7179
lon:
10.3182
Open the place page for this point
id:
NSR:StopPlace:35666
name:
Langø
label:
Langø, Stad
category:
1 results
1. onstreetBus
municipality:
Stad
county:
Vestland
lat:
61.937313
lon:
5.857541

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.