search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
langoptionalstringResult language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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. Through this API: default 25, maximum 100.
Type: one of: no, nb, nn, en. Result language: "no" (default), "nb", "nn" or "en".

Result

Source: Entur. Retrieved 2026-11-21T01:20:33Z in 0.167 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:23603
    name:
    Storehagen
    label:
    Storehagen, Lindesnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Lindesnes
    county:
    Agder
    lat:
    58.244464
    lon:
    7.512166
  2. id:
    NSR:StopPlace:62637
    name:
    Storhagen
    label:
    Storhagen, Ullensaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ullensaker
    county:
    Akershus
    lat:
    60.133898
    lon:
    11.160685
  3. id:
    NSR:StopPlace:64025
    name:
    Strønevågen
    label:
    Strønevågen, Bjørnafjorden
    category:

    1 results

    1. onstreetBus
    municipality:
    Bjørnafjorden
    county:
    Vestland
    lat:
    60.157899
    lon:
    5.363742
  4. id:
    NSR:StopPlace:32406
    name:
    Storevarden
    label:
    Storevarden, Bergen
    category:

    1 results

    1. onstreetBus
    municipality:
    Bergen
    county:
    Vestland
    lat:
    60.459598
    lon:
    5.279193
  5. id:
    NSR:StopPlace:29906
    name:
    Storehaugen
    label:
    Storehaugen, Stord
    category:

    1 results

    1. onstreetBus
    municipality:
    Stord
    county:
    Vestland
    lat:
    59.790059
    lon:
    5.530433
  6. id:
    NSR:StopPlace:50288
    name:
    Storhågen
    label:
    Storhågen, Narvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Narvik
    county:
    Nordland
    lat:
    68.415557
    lon:
    17.308652
  7. id:
    NSR:StopPlace:35642
    name:
    Storehaugen
    label:
    Storehaugen, Askvoll
    category:

    1 results

    1. onstreetBus
    municipality:
    Askvoll
    county:
    Vestland
    lat:
    61.352215
    lon:
    5.06595
  8. id:
    NSR:StopPlace:54386
    name:
    Storhågen
    label:
    Storhågen, Gratangen
    category:

    1 results

    1. onstreetBus
    municipality:
    Gratangen
    county:
    Troms
    lat:
    68.773568
    lon:
    17.272661
  9. id:
    NSR:StopPlace:30203
    name:
    Storvegen
    label:
    Storvegen, Øygarden
    category:

    1 results

    1. onstreetBus
    municipality:
    Øygarden
    county:
    Vestland
    lat:
    60.357042
    lon:
    4.955977
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:23603
    name:
    Storehagen
    label:
    Storehagen, Lindesnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Lindesnes
    county:
    Agder
    lat:
    58.244464
    lon:
    7.512166
  2. id:
    NSR:StopPlace:62637
    name:
    Storhagen
    label:
    Storhagen, Ullensaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ullensaker
    county:
    Akershus
    lat:
    60.133898
    lon:
    11.160685
  3. id:
    NSR:StopPlace:64025
    name:
    Strønevågen
    label:
    Strønevågen, Bjørnafjorden
    category:

    1 results

    1. onstreetBus
    municipality:
    Bjørnafjorden
    county:
    Vestland
    lat:
    60.157899
    lon:
    5.363742
  4. id:
    NSR:StopPlace:32406
    name:
    Storevarden
    label:
    Storevarden, Bergen
    category:

    1 results

    1. onstreetBus
    municipality:
    Bergen
    county:
    Vestland
    lat:
    60.459598
    lon:
    5.279193
  5. id:
    NSR:StopPlace:29906
    name:
    Storehaugen
    label:
    Storehaugen, Stord
    category:

    1 results

    1. onstreetBus
    municipality:
    Stord
    county:
    Vestland
    lat:
    59.790059
    lon:
    5.530433
  6. id:
    NSR:StopPlace:50288
    name:
    Storhågen
    label:
    Storhågen, Narvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Narvik
    county:
    Nordland
    lat:
    68.415557
    lon:
    17.308652
  7. id:
    NSR:StopPlace:35642
    name:
    Storehaugen
    label:
    Storehaugen, Askvoll
    category:

    1 results

    1. onstreetBus
    municipality:
    Askvoll
    county:
    Vestland
    lat:
    61.352215
    lon:
    5.06595
  8. id:
    NSR:StopPlace:54386
    name:
    Storhågen
    label:
    Storhågen, Gratangen
    category:

    1 results

    1. onstreetBus
    municipality:
    Gratangen
    county:
    Troms
    lat:
    68.773568
    lon:
    17.272661
  9. id:
    NSR:StopPlace:30203
    name:
    Storvegen
    label:
    Storvegen, Øygarden
    category:

    1 results

    1. onstreetBus
    municipality:
    Øygarden
    county:
    Vestland
    lat:
    60.357042
    lon:
    4.955977
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.