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-10-06T13:43:36Z in 0.308 seconds.

returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:26675
    name:
    Håbakk
    label:
    Håbakk, Strand
    category:

    1 results

    1. onstreetBus
    municipality:
    Strand
    county:
    Rogaland
    lat:
    59.050492
    lon:
    5.921062
  2. id:
    NSR:StopPlace:34537
    name:
    Håbakken
    label:
    Håbakken, Lærdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Lærdal
    county:
    Vestland
    lat:
    61.064069
    lon:
    7.508723
  3. id:
    NSR:StopPlace:26686
    name:
    Håbakken
    label:
    Håbakken, Randaberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Randaberg
    county:
    Rogaland
    lat:
    59.028541
    lon:
    5.587023
  4. id:
    NSR:StopPlace:26680
    name:
    Håbakken
    label:
    Håbakken, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.81086
    lon:
    5.695655
  5. id:
    NSR:StopPlace:26683
    name:
    Håbakken
    label:
    Håbakken, Klepp
    category:

    1 results

    1. onstreetBus
    municipality:
    Klepp
    county:
    Rogaland
    lat:
    58.784095
    lon:
    5.71104
  6. id:
    NSR:StopPlace:17760
    name:
    Habakken
    label:
    Habakken, Larvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Larvik
    county:
    Vestfold
    lat:
    59.03075
    lon:
    9.856649
  7. id:
    NSR:StopPlace:4031
    name:
    Haubakk
    label:
    Haubakk, Aurskog-Høland
    category:

    1 results

    1. onstreetBus
    municipality:
    Aurskog-Høland
    county:
    Akershus
    lat:
    59.748632
    lon:
    11.489683
  8. id:
    NSR:StopPlace:49308
    name:
    Haubakk
    label:
    Haubakk, Beiarn
    category:

    1 results

    1. onstreetBus
    municipality:
    Beiarn
    county:
    Nordland
    lat:
    66.979284
    lon:
    14.787019
  9. id:
    NSR:StopPlace:21899
    name:
    Harbakk
    label:
    Harbakk, Kvinesdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinesdal
    county:
    Agder
    lat:
    58.541727
    lon:
    6.96604
  10. id:
    NSR:StopPlace:16966
    name:
    Hulbakk
    label:
    Hulbakk, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.945602
    lon:
    9.815716
  11. id:
    NSR:StopPlace:15021
    name:
    Høybakk
    label:
    Høybakk, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.9212
    lon:
    9.91551
  12. id:
    NSR:StopPlace:1704
    name:
    Harebakk
    label:
    Harebakk, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.301153
    lon:
    11.120184
  13. id:
    NSR:StopPlace:42161
    name:
    Harbak
    label:
    Harbak, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    63.924111
    lon:
    10.049558
  14. id:
    NSR:StopPlace:42441
    name:
    Harbak
    label:
    Harbak, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    64.080129
    lon:
    10.044964
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
14
stops:

14 results

  1. id:
    NSR:StopPlace:26675
    name:
    Håbakk
    label:
    Håbakk, Strand
    category:

    1 results

    1. onstreetBus
    municipality:
    Strand
    county:
    Rogaland
    lat:
    59.050492
    lon:
    5.921062
  2. id:
    NSR:StopPlace:34537
    name:
    Håbakken
    label:
    Håbakken, Lærdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Lærdal
    county:
    Vestland
    lat:
    61.064069
    lon:
    7.508723
  3. id:
    NSR:StopPlace:26686
    name:
    Håbakken
    label:
    Håbakken, Randaberg
    category:

    1 results

    1. onstreetBus
    municipality:
    Randaberg
    county:
    Rogaland
    lat:
    59.028541
    lon:
    5.587023
  4. id:
    NSR:StopPlace:26680
    name:
    Håbakken
    label:
    Håbakken, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.81086
    lon:
    5.695655
  5. id:
    NSR:StopPlace:26683
    name:
    Håbakken
    label:
    Håbakken, Klepp
    category:

    1 results

    1. onstreetBus
    municipality:
    Klepp
    county:
    Rogaland
    lat:
    58.784095
    lon:
    5.71104
  6. id:
    NSR:StopPlace:17760
    name:
    Habakken
    label:
    Habakken, Larvik
    category:

    1 results

    1. onstreetBus
    municipality:
    Larvik
    county:
    Vestfold
    lat:
    59.03075
    lon:
    9.856649
  7. id:
    NSR:StopPlace:4031
    name:
    Haubakk
    label:
    Haubakk, Aurskog-Høland
    category:

    1 results

    1. onstreetBus
    municipality:
    Aurskog-Høland
    county:
    Akershus
    lat:
    59.748632
    lon:
    11.489683
  8. id:
    NSR:StopPlace:49308
    name:
    Haubakk
    label:
    Haubakk, Beiarn
    category:

    1 results

    1. onstreetBus
    municipality:
    Beiarn
    county:
    Nordland
    lat:
    66.979284
    lon:
    14.787019
  9. id:
    NSR:StopPlace:21899
    name:
    Harbakk
    label:
    Harbakk, Kvinesdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Kvinesdal
    county:
    Agder
    lat:
    58.541727
    lon:
    6.96604
  10. id:
    NSR:StopPlace:16966
    name:
    Hulbakk
    label:
    Hulbakk, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.945602
    lon:
    9.815716
  11. id:
    NSR:StopPlace:15021
    name:
    Høybakk
    label:
    Høybakk, Modum
    category:

    1 results

    1. onstreetBus
    municipality:
    Modum
    county:
    Buskerud
    lat:
    59.9212
    lon:
    9.91551
  12. id:
    NSR:StopPlace:1704
    name:
    Harebakk
    label:
    Harebakk, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.301153
    lon:
    11.120184
  13. id:
    NSR:StopPlace:42161
    name:
    Harbak
    label:
    Harbak, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    63.924111
    lon:
    10.049558
  14. id:
    NSR:StopPlace:42441
    name:
    Harbak
    label:
    Harbak, Åfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Åfjord
    county:
    Trøndelag
    lat:
    64.080129
    lon:
    10.044964
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.