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-02T01:39:49Z in 0.129 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:8409
    name:
    Byermo
    label:
    Byermo, Grue
    category:

    1 results

    1. onstreetBus
    municipality:
    Grue
    county:
    Innlandet
    lat:
    60.470028
    lon:
    12.066844
  2. id:
    NSR:StopPlace:25382
    name:
    Byremo
    label:
    Byremo, Lyngdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Lyngdal
    county:
    Agder
    lat:
    58.421415
    lon:
    7.402642
  3. id:
    NSR:StopPlace:55591
    name:
    Bergmo
    label:
    Bergmo, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.541313
    lon:
    18.725429
  4. id:
    NSR:StopPlace:40617
    name:
    Bergmo
    label:
    Bergmo, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.74614
    lon:
    7.224789
  5. id:
    NSR:StopPlace:55595
    name:
    Bergmo
    label:
    Bergmo, Nordreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordreisa
    county:
    Troms
    lat:
    69.629835
    lon:
    21.293032
  6. id:
    NSR:StopPlace:51777
    name:
    Breimo
    label:
    Breimo, Alstahaug
    category:

    1 results

    1. onstreetBus
    municipality:
    Alstahaug
    county:
    Nordland
    lat:
    65.971806
    lon:
    12.562556
  7. id:
    NSR:StopPlace:55593
    name:
    Bergmo
    label:
    Bergmo, Kåfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Kåfjord
    county:
    Troms
    lat:
    69.520981
    lon:
    20.775259
  8. id:
    NSR:StopPlace:7168
    name:
    Barmo
    label:
    Barmo, Elverum
    category:

    1 results

    1. onstreetBus
    municipality:
    Elverum
    county:
    Innlandet
    lat:
    60.811198
    lon:
    11.676116
  9. id:
    NSR:StopPlace:31328
    name:
    Bergo
    label:
    Bergo, Vaksdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Vaksdal
    county:
    Vestland
    lat:
    60.789388
    lon:
    6.119654
  10. id:
    NSR:StopPlace:31331
    name:
    Bergo
    label:
    Bergo, Ulvik
    category:

    1 results

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

10 results

  1. id:
    NSR:StopPlace:8409
    name:
    Byermo
    label:
    Byermo, Grue
    category:

    1 results

    1. onstreetBus
    municipality:
    Grue
    county:
    Innlandet
    lat:
    60.470028
    lon:
    12.066844
  2. id:
    NSR:StopPlace:25382
    name:
    Byremo
    label:
    Byremo, Lyngdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Lyngdal
    county:
    Agder
    lat:
    58.421415
    lon:
    7.402642
  3. id:
    NSR:StopPlace:55591
    name:
    Bergmo
    label:
    Bergmo, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    69.541313
    lon:
    18.725429
  4. id:
    NSR:StopPlace:40617
    name:
    Bergmo
    label:
    Bergmo, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.74614
    lon:
    7.224789
  5. id:
    NSR:StopPlace:55595
    name:
    Bergmo
    label:
    Bergmo, Nordreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordreisa
    county:
    Troms
    lat:
    69.629835
    lon:
    21.293032
  6. id:
    NSR:StopPlace:51777
    name:
    Breimo
    label:
    Breimo, Alstahaug
    category:

    1 results

    1. onstreetBus
    municipality:
    Alstahaug
    county:
    Nordland
    lat:
    65.971806
    lon:
    12.562556
  7. id:
    NSR:StopPlace:55593
    name:
    Bergmo
    label:
    Bergmo, Kåfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Kåfjord
    county:
    Troms
    lat:
    69.520981
    lon:
    20.775259
  8. id:
    NSR:StopPlace:7168
    name:
    Barmo
    label:
    Barmo, Elverum
    category:

    1 results

    1. onstreetBus
    municipality:
    Elverum
    county:
    Innlandet
    lat:
    60.811198
    lon:
    11.676116
  9. id:
    NSR:StopPlace:31328
    name:
    Bergo
    label:
    Bergo, Vaksdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Vaksdal
    county:
    Vestland
    lat:
    60.789388
    lon:
    6.119654
  10. id:
    NSR:StopPlace:31331
    name:
    Bergo
    label:
    Bergo, Ulvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Ulvik
    county:
    Vestland
    lat:
    60.577661
    lon:
    6.901175
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.