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-03T05:55:20Z in 0.441 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:37720
    name:
    Hoemsbakken
    label:
    Hoemsbakken, Gjemnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjemnes
    county:
    Møre og Romsdal
    lat:
    62.962822
    lon:
    8.027241
  2. id:
    NSR:StopPlace:26610
    name:
    Hovsbakken
    label:
    Hovsbakken, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.8341
    lon:
    5.741591
  3. id:
    NSR:StopPlace:26766
    name:
    Høyebakken
    label:
    Høyebakken, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    58.98738
    lon:
    5.665094
  4. id:
    NSR:StopPlace:45813
    name:
    Hovabakken
    label:
    Hovabakken, Steinkjer
    category:

    1 results

    1. onstreetBus
    municipality:
    Steinkjer
    county:
    Trøndelag
    lat:
    63.916249
    lon:
    10.937313
  5. id:
    NSR:StopPlace:42067
    name:
    Høybakken
    label:
    Høybakken, Ørland
    category:

    1 results

    1. onstreetBus
    municipality:
    Ørland
    county:
    Trøndelag
    lat:
    63.733934
    lon:
    9.87385
  6. id:
    NSR:StopPlace:4427
    name:
    Holtbakken
    label:
    Holtbakken, Lillestrøm
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillestrøm
    county:
    Akershus
    lat:
    59.90361
    lon:
    11.182275
  7. id:
    NSR:StopPlace:49068
    name:
    Høystakken
    label:
    Høystakken, Sørfold
    category:

    1 results

    1. onstreetBus
    municipality:
    Sørfold
    county:
    Nordland
    lat:
    67.389619
    lon:
    15.65641
  8. id:
    NSR:StopPlace:14529
    name:
    Hoffsbakken
    label:
    Hoffsbakken, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.806856
    lon:
    10.677145
  9. id:
    NSR:StopPlace:20351
    name:
    Høensbakken
    label:
    Høensbakken, Bamble
    category:

    1 results

    1. onstreetBus
    municipality:
    Bamble
    county:
    Telemark
    lat:
    59.015196
    lon:
    9.605491
  10. id:
    NSR:StopPlace:46240
    name:
    Høbakken
    label:
    Høbakken, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.84558
    lon:
    11.328838
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:37720
    name:
    Hoemsbakken
    label:
    Hoemsbakken, Gjemnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjemnes
    county:
    Møre og Romsdal
    lat:
    62.962822
    lon:
    8.027241
  2. id:
    NSR:StopPlace:26610
    name:
    Hovsbakken
    label:
    Hovsbakken, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.8341
    lon:
    5.741591
  3. id:
    NSR:StopPlace:26766
    name:
    Høyebakken
    label:
    Høyebakken, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    58.98738
    lon:
    5.665094
  4. id:
    NSR:StopPlace:45813
    name:
    Hovabakken
    label:
    Hovabakken, Steinkjer
    category:

    1 results

    1. onstreetBus
    municipality:
    Steinkjer
    county:
    Trøndelag
    lat:
    63.916249
    lon:
    10.937313
  5. id:
    NSR:StopPlace:42067
    name:
    Høybakken
    label:
    Høybakken, Ørland
    category:

    1 results

    1. onstreetBus
    municipality:
    Ørland
    county:
    Trøndelag
    lat:
    63.733934
    lon:
    9.87385
  6. id:
    NSR:StopPlace:4427
    name:
    Holtbakken
    label:
    Holtbakken, Lillestrøm
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillestrøm
    county:
    Akershus
    lat:
    59.90361
    lon:
    11.182275
  7. id:
    NSR:StopPlace:49068
    name:
    Høystakken
    label:
    Høystakken, Sørfold
    category:

    1 results

    1. onstreetBus
    municipality:
    Sørfold
    county:
    Nordland
    lat:
    67.389619
    lon:
    15.65641
  8. id:
    NSR:StopPlace:14529
    name:
    Hoffsbakken
    label:
    Hoffsbakken, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.806856
    lon:
    10.677145
  9. id:
    NSR:StopPlace:20351
    name:
    Høensbakken
    label:
    Høensbakken, Bamble
    category:

    1 results

    1. onstreetBus
    municipality:
    Bamble
    county:
    Telemark
    lat:
    59.015196
    lon:
    9.605491
  10. id:
    NSR:StopPlace:46240
    name:
    Høbakken
    label:
    Høbakken, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.84558
    lon:
    11.328838
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.