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-30T11:45:41Z in 0.121 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:21124
    name:
    Versto
    label:
    Versto, Vinje
    category:

    1 results

    1. onstreetBus
    municipality:
    Vinje
    county:
    Telemark
    lat:
    59.628213
    lon:
    8.01524
  2. id:
    NSR:StopPlace:10016
    name:
    Vestmo
    label:
    Vestmo, Våler
    category:

    1 results

    1. onstreetBus
    municipality:
    Våler
    county:
    Innlandet
    lat:
    60.650559
    lon:
    11.8241
  3. id:
    NSR:StopPlace:22488
    name:
    Vestøl
    label:
    Vestøl, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.861853
    lon:
    8.922455
  4. id:
    NSR:StopPlace:35937
    name:
    Vestro
    label:
    Vestro, Kinn
    category:

    1 results

    1. onstreetBus
    municipality:
    Kinn
    county:
    Vestland
    lat:
    61.954752
    lon:
    5.055087
  5. id:
    NSR:StopPlace:46438
    name:
    Verstad
    label:
    Verstad, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.925086
    lon:
    11.259321
  6. id:
    NSR:StopPlace:22178
    name:
    Vasstø
    label:
    Vasstø, Tvedestrand
    category:

    1 results

    1. onstreetBus
    municipality:
    Tvedestrand
    county:
    Agder
    lat:
    58.605547
    lon:
    8.926358
  7. id:
    NSR:StopPlace:60858
    name:
    Vestbø
    label:
    Vestbø, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.179184
    lon:
    5.814667
  8. id:
    NSR:StopPlace:50290
    name:
    Vegstøa
    label:
    Vegstøa, Vågan
    category:

    1 results

    1. onstreetBus
    municipality:
    Vågan
    county:
    Nordland
    lat:
    68.348983
    lon:
    14.744373
  9. id:
    NSR:StopPlace:35084
    name:
    Verlo
    label:
    Verlo, Stryn
    category:

    1 results

    1. onstreetBus
    municipality:
    Stryn
    county:
    Vestland
    lat:
    61.801287
    lon:
    6.523536
  10. id:
    NSR:StopPlace:30253
    name:
    Veste
    label:
    Veste, Etne
    category:

    1 results

    1. onstreetBus
    municipality:
    Etne
    county:
    Vestland
    lat:
    59.646477
    lon:
    5.849966
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:21124
    name:
    Versto
    label:
    Versto, Vinje
    category:

    1 results

    1. onstreetBus
    municipality:
    Vinje
    county:
    Telemark
    lat:
    59.628213
    lon:
    8.01524
  2. id:
    NSR:StopPlace:10016
    name:
    Vestmo
    label:
    Vestmo, Våler
    category:

    1 results

    1. onstreetBus
    municipality:
    Våler
    county:
    Innlandet
    lat:
    60.650559
    lon:
    11.8241
  3. id:
    NSR:StopPlace:22488
    name:
    Vestøl
    label:
    Vestøl, Gjerstad
    category:

    1 results

    1. onstreetBus
    municipality:
    Gjerstad
    county:
    Agder
    lat:
    58.861853
    lon:
    8.922455
  4. id:
    NSR:StopPlace:35937
    name:
    Vestro
    label:
    Vestro, Kinn
    category:

    1 results

    1. onstreetBus
    municipality:
    Kinn
    county:
    Vestland
    lat:
    61.954752
    lon:
    5.055087
  5. id:
    NSR:StopPlace:46438
    name:
    Verstad
    label:
    Verstad, Inderøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Inderøy
    county:
    Trøndelag
    lat:
    63.925086
    lon:
    11.259321
  6. id:
    NSR:StopPlace:22178
    name:
    Vasstø
    label:
    Vasstø, Tvedestrand
    category:

    1 results

    1. onstreetBus
    municipality:
    Tvedestrand
    county:
    Agder
    lat:
    58.605547
    lon:
    8.926358
  7. id:
    NSR:StopPlace:60858
    name:
    Vestbø
    label:
    Vestbø, Stavanger
    category:

    1 results

    1. onstreetBus
    municipality:
    Stavanger
    county:
    Rogaland
    lat:
    59.179184
    lon:
    5.814667
  8. id:
    NSR:StopPlace:50290
    name:
    Vegstøa
    label:
    Vegstøa, Vågan
    category:

    1 results

    1. onstreetBus
    municipality:
    Vågan
    county:
    Nordland
    lat:
    68.348983
    lon:
    14.744373
  9. id:
    NSR:StopPlace:35084
    name:
    Verlo
    label:
    Verlo, Stryn
    category:

    1 results

    1. onstreetBus
    municipality:
    Stryn
    county:
    Vestland
    lat:
    61.801287
    lon:
    6.523536
  10. id:
    NSR:StopPlace:30253
    name:
    Veste
    label:
    Veste, Etne
    category:

    1 results

    1. onstreetBus
    municipality:
    Etne
    county:
    Vestland
    lat:
    59.646477
    lon:
    5.849966
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.