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-02T15:05:13Z in 0.243 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:22243
    name:
    Sandtaket
    label:
    Sandtaket, Iveland
    category:

    1 results

    1. onstreetBus
    municipality:
    Iveland
    county:
    Agder
    lat:
    58.451274
    lon:
    7.917291
  2. id:
    NSR:StopPlace:37908
    name:
    Sandtaket
    label:
    Sandtaket, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.548615
    lon:
    7.659857
  3. id:
    NSR:StopPlace:63539
    name:
    Sandåker
    label:
    Sandåker, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.888606
    lon:
    9.027854
  4. id:
    NSR:StopPlace:10832
    name:
    Sandaker
    label:
    Sandaker, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.859763
    lon:
    11.242088
  5. id:
    NSR:StopPlace:2270
    name:
    Sandaker
    label:
    Sandaker, Indre Østfold
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Østfold
    county:
    Østfold
    lat:
    59.466713
    lon:
    11.379521
  6. id:
    NSR:StopPlace:47078
    name:
    Sandåker
    label:
    Sandåker, Dønna
    category:

    1 results

    1. onstreetBus
    municipality:
    Dønna
    county:
    Nordland
    lat:
    66.148912
    lon:
    12.732512
  7. id:
    NSR:StopPlace:6409
    name:
    Sandaker
    label:
    Sandaker, Oslo
    category:

    1 results

    1. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.94243
    lon:
    10.770402
  8. id:
    NSR:StopPlace:6749
    name:
    Sandaker
    label:
    Sandaker, Nes
    category:

    1 results

    1. onstreetBus
    municipality:
    Nes
    county:
    Akershus
    lat:
    60.240373
    lon:
    11.308581
  9. id:
    NSR:StopPlace:8196
    name:
    Sandaker
    label:
    Sandaker, Løten
    category:

    1 results

    1. onstreetBus
    municipality:
    Løten
    county:
    Innlandet
    lat:
    60.796397
    lon:
    11.459804
  10. id:
    NSR:StopPlace:12921
    name:
    Sandåker
    label:
    Sandåker, Østre Toten
    category:

    1 results

    1. onstreetBus
    municipality:
    Østre Toten
    county:
    Innlandet
    lat:
    60.725497
    lon:
    10.767133
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:22243
    name:
    Sandtaket
    label:
    Sandtaket, Iveland
    category:

    1 results

    1. onstreetBus
    municipality:
    Iveland
    county:
    Agder
    lat:
    58.451274
    lon:
    7.917291
  2. id:
    NSR:StopPlace:37908
    name:
    Sandtaket
    label:
    Sandtaket, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.548615
    lon:
    7.659857
  3. id:
    NSR:StopPlace:63539
    name:
    Sandåker
    label:
    Sandåker, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.888606
    lon:
    9.027854
  4. id:
    NSR:StopPlace:10832
    name:
    Sandaker
    label:
    Sandaker, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.859763
    lon:
    11.242088
  5. id:
    NSR:StopPlace:2270
    name:
    Sandaker
    label:
    Sandaker, Indre Østfold
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Østfold
    county:
    Østfold
    lat:
    59.466713
    lon:
    11.379521
  6. id:
    NSR:StopPlace:47078
    name:
    Sandåker
    label:
    Sandåker, Dønna
    category:

    1 results

    1. onstreetBus
    municipality:
    Dønna
    county:
    Nordland
    lat:
    66.148912
    lon:
    12.732512
  7. id:
    NSR:StopPlace:6409
    name:
    Sandaker
    label:
    Sandaker, Oslo
    category:

    1 results

    1. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.94243
    lon:
    10.770402
  8. id:
    NSR:StopPlace:6749
    name:
    Sandaker
    label:
    Sandaker, Nes
    category:

    1 results

    1. onstreetBus
    municipality:
    Nes
    county:
    Akershus
    lat:
    60.240373
    lon:
    11.308581
  9. id:
    NSR:StopPlace:8196
    name:
    Sandaker
    label:
    Sandaker, Løten
    category:

    1 results

    1. onstreetBus
    municipality:
    Løten
    county:
    Innlandet
    lat:
    60.796397
    lon:
    11.459804
  10. id:
    NSR:StopPlace:12921
    name:
    Sandåker
    label:
    Sandåker, Østre Toten
    category:

    1 results

    1. onstreetBus
    municipality:
    Østre Toten
    county:
    Innlandet
    lat:
    60.725497
    lon:
    10.767133
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.