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-01T02:39:05Z in 0.612 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:23542
    name:
    Stie
    label:
    Stie, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.454824
    lon:
    8.331282
  2. id:
    NSR:StopPlace:27311
    name:
    Stie
    label:
    Stie, Eigersund
    category:

    1 results

    1. onstreetBus
    municipality:
    Eigersund
    county:
    Rogaland
    lat:
    58.464118
    lon:
    5.937075
  3. id:
    NSR:StopPlace:63541
    name:
    Stien
    label:
    Stien, Vegårshei
    category:

    1 results

    1. onstreetBus
    municipality:
    Vegårshei
    county:
    Agder
    lat:
    58.746907
    lon:
    8.746029
  4. id:
    NSR:StopPlace:70215
    name:
    Stien
    label:
    Stien, Dyrøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Dyrøy
    county:
    Troms
    lat:
    68.981885
    lon:
    17.52862
  5. id:
    NSR:StopPlace:23545
    name:
    Stien
    label:
    Stien, Froland
    category:

    1 results

    1. onstreetBus
    municipality:
    Froland
    county:
    Agder
    lat:
    58.516698
    lon:
    8.619764
  6. id:
    NSR:StopPlace:51116
    name:
    Stienget
    label:
    Stienget, Hemnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Hemnes
    county:
    Nordland
    lat:
    66.162823
    lon:
    13.955487
  7. id:
    NSR:StopPlace:50716
    name:
    Stia
    label:
    Stia, Meløy
    category:

    1 results

    1. onstreetBus
    municipality:
    Meløy
    county:
    Nordland
    lat:
    66.888996
    lon:
    13.652798
  8. id:
    NSR:StopPlace:6013
    name:
    Stig
    label:
    Stig, Oslo
    category:

    1 results

    1. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.947207
    lon:
    10.817694
  9. id:
    NSR:StopPlace:59445
    name:
    Stige
    label:
    Stige, Ålesund
    category:

    1 results

    1. onstreetBus
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.534861
    lon:
    6.658471
  10. id:
    NSR:StopPlace:18600
    name:
    Sti
    label:
    Sti, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.216891
    lon:
    10.136283
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:23542
    name:
    Stie
    label:
    Stie, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.454824
    lon:
    8.331282
  2. id:
    NSR:StopPlace:27311
    name:
    Stie
    label:
    Stie, Eigersund
    category:

    1 results

    1. onstreetBus
    municipality:
    Eigersund
    county:
    Rogaland
    lat:
    58.464118
    lon:
    5.937075
  3. id:
    NSR:StopPlace:63541
    name:
    Stien
    label:
    Stien, Vegårshei
    category:

    1 results

    1. onstreetBus
    municipality:
    Vegårshei
    county:
    Agder
    lat:
    58.746907
    lon:
    8.746029
  4. id:
    NSR:StopPlace:70215
    name:
    Stien
    label:
    Stien, Dyrøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Dyrøy
    county:
    Troms
    lat:
    68.981885
    lon:
    17.52862
  5. id:
    NSR:StopPlace:23545
    name:
    Stien
    label:
    Stien, Froland
    category:

    1 results

    1. onstreetBus
    municipality:
    Froland
    county:
    Agder
    lat:
    58.516698
    lon:
    8.619764
  6. id:
    NSR:StopPlace:51116
    name:
    Stienget
    label:
    Stienget, Hemnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Hemnes
    county:
    Nordland
    lat:
    66.162823
    lon:
    13.955487
  7. id:
    NSR:StopPlace:50716
    name:
    Stia
    label:
    Stia, Meløy
    category:

    1 results

    1. onstreetBus
    municipality:
    Meløy
    county:
    Nordland
    lat:
    66.888996
    lon:
    13.652798
  8. id:
    NSR:StopPlace:6013
    name:
    Stig
    label:
    Stig, Oslo
    category:

    1 results

    1. onstreetBus
    municipality:
    Oslo
    county:
    Oslo
    lat:
    59.947207
    lon:
    10.817694
  9. id:
    NSR:StopPlace:59445
    name:
    Stige
    label:
    Stige, Ålesund
    category:

    1 results

    1. onstreetBus
    municipality:
    Ålesund
    county:
    Møre og Romsdal
    lat:
    62.534861
    lon:
    6.658471
  10. id:
    NSR:StopPlace:18600
    name:
    Sti
    label:
    Sti, Sandefjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandefjord
    county:
    Vestfold
    lat:
    59.216891
    lon:
    10.136283
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.