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-19T20:22:34Z in 0.000 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:23677
    name:
    Nøding
    label:
    Nøding, Lindesnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Lindesnes
    county:
    Agder
    lat:
    58.104372
    lon:
    7.536795
  2. id:
    NSR:StopPlace:70029
    name:
    Nordeng
    label:
    Nordeng, Balsfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Balsfjord
    county:
    Troms
    lat:
    69.40641
    lon:
    18.696483
  3. id:
    NSR:StopPlace:9357
    name:
    Nordeng
    label:
    Nordeng, Stor-Elvdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stor-Elvdal
    county:
    Innlandet
    lat:
    61.899079
    lon:
    10.112776
  4. id:
    NSR:StopPlace:1952
    name:
    Nordeng
    label:
    Nordeng, Rakkestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Rakkestad
    county:
    Østfold
    lat:
    59.437415
    lon:
    11.37655
  5. id:
    NSR:StopPlace:56232
    name:
    Nordeng
    label:
    Nordeng, Nordreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordreisa
    county:
    Troms
    lat:
    69.918073
    lon:
    21.277541
  6. id:
    NSR:StopPlace:51648
    name:
    Nordeng
    label:
    Nordeng, Rana
    category:

    1 results

    1. onstreetBus
    municipality:
    Rana
    county:
    Nordland
    lat:
    66.302947
    lon:
    13.554525
  7. id:
    NSR:StopPlace:56223
    name:
    Nordeng
    label:
    Nordeng, Bardu
    category:

    1 results

    1. onstreetBus
    municipality:
    Bardu
    county:
    Troms
    lat:
    68.897602
    lon:
    18.394562
  8. id:
    NSR:StopPlace:58174
    name:
    Nordeng
    label:
    Nordeng, Ås
    category:

    1 results

    1. onstreetBus
    municipality:
    Ås
    county:
    Akershus
    lat:
    59.723735
    lon:
    10.783672
  9. id:
    NSR:StopPlace:7430
    name:
    Norin
    label:
    Norin, Tynset
    category:

    1 results

    1. onstreetBus
    municipality:
    Tynset
    county:
    Innlandet
    lat:
    62.372062
    lon:
    10.530888
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:23677
    name:
    Nøding
    label:
    Nøding, Lindesnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Lindesnes
    county:
    Agder
    lat:
    58.104372
    lon:
    7.536795
  2. id:
    NSR:StopPlace:70029
    name:
    Nordeng
    label:
    Nordeng, Balsfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Balsfjord
    county:
    Troms
    lat:
    69.40641
    lon:
    18.696483
  3. id:
    NSR:StopPlace:9357
    name:
    Nordeng
    label:
    Nordeng, Stor-Elvdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Stor-Elvdal
    county:
    Innlandet
    lat:
    61.899079
    lon:
    10.112776
  4. id:
    NSR:StopPlace:1952
    name:
    Nordeng
    label:
    Nordeng, Rakkestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Rakkestad
    county:
    Østfold
    lat:
    59.437415
    lon:
    11.37655
  5. id:
    NSR:StopPlace:56232
    name:
    Nordeng
    label:
    Nordeng, Nordreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Nordreisa
    county:
    Troms
    lat:
    69.918073
    lon:
    21.277541
  6. id:
    NSR:StopPlace:51648
    name:
    Nordeng
    label:
    Nordeng, Rana
    category:

    1 results

    1. onstreetBus
    municipality:
    Rana
    county:
    Nordland
    lat:
    66.302947
    lon:
    13.554525
  7. id:
    NSR:StopPlace:56223
    name:
    Nordeng
    label:
    Nordeng, Bardu
    category:

    1 results

    1. onstreetBus
    municipality:
    Bardu
    county:
    Troms
    lat:
    68.897602
    lon:
    18.394562
  8. id:
    NSR:StopPlace:58174
    name:
    Nordeng
    label:
    Nordeng, Ås
    category:

    1 results

    1. onstreetBus
    municipality:
    Ås
    county:
    Akershus
    lat:
    59.723735
    lon:
    10.783672
  9. id:
    NSR:StopPlace:7430
    name:
    Norin
    label:
    Norin, Tynset
    category:

    1 results

    1. onstreetBus
    municipality:
    Tynset
    county:
    Innlandet
    lat:
    62.372062
    lon:
    10.530888
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.