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.

Parameter	Requirement	JSON type	Description
`query`	required	string	Stop name or place, e.g. "Oslo S".
`limit`	optional	integer	Maximum hits, 1-100. Unit: items.
`lang`	optional	string	Result language, normally "no" or "en".
`offset`	optional	integer	Number 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.

Result

Source: Entur. Retrieved 2026-10-01T03:18:47Z in 0.130 seconds.

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:22387
name:
Vere
label:
Vere, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.125151
lon:
6.609488
Open the place page for this point
id:
NSR:StopPlace:34653
name:
Vereide skule
label:
Vereide skule, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.809362
lon:
6.152179
Open the place page for this point
id:
NSR:StopPlace:34636
name:
Vereide kryss
label:
Vereide kryss, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.810441
lon:
6.153274
Open the place page for this point
id:
NSR:StopPlace:34684
name:
Vereide grustak
label:
Vereide grustak, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.804091
lon:
6.150156
Open the place page for this point
id:
NSR:StopPlace:34647
name:
Vereide kyrkje
label:
Vereide kyrkje, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.808069
lon:
6.141232
Open the place page for this point
id:
NSR:StopPlace:34675
name:
Vereide vest
label:
Vereide vest, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.813103
lon:
6.138517
Open the place page for this point
id:
NSR:StopPlace:34120
name:
Vereide
label:
Vereide, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.806236
lon:
6.144562
Open the place page for this point
id:
NSR:StopPlace:17070
name:
Veme
label:
Veme, Ringerike
category:
1 results
1. onstreetBus
municipality:
Ringerike
county:
Buskerud
lat:
60.2037
lon:
10.09235
Open the place page for this point
id:
NSR:StopPlace:15275
name:
Verp
label:
Verp, Øvre Eiker
category:
1 results
1. onstreetBus
municipality:
Øvre Eiker
county:
Buskerud
lat:
59.874539
lon:
9.915989
Open the place page for this point
id:
NSR:StopPlace:21510
name:
Verpe
label:
Verpe, Nome
category:
1 results
1. onstreetBus
municipality:
Nome
county:
Telemark
lat:
59.297652
lon:
9.055497
Open the place page for this point
id:
NSR:StopPlace:21515
name:
Verpe
label:
Verpe, Fyresdal
category:
1 results
1. onstreetBus
municipality:
Fyresdal
county:
Telemark
lat:
59.19979
lon:
8.08458
Open the place page for this point
id:
NSR:StopPlace:32780
name:
Vele
label:
Vele, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.592879
lon:
6.456884
Open the place page for this point
id:
NSR:StopPlace:42380
name:
Være
label:
Være, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.430915
lon:
10.567654

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

13 results

Open the place page for this point
id:
NSR:StopPlace:22387
name:
Vere
label:
Vere, Farsund
category:
1 results
1. onstreetBus
municipality:
Farsund
county:
Agder
lat:
58.125151
lon:
6.609488
Open the place page for this point
id:
NSR:StopPlace:34653
name:
Vereide skule
label:
Vereide skule, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.809362
lon:
6.152179
Open the place page for this point
id:
NSR:StopPlace:34636
name:
Vereide kryss
label:
Vereide kryss, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.810441
lon:
6.153274
Open the place page for this point
id:
NSR:StopPlace:34684
name:
Vereide grustak
label:
Vereide grustak, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.804091
lon:
6.150156
Open the place page for this point
id:
NSR:StopPlace:34647
name:
Vereide kyrkje
label:
Vereide kyrkje, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.808069
lon:
6.141232
Open the place page for this point
id:
NSR:StopPlace:34675
name:
Vereide vest
label:
Vereide vest, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.813103
lon:
6.138517
Open the place page for this point
id:
NSR:StopPlace:34120
name:
Vereide
label:
Vereide, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.806236
lon:
6.144562
Open the place page for this point
id:
NSR:StopPlace:17070
name:
Veme
label:
Veme, Ringerike
category:
1 results
1. onstreetBus
municipality:
Ringerike
county:
Buskerud
lat:
60.2037
lon:
10.09235
Open the place page for this point
id:
NSR:StopPlace:15275
name:
Verp
label:
Verp, Øvre Eiker
category:
1 results
1. onstreetBus
municipality:
Øvre Eiker
county:
Buskerud
lat:
59.874539
lon:
9.915989
Open the place page for this point
id:
NSR:StopPlace:21510
name:
Verpe
label:
Verpe, Nome
category:
1 results
1. onstreetBus
municipality:
Nome
county:
Telemark
lat:
59.297652
lon:
9.055497
Open the place page for this point
id:
NSR:StopPlace:21515
name:
Verpe
label:
Verpe, Fyresdal
category:
1 results
1. onstreetBus
municipality:
Fyresdal
county:
Telemark
lat:
59.19979
lon:
8.08458
Open the place page for this point
id:
NSR:StopPlace:32780
name:
Vele
label:
Vele, Voss
category:
1 results
1. onstreetBus
municipality:
Voss
county:
Vestland
lat:
60.592879
lon:
6.456884
Open the place page for this point
id:
NSR:StopPlace:42380
name:
Være
label:
Være, Trondheim
category:
1 results
1. onstreetBus
municipality:
Trondheim
county:
Trøndelag
lat:
63.430915
lon:
10.567654

limit:

offset:

has_more_results:

truncated:

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

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
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

Use the stop place ID for details, and distinguish scheduled times from real-time estimates.

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.

AI agent? Read the complete navigation and programming guide.