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.

ParameterRequirementJSON typeDescription
queryrequiredstringStop name or place, e.g. "Oslo S".
limitoptionalintegerMaximum hits, 1-100. Unit: items.
langoptionalstringResult language, normally "no" or "en".
offsetoptionalintegerNumber 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.

Type: string. Stop name or place, e.g. "Oslo S".
Type: integer. Maximum hits, 1-100. Unit: items.
Type: string. Result language, normally "no" or "en".

Result

Source: Entur. Retrieved 2026-09-23T02:53:17Z in 0.130 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:14266
    name:
    Rindal
    label:
    Rindal, Dovre
    category:

    1 results

    1. onstreetBus
    municipality:
    Dovre
    county:
    Innlandet
    lat:
    61.936732
    lon:
    9.320794
  2. id:
    NSR:StopPlace:41504
    name:
    Ringdal
    label:
    Ringdal, Stranda
    category:

    1 results

    1. onstreetBus
    municipality:
    Stranda
    county:
    Møre og Romsdal
    lat:
    62.089214
    lon:
    6.854874
  3. id:
    NSR:StopPlace:17498
    name:
    Ringdal
    label:
    Ringdal, Larvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Larvik
    county:
    Vestfold
    lat:
    59.110837
    lon:
    10.120079
  4. id:
    NSR:StopPlace:12572
    name:
    Rindal
    label:
    Rindal, Øyer
    category:

    1 results

    1. onstreetBus
    municipality:
    Øyer
    county:
    Innlandet
    lat:
    61.288077
    lon:
    10.338929
  5. id:
    NSR:StopPlace:41497
    name:
    Rindal
    label:
    Rindal
    category:

    1 results

    1. onstreetBus
    municipality:
    Rindal
    county:
    Trøndelag
    lat:
    63.055154
    lon:
    9.211529
  6. id:
    NSR:StopPlace:35584
    name:
    Rivedal
    label:
    Rivedal, Askvoll
    category:

    1 results

    1. onstreetBus
    municipality:
    Askvoll
    county:
    Vestland
    lat:
    61.363568
    lon:
    5.259873
  7. id:
    NSR:StopPlace:41728
    name:
    Ringvål
    label:
    Ringvål, Trondheim
    category:

    1 results

    1. onstreetBus
    municipality:
    Trondheim
    county:
    Trøndelag
    lat:
    63.351979
    lon:
    10.249703
  8. id:
    NSR:StopPlace:21796
    name:
    Risdal
    label:
    Risdal, Froland
    category:

    1 results

    1. onstreetBus
    municipality:
    Froland
    county:
    Agder
    lat:
    58.670201
    lon:
    8.129971
  9. id:
    NSR:StopPlace:25828
    name:
    Risdal
    label:
    Risdal, Karmøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Karmøy
    county:
    Rogaland
    lat:
    59.161742
    lon:
    5.231195
  10. id:
    NSR:StopPlace:11085
    name:
    Risdal
    label:
    Risdal, Nord-Fron
    category:

    1 results

    1. onstreetBus
    municipality:
    Nord-Fron
    county:
    Innlandet
    lat:
    61.53605
    lon:
    9.43087
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:14266
    name:
    Rindal
    label:
    Rindal, Dovre
    category:

    1 results

    1. onstreetBus
    municipality:
    Dovre
    county:
    Innlandet
    lat:
    61.936732
    lon:
    9.320794
  2. id:
    NSR:StopPlace:41504
    name:
    Ringdal
    label:
    Ringdal, Stranda
    category:

    1 results

    1. onstreetBus
    municipality:
    Stranda
    county:
    Møre og Romsdal
    lat:
    62.089214
    lon:
    6.854874
  3. id:
    NSR:StopPlace:17498
    name:
    Ringdal
    label:
    Ringdal, Larvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Larvik
    county:
    Vestfold
    lat:
    59.110837
    lon:
    10.120079
  4. id:
    NSR:StopPlace:12572
    name:
    Rindal
    label:
    Rindal, Øyer
    category:

    1 results

    1. onstreetBus
    municipality:
    Øyer
    county:
    Innlandet
    lat:
    61.288077
    lon:
    10.338929
  5. id:
    NSR:StopPlace:41497
    name:
    Rindal
    label:
    Rindal
    category:

    1 results

    1. onstreetBus
    municipality:
    Rindal
    county:
    Trøndelag
    lat:
    63.055154
    lon:
    9.211529
  6. id:
    NSR:StopPlace:35584
    name:
    Rivedal
    label:
    Rivedal, Askvoll
    category:

    1 results

    1. onstreetBus
    municipality:
    Askvoll
    county:
    Vestland
    lat:
    61.363568
    lon:
    5.259873
  7. id:
    NSR:StopPlace:41728
    name:
    Ringvål
    label:
    Ringvål, Trondheim
    category:

    1 results

    1. onstreetBus
    municipality:
    Trondheim
    county:
    Trøndelag
    lat:
    63.351979
    lon:
    10.249703
  8. id:
    NSR:StopPlace:21796
    name:
    Risdal
    label:
    Risdal, Froland
    category:

    1 results

    1. onstreetBus
    municipality:
    Froland
    county:
    Agder
    lat:
    58.670201
    lon:
    8.129971
  9. id:
    NSR:StopPlace:25828
    name:
    Risdal
    label:
    Risdal, Karmøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Karmøy
    county:
    Rogaland
    lat:
    59.161742
    lon:
    5.231195
  10. id:
    NSR:StopPlace:11085
    name:
    Risdal
    label:
    Risdal, Nord-Fron
    category:

    1 results

    1. onstreetBus
    municipality:
    Nord-Fron
    county:
    Innlandet
    lat:
    61.53605
    lon:
    9.43087
limit:
25
offset:
0
has_more_results:
no
truncated:
no
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

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. 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

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.