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-29T01:51:29Z in 0.120 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:45192
    name:
    Reppe
    label:
    Reppe, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.782301
    lon:
    11.679829
  2. id:
    NSR:StopPlace:21756
    name:
    Reppen
    label:
    Reppen, Flekkefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Flekkefjord
    county:
    Agder
    lat:
    58.305523
    lon:
    6.737731
  3. id:
    NSR:StopPlace:57437
    name:
    Reppen
    label:
    Reppen, Nesseby
    category:

    1 results

    1. onstreetBus
    municipality:
    Nesseby
    county:
    Finnmark
    lat:
    70.093936
    lon:
    28.663555
  4. id:
    NSR:StopPlace:41483
    name:
    Reppen
    label:
    Reppen, Surnadal
    category:

    1 results

    1. onstreetBus
    municipality:
    Surnadal
    county:
    Møre og Romsdal
    lat:
    62.902263
    lon:
    8.489811
  5. id:
    NSR:StopPlace:41698
    name:
    Reppe snuplass
    label:
    Reppe snuplass, Trondheim
    category:

    1 results

    1. onstreetBus
    municipality:
    Trondheim
    county:
    Trøndelag
    lat:
    63.415996
    lon:
    10.557936
  6. id:
    NSR:StopPlace:34054
    name:
    Reppen kryss
    label:
    Reppen kryss, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.258644
    lon:
    7.009012
  7. id:
    NSR:StopPlace:44895
    name:
    Reppesfeltet
    label:
    Reppesfeltet, Stjørdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stjørdal
    county:
    Trøndelag
    lat:
    63.44652
    lon:
    10.959742
  8. id:
    NSR:StopPlace:14665
    name:
    Aura Reppen
    label:
    Aura Reppen, Skjåk
    category:

    1 results

    1. onstreetBus
    municipality:
    Skjåk
    county:
    Innlandet
    lat:
    61.887764
    lon:
    8.348783
  9. id:
    NSR:StopPlace:50550
    name:
    Reppa
    label:
    Reppa, Rødøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Rødøy
    county:
    Nordland
    lat:
    66.647984
    lon:
    13.567295
  10. id:
    NSR:StopPlace:44997
    name:
    Reppa
    label:
    Reppa, Stjørdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stjørdal
    county:
    Trøndelag
    lat:
    63.446955
    lon:
    10.944341
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:45192
    name:
    Reppe
    label:
    Reppe, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.782301
    lon:
    11.679829
  2. id:
    NSR:StopPlace:21756
    name:
    Reppen
    label:
    Reppen, Flekkefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Flekkefjord
    county:
    Agder
    lat:
    58.305523
    lon:
    6.737731
  3. id:
    NSR:StopPlace:57437
    name:
    Reppen
    label:
    Reppen, Nesseby
    category:

    1 results

    1. onstreetBus
    municipality:
    Nesseby
    county:
    Finnmark
    lat:
    70.093936
    lon:
    28.663555
  4. id:
    NSR:StopPlace:41483
    name:
    Reppen
    label:
    Reppen, Surnadal
    category:

    1 results

    1. onstreetBus
    municipality:
    Surnadal
    county:
    Møre og Romsdal
    lat:
    62.902263
    lon:
    8.489811
  5. id:
    NSR:StopPlace:41698
    name:
    Reppe snuplass
    label:
    Reppe snuplass, Trondheim
    category:

    1 results

    1. onstreetBus
    municipality:
    Trondheim
    county:
    Trøndelag
    lat:
    63.415996
    lon:
    10.557936
  6. id:
    NSR:StopPlace:34054
    name:
    Reppen kryss
    label:
    Reppen kryss, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.258644
    lon:
    7.009012
  7. id:
    NSR:StopPlace:44895
    name:
    Reppesfeltet
    label:
    Reppesfeltet, Stjørdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stjørdal
    county:
    Trøndelag
    lat:
    63.44652
    lon:
    10.959742
  8. id:
    NSR:StopPlace:14665
    name:
    Aura Reppen
    label:
    Aura Reppen, Skjåk
    category:

    1 results

    1. onstreetBus
    municipality:
    Skjåk
    county:
    Innlandet
    lat:
    61.887764
    lon:
    8.348783
  9. id:
    NSR:StopPlace:50550
    name:
    Reppa
    label:
    Reppa, Rødøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Rødøy
    county:
    Nordland
    lat:
    66.647984
    lon:
    13.567295
  10. id:
    NSR:StopPlace:44997
    name:
    Reppa
    label:
    Reppa, Stjørdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stjørdal
    county:
    Trøndelag
    lat:
    63.446955
    lon:
    10.944341
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.