search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
langoptionalstringResult language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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. Through this API: default 25, maximum 100.
Type: one of: no, nb, nn, en. Result language: "no" (default), "nb", "nn" or "en".

Result

Source: Entur. Retrieved 2026-11-13T03:47:02Z in 0.164 seconds.

returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:20827
    name:
    Nystrand
    label:
    Nystrand, Porsgrunn
    category:

    1 results

    1. onstreetBus
    municipality:
    Porsgrunn
    county:
    Telemark
    lat:
    59.108083
    lon:
    9.700378
  2. id:
    NSR:StopPlace:48908
    name:
    Nystad
    label:
    Nystad, Grane
    category:

    1 results

    1. onstreetBus
    municipality:
    Grane
    county:
    Nordland
    lat:
    65.563637
    lon:
    13.40235
  3. id:
    NSR:StopPlace:50793
    name:
    Nystad
    label:
    Nystad, Fauske
    category:

    1 results

    1. onstreetBus
    municipality:
    Fauske
    county:
    Nordland
    lat:
    67.335178
    lon:
    15.260872
  4. id:
    NSR:StopPlace:56473
    name:
    Nystad
    label:
    Nystad, Lavangen
    category:

    1 results

    1. onstreetBus
    municipality:
    Lavangen
    county:
    Troms
    lat:
    68.769682
    lon:
    17.753367
  5. id:
    NSR:StopPlace:49332
    name:
    Nystad
    label:
    Nystad, Bodø
    category:

    1 results

    1. onstreetBus
    municipality:
    Bodø
    county:
    Nordland
    lat:
    67.291891
    lon:
    14.634985
  6. id:
    NSR:StopPlace:56476
    name:
    Nystad
    label:
    Nystad, Storfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Storfjord
    county:
    Troms
    lat:
    69.206127
    lon:
    19.977891
  7. id:
    NSR:StopPlace:56472
    name:
    Nystad
    label:
    Nystad, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    70.022064
    lon:
    18.757355
  8. id:
    NSR:StopPlace:56475
    name:
    Nystad
    label:
    Nystad, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.207663
    lon:
    17.574597
  9. id:
    NSR:StopPlace:56474
    name:
    Nystad
    label:
    Nystad, Sørreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Sørreisa
    county:
    Troms
    lat:
    69.087449
    lon:
    18.354692
  10. id:
    NSR:StopPlace:50709
    name:
    Nystad
    label:
    Nystad, Meløy
    category:

    1 results

    1. onstreetBus
    municipality:
    Meløy
    county:
    Nordland
    lat:
    66.842878
    lon:
    13.758371
Show all fields in HTML
returned:
10
stops:

10 results

  1. id:
    NSR:StopPlace:20827
    name:
    Nystrand
    label:
    Nystrand, Porsgrunn
    category:

    1 results

    1. onstreetBus
    municipality:
    Porsgrunn
    county:
    Telemark
    lat:
    59.108083
    lon:
    9.700378
  2. id:
    NSR:StopPlace:48908
    name:
    Nystad
    label:
    Nystad, Grane
    category:

    1 results

    1. onstreetBus
    municipality:
    Grane
    county:
    Nordland
    lat:
    65.563637
    lon:
    13.40235
  3. id:
    NSR:StopPlace:50793
    name:
    Nystad
    label:
    Nystad, Fauske
    category:

    1 results

    1. onstreetBus
    municipality:
    Fauske
    county:
    Nordland
    lat:
    67.335178
    lon:
    15.260872
  4. id:
    NSR:StopPlace:56473
    name:
    Nystad
    label:
    Nystad, Lavangen
    category:

    1 results

    1. onstreetBus
    municipality:
    Lavangen
    county:
    Troms
    lat:
    68.769682
    lon:
    17.753367
  5. id:
    NSR:StopPlace:49332
    name:
    Nystad
    label:
    Nystad, Bodø
    category:

    1 results

    1. onstreetBus
    municipality:
    Bodø
    county:
    Nordland
    lat:
    67.291891
    lon:
    14.634985
  6. id:
    NSR:StopPlace:56476
    name:
    Nystad
    label:
    Nystad, Storfjord
    category:

    1 results

    1. onstreetBus
    municipality:
    Storfjord
    county:
    Troms
    lat:
    69.206127
    lon:
    19.977891
  7. id:
    NSR:StopPlace:56472
    name:
    Nystad
    label:
    Nystad, Tromsø
    category:

    1 results

    1. onstreetBus
    municipality:
    Tromsø
    county:
    Troms
    lat:
    70.022064
    lon:
    18.757355
  8. id:
    NSR:StopPlace:56475
    name:
    Nystad
    label:
    Nystad, Senja
    category:

    1 results

    1. onstreetBus
    municipality:
    Senja
    county:
    Troms
    lat:
    69.207663
    lon:
    17.574597
  9. id:
    NSR:StopPlace:56474
    name:
    Nystad
    label:
    Nystad, Sørreisa
    category:

    1 results

    1. onstreetBus
    municipality:
    Sørreisa
    county:
    Troms
    lat:
    69.087449
    lon:
    18.354692
  10. id:
    NSR:StopPlace:50709
    name:
    Nystad
    label:
    Nystad, Meløy
    category:

    1 results

    1. onstreetBus
    municipality:
    Meløy
    county:
    Nordland
    lat:
    66.842878
    lon:
    13.758371
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.