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-07T17:03:35Z in 0.208 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:57176
    name:
    Loppa kai Mevær
    label:
    Loppa kai Mevær, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.344823
    lon:
    21.452747
  2. id:
    NSR:StopPlace:58548
    name:
    Sør-Tverrfjord kai
    label:
    Sør-Tverrfjord kai, Loppa
    category:

    2 results

    1. ferryStop
    2. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.219038
    lon:
    21.716548
  3. id:
    NSR:StopPlace:57178
    name:
    Skavnakk kai Frakkfjorden
    label:
    Skavnakk kai Frakkfjorden, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.232509
    lon:
    21.422661
  4. id:
    NSR:StopPlace:57170
    name:
    Bergsfjord kai
    label:
    Bergsfjord kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.252412
    lon:
    21.783791
  5. id:
    NSR:StopPlace:57174
    name:
    Sandland kai
    label:
    Sandland kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.266644
    lon:
    21.608163
  6. id:
    NSR:StopPlace:57166
    name:
    Nuvsvåg kai
    label:
    Nuvsvåg kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.263493
    lon:
    22.105889
  7. id:
    NSR:StopPlace:57168
    name:
    Langfjordhamn kai
    label:
    Langfjordhamn kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.141003
    lon:
    21.855502
  8. id:
    NSR:StopPlace:57164
    name:
    Øksfjord hurtigbåtkai
    label:
    Øksfjord hurtigbåtkai, Loppa
    category:

    1 results

    1. ferryStop
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.238444
    lon:
    22.348516
  9. id:
    NSR:StopPlace:59707
    name:
    Tverrfjord ferjekai
    label:
    Tverrfjord ferjekai, Loppa
    category:

    2 results

    1. onstreetBus
    2. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.230396
    lon:
    22.268858
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:57176
    name:
    Loppa kai Mevær
    label:
    Loppa kai Mevær, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.344823
    lon:
    21.452747
  2. id:
    NSR:StopPlace:58548
    name:
    Sør-Tverrfjord kai
    label:
    Sør-Tverrfjord kai, Loppa
    category:

    2 results

    1. ferryStop
    2. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.219038
    lon:
    21.716548
  3. id:
    NSR:StopPlace:57178
    name:
    Skavnakk kai Frakkfjorden
    label:
    Skavnakk kai Frakkfjorden, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.232509
    lon:
    21.422661
  4. id:
    NSR:StopPlace:57170
    name:
    Bergsfjord kai
    label:
    Bergsfjord kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.252412
    lon:
    21.783791
  5. id:
    NSR:StopPlace:57174
    name:
    Sandland kai
    label:
    Sandland kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.266644
    lon:
    21.608163
  6. id:
    NSR:StopPlace:57166
    name:
    Nuvsvåg kai
    label:
    Nuvsvåg kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.263493
    lon:
    22.105889
  7. id:
    NSR:StopPlace:57168
    name:
    Langfjordhamn kai
    label:
    Langfjordhamn kai, Loppa
    category:

    1 results

    1. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.141003
    lon:
    21.855502
  8. id:
    NSR:StopPlace:57164
    name:
    Øksfjord hurtigbåtkai
    label:
    Øksfjord hurtigbåtkai, Loppa
    category:

    1 results

    1. ferryStop
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.238444
    lon:
    22.348516
  9. id:
    NSR:StopPlace:59707
    name:
    Tverrfjord ferjekai
    label:
    Tverrfjord ferjekai, Loppa
    category:

    2 results

    1. onstreetBus
    2. harbourPort
    municipality:
    Loppa
    county:
    Finnmark
    lat:
    70.230396
    lon:
    22.268858
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.