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-04T22:47:26Z in 0.154 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:31817
    name:
    Løfall
    label:
    Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.016984
    lon:
    6.000221
  2. id:
    NSR:StopPlace:31819
    name:
    Løfallstrand kai
    label:
    Løfallstrand kai, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.016929
    lon:
    5.997956
  3. id:
    NSR:StopPlace:31812
    name:
    Gjerde Løfall
    label:
    Gjerde Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.023483
    lon:
    6.002601
  4. id:
    NSR:StopPlace:31822
    name:
    Myre Løfall
    label:
    Myre Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.012709
    lon:
    5.99852
  5. id:
    NSR:StopPlace:39463
    name:
    Løfald
    label:
    Løfald, Rindal
    category:

    1 results

    1. onstreetBus
    municipality:
    Rindal
    county:
    Trøndelag
    lat:
    63.09318
    lon:
    9.257912
  6. id:
    NSR:StopPlace:39466
    name:
    Løfoll
    label:
    Løfoll, Volda
    category:

    1 results

    1. onstreetBus
    municipality:
    Volda
    county:
    Møre og Romsdal
    lat:
    62.065411
    lon:
    6.28615
  7. id:
    NSR:StopPlace:39541
    name:
    Løvoll
    label:
    Løvoll, Sykkylven
    category:

    1 results

    1. onstreetBus
    municipality:
    Sykkylven
    county:
    Møre og Romsdal
    lat:
    62.424133
    lon:
    6.710935
  8. id:
    NSR:StopPlace:39544
    name:
    Løvoll
    label:
    Løvoll, Fjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Fjord
    county:
    Møre og Romsdal
    lat:
    62.212298
    lon:
    7.160013
  9. id:
    NSR:StopPlace:54750
    name:
    Løvoll
    label:
    Løvoll, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.624067
    lon:
    18.330655
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:31817
    name:
    Løfall
    label:
    Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.016984
    lon:
    6.000221
  2. id:
    NSR:StopPlace:31819
    name:
    Løfallstrand kai
    label:
    Løfallstrand kai, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.016929
    lon:
    5.997956
  3. id:
    NSR:StopPlace:31812
    name:
    Gjerde Løfall
    label:
    Gjerde Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.023483
    lon:
    6.002601
  4. id:
    NSR:StopPlace:31822
    name:
    Myre Løfall
    label:
    Myre Løfall, Kvinnherad
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinnherad
    county:
    Vestland
    lat:
    60.012709
    lon:
    5.99852
  5. id:
    NSR:StopPlace:39463
    name:
    Løfald
    label:
    Løfald, Rindal
    category:

    1 results

    1. onstreetBus
    municipality:
    Rindal
    county:
    Trøndelag
    lat:
    63.09318
    lon:
    9.257912
  6. id:
    NSR:StopPlace:39466
    name:
    Løfoll
    label:
    Løfoll, Volda
    category:

    1 results

    1. onstreetBus
    municipality:
    Volda
    county:
    Møre og Romsdal
    lat:
    62.065411
    lon:
    6.28615
  7. id:
    NSR:StopPlace:39541
    name:
    Løvoll
    label:
    Løvoll, Sykkylven
    category:

    1 results

    1. onstreetBus
    municipality:
    Sykkylven
    county:
    Møre og Romsdal
    lat:
    62.424133
    lon:
    6.710935
  8. id:
    NSR:StopPlace:39544
    name:
    Løvoll
    label:
    Løvoll, Fjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Fjord
    county:
    Møre og Romsdal
    lat:
    62.212298
    lon:
    7.160013
  9. id:
    NSR:StopPlace:54750
    name:
    Løvoll
    label:
    Løvoll, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.624067
    lon:
    18.330655
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.