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-10-07T15:57:20Z in 0.130 seconds.

returned:
11
stops:

11 results

  1. id:
    NSR:StopPlace:15917
    name:
    Øynan
    label:
    Øynan, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.50557
    lon:
    8.002425
  2. id:
    NSR:StopPlace:42558
    name:
    Øyan
    label:
    Øyan, Indre Fosen
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Fosen
    county:
    Trøndelag
    lat:
    63.754515
    lon:
    10.237134
  3. id:
    NSR:StopPlace:63082
    name:
    Øyna
    label:
    Øyna, Vindafjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Vindafjord
    county:
    Rogaland
    lat:
    59.532373
    lon:
    5.538566
  4. id:
    NSR:StopPlace:42562
    name:
    Øyan
    label:
    Øyan, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    63.917641
    lon:
    9.994527
  5. id:
    NSR:StopPlace:42564
    name:
    Øyan
    label:
    Øyan, Midtre Gauldal
    category:

    1 results

    1. onstreetBus
    municipality:
    Midtre Gauldal
    county:
    Trøndelag
    lat:
    62.966373
    lon:
    10.578646
  6. id:
    NSR:StopPlace:59968
    name:
    Øyna
    label:
    Øyna, Etne
    category:

    1 results

    1. onstreetBus
    municipality:
    Etne
    county:
    Vestland
    lat:
    59.752342
    lon:
    6.203531
  7. id:
    NSR:StopPlace:45284
    name:
    Øyan
    label:
    Øyan, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.768476
    lon:
    11.558261
  8. id:
    NSR:StopPlace:60625
    name:
    Øyan
    label:
    Øyan, Meråker
    category:

    1 results

    1. onstreetBus
    municipality:
    Meråker
    county:
    Trøndelag
    lat:
    63.371777
    lon:
    11.813964
  9. id:
    NSR:StopPlace:37460
    name:
    Øyna
    label:
    Øyna, Sunnfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunnfjord
    county:
    Vestland
    lat:
    61.358157
    lon:
    6.199823
  10. id:
    NSR:StopPlace:60986
    name:
    Øyna
    label:
    Øyna, Iveland
    category:

    1 results

    1. onstreetBus
    municipality:
    Iveland
    county:
    Agder
    lat:
    58.413986
    lon:
    7.837107
  11. id:
    NSR:StopPlace:64367
    name:
    Øyan
    label:
    Øyan, Melhus
    category:

    1 results

    1. onstreetBus
    municipality:
    Melhus
    county:
    Trøndelag
    lat:
    63.312831
    lon:
    10.274379
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
11
stops:

11 results

  1. id:
    NSR:StopPlace:15917
    name:
    Øynan
    label:
    Øynan, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.50557
    lon:
    8.002425
  2. id:
    NSR:StopPlace:42558
    name:
    Øyan
    label:
    Øyan, Indre Fosen
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Fosen
    county:
    Trøndelag
    lat:
    63.754515
    lon:
    10.237134
  3. id:
    NSR:StopPlace:63082
    name:
    Øyna
    label:
    Øyna, Vindafjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Vindafjord
    county:
    Rogaland
    lat:
    59.532373
    lon:
    5.538566
  4. id:
    NSR:StopPlace:42562
    name:
    Øyan
    label:
    Øyan, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    63.917641
    lon:
    9.994527
  5. id:
    NSR:StopPlace:42564
    name:
    Øyan
    label:
    Øyan, Midtre Gauldal
    category:

    1 results

    1. onstreetBus
    municipality:
    Midtre Gauldal
    county:
    Trøndelag
    lat:
    62.966373
    lon:
    10.578646
  6. id:
    NSR:StopPlace:59968
    name:
    Øyna
    label:
    Øyna, Etne
    category:

    1 results

    1. onstreetBus
    municipality:
    Etne
    county:
    Vestland
    lat:
    59.752342
    lon:
    6.203531
  7. id:
    NSR:StopPlace:45284
    name:
    Øyan
    label:
    Øyan, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.768476
    lon:
    11.558261
  8. id:
    NSR:StopPlace:60625
    name:
    Øyan
    label:
    Øyan, Meråker
    category:

    1 results

    1. onstreetBus
    municipality:
    Meråker
    county:
    Trøndelag
    lat:
    63.371777
    lon:
    11.813964
  9. id:
    NSR:StopPlace:37460
    name:
    Øyna
    label:
    Øyna, Sunnfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunnfjord
    county:
    Vestland
    lat:
    61.358157
    lon:
    6.199823
  10. id:
    NSR:StopPlace:60986
    name:
    Øyna
    label:
    Øyna, Iveland
    category:

    1 results

    1. onstreetBus
    municipality:
    Iveland
    county:
    Agder
    lat:
    58.413986
    lon:
    7.837107
  11. id:
    NSR:StopPlace:64367
    name:
    Øyan
    label:
    Øyan, Melhus
    category:

    1 results

    1. onstreetBus
    municipality:
    Melhus
    county:
    Trøndelag
    lat:
    63.312831
    lon:
    10.274379
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.