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-03T09:34:33Z in 0.171 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:54017
name:
Langberget
label:
Langberget, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.294217
lon:
17.799592
Open the place page for this point
id:
NSR:StopPlace:54014
name:
Langberget
label:
Langberget, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.676914
lon:
16.765439
Open the place page for this point
id:
NSR:StopPlace:56583
name:
Perhansanes Langberget
label:
Perhansanes Langberget, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.280018
lon:
18.672775
Open the place page for this point
id:
NSR:StopPlace:64219
name:
Langeberget
label:
Langeberget, Masfjorden
category:
1 results
1. onstreetBus
municipality:
Masfjorden
county:
Vestland
lat:
60.844491
lon:
5.147473
Open the place page for this point
id:
NSR:StopPlace:6587
name:
Låkeberget
label:
Låkeberget, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.979967
lon:
10.757226
Open the place page for this point
id:
NSR:StopPlace:64444
name:
Landaberget
label:
Landaberget, Time
category:
1 results
1. onstreetBus
municipality:
Time
county:
Rogaland
lat:
58.704025
lon:
5.760917
Open the place page for this point
id:
NSR:StopPlace:54193
name:
Laupberget
label:
Laupberget, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.931311
lon:
16.633962
Open the place page for this point
id:
NSR:StopPlace:53872
name:
Laberget
label:
Laberget, Ibestad
category:
1 results
1. onstreetBus
municipality:
Ibestad
county:
Troms
lat:
68.831673
lon:
17.071792
Open the place page for this point
id:
NSR:StopPlace:53869
name:
Laberget
label:
Laberget, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.641038
lon:
17.170485
Open the place page for this point
id:
NSR:StopPlace:53875
name:
Laberget
label:
Laberget, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.676652
lon:
17.509382
Open the place page for this point
id:
NSR:StopPlace:26988
name:
Laberget
label:
Laberget, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.862634
lon:
5.754606
Open the place page for this point
id:
NSR:StopPlace:45068
name:
Laberget
label:
Laberget, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.7052
lon:
11.137825

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:54017
name:
Langberget
label:
Langberget, Senja
category:
1 results
1. onstreetBus
municipality:
Senja
county:
Troms
lat:
69.294217
lon:
17.799592
Open the place page for this point
id:
NSR:StopPlace:54014
name:
Langberget
label:
Langberget, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.676914
lon:
16.765439
Open the place page for this point
id:
NSR:StopPlace:56583
name:
Perhansanes Langberget
label:
Perhansanes Langberget, Målselv
category:
1 results
1. onstreetBus
municipality:
Målselv
county:
Troms
lat:
69.280018
lon:
18.672775
Open the place page for this point
id:
NSR:StopPlace:64219
name:
Langeberget
label:
Langeberget, Masfjorden
category:
1 results
1. onstreetBus
municipality:
Masfjorden
county:
Vestland
lat:
60.844491
lon:
5.147473
Open the place page for this point
id:
NSR:StopPlace:6587
name:
Låkeberget
label:
Låkeberget, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.979967
lon:
10.757226
Open the place page for this point
id:
NSR:StopPlace:64444
name:
Landaberget
label:
Landaberget, Time
category:
1 results
1. onstreetBus
municipality:
Time
county:
Rogaland
lat:
58.704025
lon:
5.760917
Open the place page for this point
id:
NSR:StopPlace:54193
name:
Laupberget
label:
Laupberget, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.931311
lon:
16.633962
Open the place page for this point
id:
NSR:StopPlace:53872
name:
Laberget
label:
Laberget, Ibestad
category:
1 results
1. onstreetBus
municipality:
Ibestad
county:
Troms
lat:
68.831673
lon:
17.071792
Open the place page for this point
id:
NSR:StopPlace:53869
name:
Laberget
label:
Laberget, Tjeldsund
category:
1 results
1. onstreetBus
municipality:
Tjeldsund
county:
Troms
lat:
68.641038
lon:
17.170485
Open the place page for this point
id:
NSR:StopPlace:53875
name:
Laberget
label:
Laberget, Gratangen
category:
1 results
1. onstreetBus
municipality:
Gratangen
county:
Troms
lat:
68.676652
lon:
17.509382
Open the place page for this point
id:
NSR:StopPlace:26988
name:
Laberget
label:
Laberget, Sandnes
category:
1 results
1. onstreetBus
municipality:
Sandnes
county:
Rogaland
lat:
58.862634
lon:
5.754606
Open the place page for this point
id:
NSR:StopPlace:45068
name:
Laberget
label:
Laberget, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.7052
lon:
11.137825

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.