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-09-30T17:13:46Z in 0.129 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:44498
name:
Devika
label:
Devika, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.631739
lon:
11.134775
Open the place page for this point
id:
NSR:StopPlace:44322
name:
Devika
label:
Devika, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.245734
lon:
13.759189
Open the place page for this point
id:
NSR:StopPlace:44216
name:
Devika Slåttnes
label:
Devika Slåttnes, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.777146
lon:
13.680233
Open the place page for this point
id:
NSR:StopPlace:25580
name:
Dyvika
label:
Dyvika, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.478356
lon:
8.824611
Open the place page for this point
id:
NSR:StopPlace:34153
name:
Devik
label:
Devik, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.825964
lon:
6.056531
Open the place page for this point
id:
NSR:StopPlace:28820
name:
Døvika
label:
Døvika, Hjelmeland
category:
1 results
1. onstreetBus
municipality:
Hjelmeland
county:
Rogaland
lat:
59.207759
lon:
6.09756
Open the place page for this point
id:
NSR:StopPlace:56329
name:
Dalvika
label:
Dalvika, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.936305
lon:
16.350906
Open the place page for this point
id:
NSR:StopPlace:34460
name:
Davik
label:
Davik, Bremanger
category:
1 results
1. onstreetBus
municipality:
Bremanger
county:
Vestland
lat:
61.888192
lon:
5.539186
Open the place page for this point
id:
NSR:StopPlace:25582
name:
Dyvik
label:
Dyvik, Lillesand
category:
1 results
1. onstreetBus
municipality:
Lillesand
county:
Agder
lat:
58.26507
lon:
8.409846
Open the place page for this point
id:
NSR:StopPlace:28819
name:
Døvik
label:
Døvik, Strand
category:
1 results
1. onstreetBus
municipality:
Strand
county:
Rogaland
lat:
59.133006
lon:
6.097028
Open the place page for this point
id:
NSR:StopPlace:30061
name:
Dyvik
label:
Dyvik, Stord
category:
1 results
1. onstreetBus
municipality:
Stord
county:
Vestland
lat:
59.791636
lon:
5.372562
Open the place page for this point
id:
NSR:StopPlace:44202
name:
Devla
label:
Devla, Stjørdal
category:
1 results
1. onstreetBus
municipality:
Stjørdal
county:
Trøndelag
lat:
63.500461
lon:
10.900001

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:44498
name:
Devika
label:
Devika, Namsos
category:
1 results
1. onstreetBus
municipality:
Namsos
county:
Trøndelag
lat:
64.631739
lon:
11.134775
Open the place page for this point
id:
NSR:StopPlace:44322
name:
Devika
label:
Devika, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.245734
lon:
13.759189
Open the place page for this point
id:
NSR:StopPlace:44216
name:
Devika Slåttnes
label:
Devika Slåttnes, Lierne
category:
1 results
1. onstreetBus
municipality:
Lierne
county:
Trøndelag
lat:
64.777146
lon:
13.680233
Open the place page for this point
id:
NSR:StopPlace:25580
name:
Dyvika
label:
Dyvika, Arendal
category:
1 results
1. onstreetBus
municipality:
Arendal
county:
Agder
lat:
58.478356
lon:
8.824611
Open the place page for this point
id:
NSR:StopPlace:34153
name:
Devik
label:
Devik, Gloppen
category:
1 results
1. onstreetBus
municipality:
Gloppen
county:
Vestland
lat:
61.825964
lon:
6.056531
Open the place page for this point
id:
NSR:StopPlace:28820
name:
Døvika
label:
Døvika, Hjelmeland
category:
1 results
1. onstreetBus
municipality:
Hjelmeland
county:
Rogaland
lat:
59.207759
lon:
6.09756
Open the place page for this point
id:
NSR:StopPlace:56329
name:
Dalvika
label:
Dalvika, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.936305
lon:
16.350906
Open the place page for this point
id:
NSR:StopPlace:34460
name:
Davik
label:
Davik, Bremanger
category:
1 results
1. onstreetBus
municipality:
Bremanger
county:
Vestland
lat:
61.888192
lon:
5.539186
Open the place page for this point
id:
NSR:StopPlace:25582
name:
Dyvik
label:
Dyvik, Lillesand
category:
1 results
1. onstreetBus
municipality:
Lillesand
county:
Agder
lat:
58.26507
lon:
8.409846
Open the place page for this point
id:
NSR:StopPlace:28819
name:
Døvik
label:
Døvik, Strand
category:
1 results
1. onstreetBus
municipality:
Strand
county:
Rogaland
lat:
59.133006
lon:
6.097028
Open the place page for this point
id:
NSR:StopPlace:30061
name:
Dyvik
label:
Dyvik, Stord
category:
1 results
1. onstreetBus
municipality:
Stord
county:
Vestland
lat:
59.791636
lon:
5.372562
Open the place page for this point
id:
NSR:StopPlace:44202
name:
Devla
label:
Devla, Stjørdal
category:
1 results
1. onstreetBus
municipality:
Stjørdal
county:
Trøndelag
lat:
63.500461
lon:
10.900001

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.