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-21T12:15:33Z in 0.127 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:10276
    name:
    Ingeberg
    label:
    Ingeberg, Ringsaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringsaker
    county:
    Innlandet
    lat:
    60.847294
    lon:
    10.797027
  2. id:
    NSR:StopPlace:10719
    name:
    Ingeberg nedre
    label:
    Ingeberg nedre, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.827674
    lon:
    11.125693
  3. id:
    NSR:StopPlace:9605
    name:
    Ingeberg skole
    label:
    Ingeberg skole, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.826954
    lon:
    11.130955
  4. id:
    NSR:StopPlace:36449
    name:
    Ingebergvika
    label:
    Ingebergvika, Solund
    category:

    1 results

    1. onstreetBus
    municipality:
    Solund
    county:
    Vestland
    lat:
    61.08049
    lon:
    4.868372
  5. id:
    NSR:StopPlace:10745
    name:
    Rugdevegen
    label:
    Rugdevegen, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.828451
    lon:
    11.135016
  6. id:
    NSR:StopPlace:9608
    name:
    Hagavegen
    label:
    Hagavegen, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.827083
    lon:
    11.125956
  7. id:
    NSR:StopPlace:45938
    name:
    Inner-Berg
    label:
    Inner-Berg, Levanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Levanger
    county:
    Trøndelag
    lat:
    63.796151
    lon:
    11.134533
  8. id:
    NSR:StopPlace:52818
    name:
    Indre Berg
    label:
    Indre Berg, Storfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Storfjord
    county:
    Troms
    lat:
    69.299921
    lon:
    19.98297
  9. id:
    NSR:StopPlace:52820
    name:
    Indre Berg
    label:
    Indre Berg, Lyngen
    category:

    1 results

    1. onstreetBus
    municipality:
    Lyngen
    county:
    Troms
    lat:
    69.642894
    lon:
    19.817773
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:10276
    name:
    Ingeberg
    label:
    Ingeberg, Ringsaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringsaker
    county:
    Innlandet
    lat:
    60.847294
    lon:
    10.797027
  2. id:
    NSR:StopPlace:10719
    name:
    Ingeberg nedre
    label:
    Ingeberg nedre, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.827674
    lon:
    11.125693
  3. id:
    NSR:StopPlace:9605
    name:
    Ingeberg skole
    label:
    Ingeberg skole, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.826954
    lon:
    11.130955
  4. id:
    NSR:StopPlace:36449
    name:
    Ingebergvika
    label:
    Ingebergvika, Solund
    category:

    1 results

    1. onstreetBus
    municipality:
    Solund
    county:
    Vestland
    lat:
    61.08049
    lon:
    4.868372
  5. id:
    NSR:StopPlace:10745
    name:
    Rugdevegen
    label:
    Rugdevegen, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.828451
    lon:
    11.135016
  6. id:
    NSR:StopPlace:9608
    name:
    Hagavegen
    label:
    Hagavegen, Hamar
    category:

    1 results

    1. onstreetBus
    municipality:
    Hamar
    county:
    Innlandet
    lat:
    60.827083
    lon:
    11.125956
  7. id:
    NSR:StopPlace:45938
    name:
    Inner-Berg
    label:
    Inner-Berg, Levanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Levanger
    county:
    Trøndelag
    lat:
    63.796151
    lon:
    11.134533
  8. id:
    NSR:StopPlace:52818
    name:
    Indre Berg
    label:
    Indre Berg, Storfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Storfjord
    county:
    Troms
    lat:
    69.299921
    lon:
    19.98297
  9. id:
    NSR:StopPlace:52820
    name:
    Indre Berg
    label:
    Indre Berg, Lyngen
    category:

    1 results

    1. onstreetBus
    municipality:
    Lyngen
    county:
    Troms
    lat:
    69.642894
    lon:
    19.817773
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.