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-11T20:47:59Z in 0.001 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:13891
    name:
    Hornås
    label:
    Hornås, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.80834
    lon:
    10.439576
  2. id:
    NSR:StopPlace:48655
    name:
    Holdøy
    label:
    Holdøy, Hadsel
    category:

    1 results

    1. onstreetBus
    municipality:
    Hadsel
    county:
    Nordland
    lat:
    68.45619
    lon:
    14.900484
  3. id:
    NSR:StopPlace:36637
    name:
    Horne
    label:
    Horne, Hyllestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Hyllestad
    county:
    Vestland
    lat:
    61.267188
    lon:
    5.226653
  4. id:
    NSR:StopPlace:15563
    name:
    Horne
    label:
    Horne, Ringerike
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringerike
    county:
    Buskerud
    lat:
    60.169841
    lon:
    10.345406
  5. id:
    NSR:StopPlace:10757
    name:
    Horna
    label:
    Horna, Elverum
    category:

    1 results

    1. onstreetBus
    municipality:
    Elverum
    county:
    Innlandet
    lat:
    60.950161
    lon:
    11.672732
  6. id:
    NSR:StopPlace:18321
    name:
    Horn
    label:
    Horn, Tønsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Tønsberg
    county:
    Vestfold
    lat:
    59.386201
    lon:
    10.220866
  7. id:
    NSR:StopPlace:13840
    name:
    Horn
    label:
    Horn, Lillehammer
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillehammer
    county:
    Innlandet
    lat:
    61.179921
    lon:
    10.324673
  8. id:
    NSR:StopPlace:47081
    name:
    Horn
    label:
    Horn, Dønna
    category:

    1 results

    1. onstreetBus
    municipality:
    Dønna
    county:
    Nordland
    lat:
    66.15692
    lon:
    12.785889
  9. id:
    NSR:StopPlace:47487
    name:
    Horn
    label:
    Horn, Vestvågøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Vestvågøy
    county:
    Nordland
    lat:
    68.21544
    lon:
    14.05585
  10. id:
    NSR:StopPlace:16601
    name:
    Horn
    label:
    Horn, Lier
    category:

    1 results

    1. onstreetBus
    municipality:
    Lier
    county:
    Buskerud
    lat:
    59.959427
    lon:
    10.282379
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:13891
    name:
    Hornås
    label:
    Hornås, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.80834
    lon:
    10.439576
  2. id:
    NSR:StopPlace:48655
    name:
    Holdøy
    label:
    Holdøy, Hadsel
    category:

    1 results

    1. onstreetBus
    municipality:
    Hadsel
    county:
    Nordland
    lat:
    68.45619
    lon:
    14.900484
  3. id:
    NSR:StopPlace:36637
    name:
    Horne
    label:
    Horne, Hyllestad
    category:

    1 results

    1. onstreetBus
    municipality:
    Hyllestad
    county:
    Vestland
    lat:
    61.267188
    lon:
    5.226653
  4. id:
    NSR:StopPlace:15563
    name:
    Horne
    label:
    Horne, Ringerike
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringerike
    county:
    Buskerud
    lat:
    60.169841
    lon:
    10.345406
  5. id:
    NSR:StopPlace:10757
    name:
    Horna
    label:
    Horna, Elverum
    category:

    1 results

    1. onstreetBus
    municipality:
    Elverum
    county:
    Innlandet
    lat:
    60.950161
    lon:
    11.672732
  6. id:
    NSR:StopPlace:18321
    name:
    Horn
    label:
    Horn, Tønsberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Tønsberg
    county:
    Vestfold
    lat:
    59.386201
    lon:
    10.220866
  7. id:
    NSR:StopPlace:13840
    name:
    Horn
    label:
    Horn, Lillehammer
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillehammer
    county:
    Innlandet
    lat:
    61.179921
    lon:
    10.324673
  8. id:
    NSR:StopPlace:47081
    name:
    Horn
    label:
    Horn, Dønna
    category:

    1 results

    1. onstreetBus
    municipality:
    Dønna
    county:
    Nordland
    lat:
    66.15692
    lon:
    12.785889
  9. id:
    NSR:StopPlace:47487
    name:
    Horn
    label:
    Horn, Vestvågøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Vestvågøy
    county:
    Nordland
    lat:
    68.21544
    lon:
    14.05585
  10. id:
    NSR:StopPlace:16601
    name:
    Horn
    label:
    Horn, Lier
    category:

    1 results

    1. onstreetBus
    municipality:
    Lier
    county:
    Buskerud
    lat:
    59.959427
    lon:
    10.282379
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.