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-28T20:30:37Z in 0.420 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:21569
    name:
    Veting
    label:
    Veting, Kviteseid
    category:

    1 results

    1. onstreetBus
    municipality:
    Kviteseid
    county:
    Telemark
    lat:
    59.442039
    lon:
    8.522707
  2. id:
    NSR:StopPlace:50034
    name:
    Vetting
    label:
    Vetting, Vestvågøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Vestvågøy
    county:
    Nordland
    lat:
    68.098811
    lon:
    13.472109
  3. id:
    NSR:StopPlace:22717
    name:
    Væting
    label:
    Væting, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.459077
    lon:
    8.267534
  4. id:
    NSR:StopPlace:3897
    name:
    Vesteng
    label:
    Vesteng, Aurskog-Høland
    category:

    1 results

    1. onstreetBus
    municipality:
    Aurskog-Høland
    county:
    Akershus
    lat:
    59.805388
    lon:
    11.430185
  5. id:
    NSR:StopPlace:10021
    name:
    Vesteng
    label:
    Vesteng, Ringsaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringsaker
    county:
    Innlandet
    lat:
    60.873812
    lon:
    11.022278
  6. id:
    NSR:StopPlace:22712
    name:
    Væding
    label:
    Væding, Arendal
    category:

    1 results

    1. onstreetBus
    municipality:
    Arendal
    county:
    Agder
    lat:
    58.418249
    lon:
    8.678538
  7. id:
    NSR:StopPlace:52875
    name:
    Vesteng
    label:
    Vesteng, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    69.022934
    lon:
    18.785296
  8. id:
    NSR:StopPlace:38004
    name:
    Vevang
    label:
    Vevang, Hustadvika
    category:

    1 results

    1. onstreetBus
    municipality:
    Hustadvika
    county:
    Møre og Romsdal
    lat:
    63.003959
    lon:
    7.294214
  9. id:
    NSR:StopPlace:17961
    name:
    Vetan
    label:
    Vetan, Færder
    category:

    1 results

    1. onstreetBus
    municipality:
    Færder
    county:
    Vestfold
    lat:
    59.175174
    lon:
    10.430277
  10. id:
    NSR:StopPlace:35076
    name:
    Veten
    label:
    Veten, Sogndal
    category:

    1 results

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

10 results

  1. id:
    NSR:StopPlace:21569
    name:
    Veting
    label:
    Veting, Kviteseid
    category:

    1 results

    1. onstreetBus
    municipality:
    Kviteseid
    county:
    Telemark
    lat:
    59.442039
    lon:
    8.522707
  2. id:
    NSR:StopPlace:50034
    name:
    Vetting
    label:
    Vetting, Vestvågøy
    category:

    1 results

    1. onstreetBus
    municipality:
    Vestvågøy
    county:
    Nordland
    lat:
    68.098811
    lon:
    13.472109
  3. id:
    NSR:StopPlace:22717
    name:
    Væting
    label:
    Væting, Birkenes
    category:

    1 results

    1. onstreetBus
    municipality:
    Birkenes
    county:
    Agder
    lat:
    58.459077
    lon:
    8.267534
  4. id:
    NSR:StopPlace:3897
    name:
    Vesteng
    label:
    Vesteng, Aurskog-Høland
    category:

    1 results

    1. onstreetBus
    municipality:
    Aurskog-Høland
    county:
    Akershus
    lat:
    59.805388
    lon:
    11.430185
  5. id:
    NSR:StopPlace:10021
    name:
    Vesteng
    label:
    Vesteng, Ringsaker
    category:

    1 results

    1. onstreetBus
    municipality:
    Ringsaker
    county:
    Innlandet
    lat:
    60.873812
    lon:
    11.022278
  6. id:
    NSR:StopPlace:22712
    name:
    Væding
    label:
    Væding, Arendal
    category:

    1 results

    1. onstreetBus
    municipality:
    Arendal
    county:
    Agder
    lat:
    58.418249
    lon:
    8.678538
  7. id:
    NSR:StopPlace:52875
    name:
    Vesteng
    label:
    Vesteng, Målselv
    category:

    1 results

    1. onstreetBus
    municipality:
    Målselv
    county:
    Troms
    lat:
    69.022934
    lon:
    18.785296
  8. id:
    NSR:StopPlace:38004
    name:
    Vevang
    label:
    Vevang, Hustadvika
    category:

    1 results

    1. onstreetBus
    municipality:
    Hustadvika
    county:
    Møre og Romsdal
    lat:
    63.003959
    lon:
    7.294214
  9. id:
    NSR:StopPlace:17961
    name:
    Vetan
    label:
    Vetan, Færder
    category:

    1 results

    1. onstreetBus
    municipality:
    Færder
    county:
    Vestfold
    lat:
    59.175174
    lon:
    10.430277
  10. id:
    NSR:StopPlace:35076
    name:
    Veten
    label:
    Veten, Sogndal
    category:

    1 results

    1. onstreetBus
    municipality:
    Sogndal
    county:
    Vestland
    lat:
    61.182432
    lon:
    6.774174
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.