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-13T17:45:22Z in 0.148 seconds.

returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:39032
    name:
    Flatvad
    label:
    Flatvad, Sunndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunndal
    county:
    Møre og Romsdal
    lat:
    62.639981
    lon:
    8.78563
  2. id:
    NSR:StopPlace:43817
    name:
    Flatval
    label:
    Flatval, Frøya
    category:

    1 results

    1. onstreetBus
    municipality:
    Frøya
    county:
    Trøndelag
    lat:
    63.688751
    lon:
    8.759374
  3. id:
    NSR:StopPlace:32428
    name:
    Flatevad
    label:
    Flatevad, Bergen
    category:

    1 results

    1. onstreetBus
    municipality:
    Bergen
    county:
    Vestland
    lat:
    60.465055
    lon:
    5.313241
  4. id:
    NSR:StopPlace:38986
    name:
    Flatmark
    label:
    Flatmark, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.429387
    lon:
    7.970875
  5. id:
    NSR:StopPlace:4888
    name:
    Flatner
    label:
    Flatner, Gjerdrum
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerdrum
    county:
    Akershus
    lat:
    60.032025
    lon:
    11.045071
  6. id:
    NSR:StopPlace:11077
    name:
    Flatla
    label:
    Flatla, Lunner
    category:

    1 results

    1. onstreetBus
    municipality:
    Lunner
    county:
    Akershus
    lat:
    60.309179
    lon:
    10.582272
  7. id:
    NSR:StopPlace:46578
    name:
    Flatås
    label:
    Flatås, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.921125
    lon:
    11.274652
  8. id:
    NSR:StopPlace:19054
    name:
    Flåtan
    label:
    Flåtan, Holmestrand
    category:

    1 results

    1. onstreetBus
    municipality:
    Holmestrand
    county:
    Vestfold
    lat:
    59.65894
    lon:
    10.211886
  9. id:
    NSR:StopPlace:45469
    name:
    Flatås
    label:
    Flatås, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.820282
    lon:
    11.631798
  10. id:
    NSR:StopPlace:46363
    name:
    Flåtta
    label:
    Flåtta, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.93538
    lon:
    11.296172
  11. id:
    NSR:StopPlace:15843
    name:
    Flåta
    label:
    Flåta, Nore og Uvdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Nore og Uvdal
    county:
    Buskerud
    lat:
    60.269479
    lon:
    8.734199
  12. id:
    NSR:StopPlace:44977
    name:
    Flata
    label:
    Flata, Indre Fosen
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Fosen
    county:
    Trøndelag
    lat:
    63.575947
    lon:
    10.369957
  13. id:
    NSR:StopPlace:16718
    name:
    Flata
    label:
    Flata, Kongsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Kongsberg
    county:
    Buskerud
    lat:
    59.57231
    lon:
    9.625262
  14. id:
    NSR:StopPlace:14957
    name:
    Flata
    label:
    Flata, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.9898
    lon:
    9.881955
Show all fields in HTML
returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:39032
    name:
    Flatvad
    label:
    Flatvad, Sunndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sunndal
    county:
    Møre og Romsdal
    lat:
    62.639981
    lon:
    8.78563
  2. id:
    NSR:StopPlace:43817
    name:
    Flatval
    label:
    Flatval, Frøya
    category:

    1 results

    1. onstreetBus
    municipality:
    Frøya
    county:
    Trøndelag
    lat:
    63.688751
    lon:
    8.759374
  3. id:
    NSR:StopPlace:32428
    name:
    Flatevad
    label:
    Flatevad, Bergen
    category:

    1 results

    1. onstreetBus
    municipality:
    Bergen
    county:
    Vestland
    lat:
    60.465055
    lon:
    5.313241
  4. id:
    NSR:StopPlace:38986
    name:
    Flatmark
    label:
    Flatmark, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.429387
    lon:
    7.970875
  5. id:
    NSR:StopPlace:4888
    name:
    Flatner
    label:
    Flatner, Gjerdrum
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerdrum
    county:
    Akershus
    lat:
    60.032025
    lon:
    11.045071
  6. id:
    NSR:StopPlace:11077
    name:
    Flatla
    label:
    Flatla, Lunner
    category:

    1 results

    1. onstreetBus
    municipality:
    Lunner
    county:
    Akershus
    lat:
    60.309179
    lon:
    10.582272
  7. id:
    NSR:StopPlace:46578
    name:
    Flatås
    label:
    Flatås, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.921125
    lon:
    11.274652
  8. id:
    NSR:StopPlace:19054
    name:
    Flåtan
    label:
    Flåtan, Holmestrand
    category:

    1 results

    1. onstreetBus
    municipality:
    Holmestrand
    county:
    Vestfold
    lat:
    59.65894
    lon:
    10.211886
  9. id:
    NSR:StopPlace:45469
    name:
    Flatås
    label:
    Flatås, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.820282
    lon:
    11.631798
  10. id:
    NSR:StopPlace:46363
    name:
    Flåtta
    label:
    Flåtta, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.93538
    lon:
    11.296172
  11. id:
    NSR:StopPlace:15843
    name:
    Flåta
    label:
    Flåta, Nore og Uvdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Nore og Uvdal
    county:
    Buskerud
    lat:
    60.269479
    lon:
    8.734199
  12. id:
    NSR:StopPlace:44977
    name:
    Flata
    label:
    Flata, Indre Fosen
    category:

    1 results

    1. onstreetBus
    municipality:
    Indre Fosen
    county:
    Trøndelag
    lat:
    63.575947
    lon:
    10.369957
  13. id:
    NSR:StopPlace:16718
    name:
    Flata
    label:
    Flata, Kongsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Kongsberg
    county:
    Buskerud
    lat:
    59.57231
    lon:
    9.625262
  14. id:
    NSR:StopPlace:14957
    name:
    Flata
    label:
    Flata, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.9898
    lon:
    9.881955
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.