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-01T23:50:03Z in 0.360 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:64193
    name:
    Tuftene
    label:
    Tuftene, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.275268
    lon:
    6.095197
  2. id:
    NSR:StopPlace:23622
    name:
    Tuftene
    label:
    Tuftene, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.813106
    lon:
    9.079303
  3. id:
    NSR:StopPlace:58412
    name:
    Tuftene kryss
    label:
    Tuftene kryss, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.257554
    lon:
    7.001333
  4. id:
    NSR:StopPlace:37403
    name:
    Tuften
    label:
    Tuften, Sunnfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunnfjord
    county:
    Vestland
    lat:
    61.358107
    lon:
    6.193353
  5. id:
    NSR:StopPlace:17585
    name:
    Tuften
    label:
    Tuften, Tønsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Tønsberg
    county:
    Vestfold
    lat:
    59.397061
    lon:
    10.117349
  6. id:
    NSR:StopPlace:52329
    name:
    Tufte
    label:
    Tufte, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.601408
    lon:
    19.868386
  7. id:
    NSR:StopPlace:21011
    name:
    Tufte
    label:
    Tufte, Nome
    category:

    1 results

    1. onstreetBus
    municipality:
    Nome
    county:
    Telemark
    lat:
    59.270182
    lon:
    9.285853
  8. id:
    NSR:StopPlace:21008
    name:
    Tufte
    label:
    Tufte, Skien
    category:

    1 results

    1. onstreetBus
    municipality:
    Skien
    county:
    Telemark
    lat:
    59.25338
    lon:
    9.578618
  9. id:
    NSR:StopPlace:17581
    name:
    Tufte
    label:
    Tufte, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.236959
    lon:
    10.34412
  10. id:
    NSR:StopPlace:35027
    name:
    Tufte
    label:
    Tufte, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.171075
    lon:
    6.539509
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:64193
    name:
    Tuftene
    label:
    Tuftene, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.275268
    lon:
    6.095197
  2. id:
    NSR:StopPlace:23622
    name:
    Tuftene
    label:
    Tuftene, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.813106
    lon:
    9.079303
  3. id:
    NSR:StopPlace:58412
    name:
    Tuftene kryss
    label:
    Tuftene kryss, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.257554
    lon:
    7.001333
  4. id:
    NSR:StopPlace:37403
    name:
    Tuften
    label:
    Tuften, Sunnfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunnfjord
    county:
    Vestland
    lat:
    61.358107
    lon:
    6.193353
  5. id:
    NSR:StopPlace:17585
    name:
    Tuften
    label:
    Tuften, Tønsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Tønsberg
    county:
    Vestfold
    lat:
    59.397061
    lon:
    10.117349
  6. id:
    NSR:StopPlace:52329
    name:
    Tufte
    label:
    Tufte, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.601408
    lon:
    19.868386
  7. id:
    NSR:StopPlace:21011
    name:
    Tufte
    label:
    Tufte, Nome
    category:

    1 results

    1. onstreetBus
    municipality:
    Nome
    county:
    Telemark
    lat:
    59.270182
    lon:
    9.285853
  8. id:
    NSR:StopPlace:21008
    name:
    Tufte
    label:
    Tufte, Skien
    category:

    1 results

    1. onstreetBus
    municipality:
    Skien
    county:
    Telemark
    lat:
    59.25338
    lon:
    9.578618
  9. id:
    NSR:StopPlace:17581
    name:
    Tufte
    label:
    Tufte, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.236959
    lon:
    10.34412
  10. id:
    NSR:StopPlace:35027
    name:
    Tufte
    label:
    Tufte, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.171075
    lon:
    6.539509
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.