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-28T12:07:10Z in 0.000 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:13935
    name:
    Hasli
    label:
    Hasli, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.764818
    lon:
    10.608035
  2. id:
    NSR:StopPlace:12674
    name:
    Hasli
    label:
    Hasli, Øyer
    category:

    1 results

    1. onstreetBus
    municipality:
    Øyer
    county:
    Innlandet
    lat:
    61.283552
    lon:
    10.356827
  3. id:
    NSR:StopPlace:21965
    name:
    Haslia
    label:
    Haslia, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.453292
    lon:
    8.248466
  4. id:
    NSR:StopPlace:14061
    name:
    Hasligrenda
    label:
    Hasligrenda, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.940192
    lon:
    10.206755
  5. id:
    NSR:StopPlace:58191
    name:
    Hasle
    label:
    Hasle, Oslo
    category:

    2 results

    1. metroStation
    2. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.923903
    lon:
    10.793032
  6. id:
    NSR:StopPlace:12648
    name:
    Haslo
    label:
    Haslo, Sør-Aurdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sør-Aurdal
    county:
    Innlandet
    lat:
    60.826173
    lon:
    9.50497
  7. id:
    NSR:StopPlace:3163
    name:
    Hasle
    label:
    Hasle, Nesodden
    category:

    1 results

    1. onstreetBus
    municipality:
    Nesodden
    county:
    Akershus
    lat:
    59.777644
    lon:
    10.689509
  8. id:
    NSR:StopPlace:12052
    name:
    Hasle
    label:
    Hasle, Gran
    category:

    1 results

    1. onstreetBus
    municipality:
    Gran
    county:
    Innlandet
    lat:
    60.340333
    lon:
    10.546052
  9. id:
    NSR:StopPlace:17851
    name:
    Hasle
    label:
    Hasle, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.098001
    lon:
    10.254426
  10. id:
    NSR:StopPlace:9928
    name:
    Hasla
    label:
    Hasla, Våler
    category:

    1 results

    1. onstreetBus
    municipality:
    Våler
    county:
    Innlandet
    lat:
    60.698357
    lon:
    11.900776
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:13935
    name:
    Hasli
    label:
    Hasli, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.764818
    lon:
    10.608035
  2. id:
    NSR:StopPlace:12674
    name:
    Hasli
    label:
    Hasli, Øyer
    category:

    1 results

    1. onstreetBus
    municipality:
    Øyer
    county:
    Innlandet
    lat:
    61.283552
    lon:
    10.356827
  3. id:
    NSR:StopPlace:21965
    name:
    Haslia
    label:
    Haslia, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.453292
    lon:
    8.248466
  4. id:
    NSR:StopPlace:14061
    name:
    Hasligrenda
    label:
    Hasligrenda, Gjøvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjøvik
    county:
    Innlandet
    lat:
    60.940192
    lon:
    10.206755
  5. id:
    NSR:StopPlace:58191
    name:
    Hasle
    label:
    Hasle, Oslo
    category:

    2 results

    1. metroStation
    2. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.923903
    lon:
    10.793032
  6. id:
    NSR:StopPlace:12648
    name:
    Haslo
    label:
    Haslo, Sør-Aurdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sør-Aurdal
    county:
    Innlandet
    lat:
    60.826173
    lon:
    9.50497
  7. id:
    NSR:StopPlace:3163
    name:
    Hasle
    label:
    Hasle, Nesodden
    category:

    1 results

    1. onstreetBus
    municipality:
    Nesodden
    county:
    Akershus
    lat:
    59.777644
    lon:
    10.689509
  8. id:
    NSR:StopPlace:12052
    name:
    Hasle
    label:
    Hasle, Gran
    category:

    1 results

    1. onstreetBus
    municipality:
    Gran
    county:
    Innlandet
    lat:
    60.340333
    lon:
    10.546052
  9. id:
    NSR:StopPlace:17851
    name:
    Hasle
    label:
    Hasle, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.098001
    lon:
    10.254426
  10. id:
    NSR:StopPlace:9928
    name:
    Hasla
    label:
    Hasla, Våler
    category:

    1 results

    1. onstreetBus
    municipality:
    Våler
    county:
    Innlandet
    lat:
    60.698357
    lon:
    11.900776
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.