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-02T21:17:36Z in 0.411 seconds.

returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:27889
    name:
    Opstadveien
    label:
    Opstadveien, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.781056
    lon:
    5.832759
  2. id:
    NSR:StopPlace:2734
    name:
    Opstadveien 85
    label:
    Opstadveien 85, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.28341
    lon:
    11.034814
  3. id:
    NSR:StopPlace:2717
    name:
    Opstadveien 38
    label:
    Opstadveien 38, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.273754
    lon:
    11.032179
  4. id:
    NSR:StopPlace:2721
    name:
    Opstadveien 30
    label:
    Opstadveien 30, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.273464
    lon:
    11.031861
  5. id:
    NSR:StopPlace:2736
    name:
    Opstadveien 129
    label:
    Opstadveien 129, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.288633
    lon:
    11.039865
  6. id:
    NSR:StopPlace:2724
    name:
    Opstadveien Greåker vgs.
    label:
    Opstadveien Greåker vgs., Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.274882
    lon:
    11.032917
  7. id:
    NSR:StopPlace:2731
    name:
    Opstadveien 100
    label:
    Opstadveien 100, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.28316
    lon:
    11.034966
  8. id:
    NSR:StopPlace:2739
    name:
    Opstadveien 194
    label:
    Opstadveien 194, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.295323
    lon:
    11.048612
  9. id:
    NSR:StopPlace:58994
    name:
    Opstadvegen
    label:
    Opstadvegen, Hå
    category:

    1 results

    1. onstreetBus
    municipality:
    Hå
    county:
    Rogaland
    lat:
    58.632329
    lon:
    5.668063
limit:
25
offset:
0
has_more_results:
no
truncated:
no
Show all fields in HTML
returned:
9
stops:

9 results

  1. id:
    NSR:StopPlace:27889
    name:
    Opstadveien
    label:
    Opstadveien, Sandnes
    category:

    1 results

    1. onstreetBus
    municipality:
    Sandnes
    county:
    Rogaland
    lat:
    58.781056
    lon:
    5.832759
  2. id:
    NSR:StopPlace:2734
    name:
    Opstadveien 85
    label:
    Opstadveien 85, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.28341
    lon:
    11.034814
  3. id:
    NSR:StopPlace:2717
    name:
    Opstadveien 38
    label:
    Opstadveien 38, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.273754
    lon:
    11.032179
  4. id:
    NSR:StopPlace:2721
    name:
    Opstadveien 30
    label:
    Opstadveien 30, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.273464
    lon:
    11.031861
  5. id:
    NSR:StopPlace:2736
    name:
    Opstadveien 129
    label:
    Opstadveien 129, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.288633
    lon:
    11.039865
  6. id:
    NSR:StopPlace:2724
    name:
    Opstadveien Greåker vgs.
    label:
    Opstadveien Greåker vgs., Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.274882
    lon:
    11.032917
  7. id:
    NSR:StopPlace:2731
    name:
    Opstadveien 100
    label:
    Opstadveien 100, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.28316
    lon:
    11.034966
  8. id:
    NSR:StopPlace:2739
    name:
    Opstadveien 194
    label:
    Opstadveien 194, Sarpsborg
    category:

    1 results

    1. onstreetBus
    municipality:
    Sarpsborg
    county:
    Østfold
    lat:
    59.295323
    lon:
    11.048612
  9. id:
    NSR:StopPlace:58994
    name:
    Opstadvegen
    label:
    Opstadvegen, Hå
    category:

    1 results

    1. onstreetBus
    municipality:
    Hå
    county:
    Rogaland
    lat:
    58.632329
    lon:
    5.668063
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.