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-09-29T22:46:12Z in 0.133 seconds.

returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:38063
    name:
    Djupdalen
    label:
    Djupdalen, Sula
    category:

    1 results

    1. onstreetBus
    municipality:
    Sula
    county:
    Møre og Romsdal
    lat:
    62.44068
    lon:
    6.194841
  2. id:
    NSR:StopPlace:51145
    name:
    Djupdalen
    label:
    Djupdalen, Rana
    category:

    1 results

    1. onstreetBus
    municipality:
    Rana
    county:
    Nordland
    lat:
    66.329436
    lon:
    13.993394
  3. id:
    NSR:StopPlace:57841
    name:
    Djupdalen
    label:
    Djupdalen, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    69.068049
    lon:
    18.597295
  4. id:
    NSR:StopPlace:13052
    name:
    Djupdalen
    label:
    Djupdalen, Sel
    category:

    1 results

    1. onstreetBus
    municipality:
    Sel
    county:
    Innlandet
    lat:
    61.746249
    lon:
    9.201205
  5. id:
    NSR:StopPlace:17126
    name:
    Djupdalen
    label:
    Djupdalen, Drammen
    category:

    1 results

    1. onstreetBus
    municipality:
    Drammen
    county:
    Buskerud
    lat:
    59.71555
    lon:
    10.1592
  6. id:
    NSR:StopPlace:45322
    name:
    Djupdalen
    label:
    Djupdalen, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.810221
    lon:
    12.244504
  7. id:
    NSR:StopPlace:41360
    name:
    Djupdalen øst
    label:
    Djupdalen øst, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.732697
    lon:
    7.058638
  8. id:
    NSR:StopPlace:41356
    name:
    Djupdalen vest
    label:
    Djupdalen vest, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.73232
    lon:
    7.055316
  9. id:
    NSR:StopPlace:56340
    name:
    Djupedalen
    label:
    Djupedalen, Ibestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Ibestad
    county:
    Troms
    lat:
    68.811276
    lon:
    17.184587
  10. id:
    NSR:StopPlace:15743
    name:
    Djupedalen
    label:
    Djupedalen, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.613384
    lon:
    8.274427
  11. id:
    NSR:StopPlace:70183
    name:
    Djupdal
    label:
    Djupdal, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    68.94979
    lon:
    18.93727
  12. id:
    NSR:StopPlace:43452
    name:
    Djupdal
    label:
    Djupdal, Ørland
    category:

    1 results

    1. onstreetBus
    municipality:
    Ørland
    county:
    Trøndelag
    lat:
    63.702758
    lon:
    9.594759
  13. id:
    NSR:StopPlace:56339
    name:
    Djupdal
    label:
    Djupdal, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.228603
    lon:
    18.19309
  14. id:
    NSR:StopPlace:15688
    name:
    Djupdal
    label:
    Djupdal, Rollag
    category:

    1 results

    1. onstreetBus
    municipality:
    Rollag
    county:
    Buskerud
    lat:
    59.94275
    lon:
    9.342155
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:38063
    name:
    Djupdalen
    label:
    Djupdalen, Sula
    category:

    1 results

    1. onstreetBus
    municipality:
    Sula
    county:
    Møre og Romsdal
    lat:
    62.44068
    lon:
    6.194841
  2. id:
    NSR:StopPlace:51145
    name:
    Djupdalen
    label:
    Djupdalen, Rana
    category:

    1 results

    1. onstreetBus
    municipality:
    Rana
    county:
    Nordland
    lat:
    66.329436
    lon:
    13.993394
  3. id:
    NSR:StopPlace:57841
    name:
    Djupdalen
    label:
    Djupdalen, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    69.068049
    lon:
    18.597295
  4. id:
    NSR:StopPlace:13052
    name:
    Djupdalen
    label:
    Djupdalen, Sel
    category:

    1 results

    1. onstreetBus
    municipality:
    Sel
    county:
    Innlandet
    lat:
    61.746249
    lon:
    9.201205
  5. id:
    NSR:StopPlace:17126
    name:
    Djupdalen
    label:
    Djupdalen, Drammen
    category:

    1 results

    1. onstreetBus
    municipality:
    Drammen
    county:
    Buskerud
    lat:
    59.71555
    lon:
    10.1592
  6. id:
    NSR:StopPlace:45322
    name:
    Djupdalen
    label:
    Djupdalen, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.810221
    lon:
    12.244504
  7. id:
    NSR:StopPlace:41360
    name:
    Djupdalen øst
    label:
    Djupdalen øst, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.732697
    lon:
    7.058638
  8. id:
    NSR:StopPlace:41356
    name:
    Djupdalen vest
    label:
    Djupdalen vest, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.73232
    lon:
    7.055316
  9. id:
    NSR:StopPlace:56340
    name:
    Djupedalen
    label:
    Djupedalen, Ibestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Ibestad
    county:
    Troms
    lat:
    68.811276
    lon:
    17.184587
  10. id:
    NSR:StopPlace:15743
    name:
    Djupedalen
    label:
    Djupedalen, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.613384
    lon:
    8.274427
  11. id:
    NSR:StopPlace:70183
    name:
    Djupdal
    label:
    Djupdal, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    68.94979
    lon:
    18.93727
  12. id:
    NSR:StopPlace:43452
    name:
    Djupdal
    label:
    Djupdal, Ørland
    category:

    1 results

    1. onstreetBus
    municipality:
    Ørland
    county:
    Trøndelag
    lat:
    63.702758
    lon:
    9.594759
  13. id:
    NSR:StopPlace:56339
    name:
    Djupdal
    label:
    Djupdal, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.228603
    lon:
    18.19309
  14. id:
    NSR:StopPlace:15688
    name:
    Djupdal
    label:
    Djupdal, Rollag
    category:

    1 results

    1. onstreetBus
    municipality:
    Rollag
    county:
    Buskerud
    lat:
    59.94275
    lon:
    9.342155
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.