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-03T17:39:18Z in 0.165 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:24461
    name:
    Trøe
    label:
    Trøe, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.209472
    lon:
    8.254137
  2. id:
    NSR:StopPlace:45159
    name:
    Trøen
    label:
    Trøen, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.818035
    lon:
    11.962947
  3. id:
    NSR:StopPlace:41456
    name:
    Trøen
    label:
    Trøen, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.812057
    lon:
    7.709025
  4. id:
    NSR:StopPlace:22486
    name:
    Trøe vest
    label:
    Trøe vest, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.207612
    lon:
    8.251335
  5. id:
    NSR:StopPlace:24462
    name:
    Trøestranda
    label:
    Trøestranda, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.211197
    lon:
    8.2527
  6. id:
    NSR:StopPlace:45665
    name:
    Trøa
    label:
    Trøa, Steinkjer
    category:

    1 results

    1. onstreetBus
    municipality:
    Steinkjer
    county:
    Trøndelag
    lat:
    64.075589
    lon:
    11.513422
  7. id:
    NSR:StopPlace:8204
    name:
    Trøa
    label:
    Trøa, Os
    category:

    1 results

    1. onstreetBus
    municipality:
    Os
    county:
    Innlandet
    lat:
    62.533252
    lon:
    11.1141
  8. id:
    NSR:StopPlace:39464
    name:
    Trøa
    label:
    Trøa, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.436291
    lon:
    7.857436
  9. id:
    NSR:StopPlace:15646
    name:
    Trøo
    label:
    Trøo, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.549979
    lon:
    8.245867
  10. id:
    NSR:StopPlace:30225
    name:
    Tre
    label:
    Tre, Stord
    category:

    1 results

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

10 results

  1. id:
    NSR:StopPlace:24461
    name:
    Trøe
    label:
    Trøe, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.209472
    lon:
    8.254137
  2. id:
    NSR:StopPlace:45159
    name:
    Trøen
    label:
    Trøen, Verdal
    category:

    1 results

    1. onstreetBus
    municipality:
    Verdal
    county:
    Trøndelag
    lat:
    63.818035
    lon:
    11.962947
  3. id:
    NSR:StopPlace:41456
    name:
    Trøen
    label:
    Trøen, Molde
    category:

    1 results

    1. onstreetBus
    municipality:
    Molde
    county:
    Møre og Romsdal
    lat:
    62.812057
    lon:
    7.709025
  4. id:
    NSR:StopPlace:22486
    name:
    Trøe vest
    label:
    Trøe vest, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.207612
    lon:
    8.251335
  5. id:
    NSR:StopPlace:24462
    name:
    Trøestranda
    label:
    Trøestranda, Lillesand
    category:

    1 results

    1. onstreetBus
    municipality:
    Lillesand
    county:
    Agder
    lat:
    58.211197
    lon:
    8.2527
  6. id:
    NSR:StopPlace:45665
    name:
    Trøa
    label:
    Trøa, Steinkjer
    category:

    1 results

    1. onstreetBus
    municipality:
    Steinkjer
    county:
    Trøndelag
    lat:
    64.075589
    lon:
    11.513422
  7. id:
    NSR:StopPlace:8204
    name:
    Trøa
    label:
    Trøa, Os
    category:

    1 results

    1. onstreetBus
    municipality:
    Os
    county:
    Innlandet
    lat:
    62.533252
    lon:
    11.1141
  8. id:
    NSR:StopPlace:39464
    name:
    Trøa
    label:
    Trøa, Rauma
    category:

    1 results

    1. onstreetBus
    municipality:
    Rauma
    county:
    Møre og Romsdal
    lat:
    62.436291
    lon:
    7.857436
  9. id:
    NSR:StopPlace:15646
    name:
    Trøo
    label:
    Trøo, Hol
    category:

    1 results

    1. onstreetBus
    municipality:
    Hol
    county:
    Buskerud
    lat:
    60.549979
    lon:
    8.245867
  10. id:
    NSR:StopPlace:30225
    name:
    Tre
    label:
    Tre, Stord
    category:

    1 results

    1. onstreetBus
    municipality:
    Stord
    county:
    Vestland
    lat:
    59.847823
    lon:
    5.604475
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.