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-10T23:35:05Z in 0.000 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:47615
    name:
    Finnøy
    label:
    Finnøy, Hamarøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamarøy
    county:
    Nordland
    lat:
    68.001866
    lon:
    15.497103
  2. id:
    NSR:StopPlace:38829
    name:
    Finnøy
    label:
    Finnøy, Ålesund
    category:

    1 results

    1. onstreetBus
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.796238
    lon:
    6.492039
  3. id:
    NSR:StopPlace:58745
    name:
    Finnøya ferjekai
    label:
    Finnøya ferjekai, Ålesund
    category:

    2 results

    1. onstreetBus
    2. harbourPort
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.804063
    lon:
    6.508935
  4. id:
    NSR:StopPlace:28219
    name:
    Finnøy sentralskule
    label:
    Finnøy sentralskule, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.175047
    lon:
    5.873684
  5. id:
    NSR:StopPlace:55367
    name:
    Finnes
    label:
    Finnes, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.273248
    lon:
    17.124389
  6. id:
    NSR:StopPlace:56943
    name:
    Finnes
    label:
    Finnes, Alta
    category:

    1 results

    1. onstreetBus
    municipality:
    Alta
    county:
    Finnmark
    lat:
    70.137006
    lon:
    22.9751
  7. id:
    NSR:StopPlace:12400
    name:
    Finni
    label:
    Finni, Nordre Land
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordre Land
    county:
    Innlandet
    lat:
    60.941625
    lon:
    10.119657
  8. id:
    NSR:StopPlace:45610
    name:
    Finne
    label:
    Finne, Levanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Levanger
    county:
    Trøndelag
    lat:
    63.662111
    lon:
    11.215912
  9. id:
    NSR:StopPlace:45947
    name:
    Finne
    label:
    Finne, Nærøysund
    category:

    1 results

    1. onstreetBus
    municipality:
    Nærøysund
    county:
    Trøndelag
    lat:
    64.879494
    lon:
    11.66253
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:47615
    name:
    Finnøy
    label:
    Finnøy, Hamarøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamarøy
    county:
    Nordland
    lat:
    68.001866
    lon:
    15.497103
  2. id:
    NSR:StopPlace:38829
    name:
    Finnøy
    label:
    Finnøy, Ålesund
    category:

    1 results

    1. onstreetBus
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.796238
    lon:
    6.492039
  3. id:
    NSR:StopPlace:58745
    name:
    Finnøya ferjekai
    label:
    Finnøya ferjekai, Ålesund
    category:

    2 results

    1. onstreetBus
    2. harbourPort
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.804063
    lon:
    6.508935
  4. id:
    NSR:StopPlace:28219
    name:
    Finnøy sentralskule
    label:
    Finnøy sentralskule, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.175047
    lon:
    5.873684
  5. id:
    NSR:StopPlace:55367
    name:
    Finnes
    label:
    Finnes, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.273248
    lon:
    17.124389
  6. id:
    NSR:StopPlace:56943
    name:
    Finnes
    label:
    Finnes, Alta
    category:

    1 results

    1. onstreetBus
    municipality:
    Alta
    county:
    Finnmark
    lat:
    70.137006
    lon:
    22.9751
  7. id:
    NSR:StopPlace:12400
    name:
    Finni
    label:
    Finni, Nordre Land
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordre Land
    county:
    Innlandet
    lat:
    60.941625
    lon:
    10.119657
  8. id:
    NSR:StopPlace:45610
    name:
    Finne
    label:
    Finne, Levanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Levanger
    county:
    Trøndelag
    lat:
    63.662111
    lon:
    11.215912
  9. id:
    NSR:StopPlace:45947
    name:
    Finne
    label:
    Finne, Nærøysund
    category:

    1 results

    1. onstreetBus
    municipality:
    Nærøysund
    county:
    Trøndelag
    lat:
    64.879494
    lon:
    11.66253
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.