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-03T11:10:51Z in 0.145 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:1501
name:
Tomta
label:
Tomta, Sarpsborg
category:
1 results
1. onstreetBus
municipality:
Sarpsborg
county:
Østfold
lat:
59.379952
lon:
11.215849
Open the place page for this point
id:
NSR:StopPlace:7915
name:
Tomtan
label:
Tomtan, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.200843
lon:
10.307291
Open the place page for this point
id:
NSR:StopPlace:14881
name:
Tomta Geithus
label:
Tomta Geithus, Modum
category:
1 results
1. onstreetBus
municipality:
Modum
county:
Buskerud
lat:
59.92478
lon:
9.96652
Open the place page for this point
id:
NSR:StopPlace:61467
name:
Vy-tomta
label:
Vy-tomta, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.910266
lon:
10.714851
Open the place page for this point
id:
NSR:StopPlace:24883
name:
Birkeland Tomta
label:
Birkeland Tomta, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.330576
lon:
8.231742
Open the place page for this point
id:
NSR:StopPlace:39287
name:
Tomra
label:
Tomra, Vestnes
category:
1 results
1. onstreetBus
municipality:
Vestnes
county:
Møre og Romsdal
lat:
62.582085
lon:
6.93038
Open the place page for this point
id:
NSR:StopPlace:60567
name:
Tømte
label:
Tømte, Inderøy
category:
1 results
1. onstreetBus
municipality:
Inderøy
county:
Trøndelag
lat:
63.870282
lon:
11.217454
Open the place page for this point
id:
NSR:StopPlace:41903
name:
Tømra
label:
Tømra, Selbu
category:
1 results
1. onstreetBus
municipality:
Selbu
county:
Trøndelag
lat:
63.285188
lon:
11.073106
Open the place page for this point
id:
NSR:StopPlace:52048
name:
Tofta
label:
Tofta, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.803023
lon:
16.492126
Open the place page for this point
id:
NSR:StopPlace:8348
name:
Tomte
label:
Tomte, Løten
category:
1 results
1. onstreetBus
municipality:
Løten
county:
Innlandet
lat:
60.863298
lon:
11.302373
Open the place page for this point
id:
NSR:StopPlace:12488
name:
Tomte
label:
Tomte, Nordre Land
category:
1 results
1. onstreetBus
municipality:
Nordre Land
county:
Innlandet
lat:
60.895492
lon:
10.047136
Open the place page for this point
id:
NSR:StopPlace:1387
name:
Tømt
label:
Tømt, Indre Østfold
category:
1 results
1. onstreetBus
municipality:
Indre Østfold
county:
Østfold
lat:
59.624267
lon:
11.157635

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:1501
name:
Tomta
label:
Tomta, Sarpsborg
category:
1 results
1. onstreetBus
municipality:
Sarpsborg
county:
Østfold
lat:
59.379952
lon:
11.215849
Open the place page for this point
id:
NSR:StopPlace:7915
name:
Tomtan
label:
Tomtan, Folldal
category:
1 results
1. onstreetBus
municipality:
Folldal
county:
Innlandet
lat:
62.200843
lon:
10.307291
Open the place page for this point
id:
NSR:StopPlace:14881
name:
Tomta Geithus
label:
Tomta Geithus, Modum
category:
1 results
1. onstreetBus
municipality:
Modum
county:
Buskerud
lat:
59.92478
lon:
9.96652
Open the place page for this point
id:
NSR:StopPlace:61467
name:
Vy-tomta
label:
Vy-tomta, Oslo
category:
1 results
1. onstreetBus
municipality:
Oslo
county:
Oslo
lat:
59.910266
lon:
10.714851
Open the place page for this point
id:
NSR:StopPlace:24883
name:
Birkeland Tomta
label:
Birkeland Tomta, Birkenes
category:
1 results
1. onstreetBus
municipality:
Birkenes
county:
Agder
lat:
58.330576
lon:
8.231742
Open the place page for this point
id:
NSR:StopPlace:39287
name:
Tomra
label:
Tomra, Vestnes
category:
1 results
1. onstreetBus
municipality:
Vestnes
county:
Møre og Romsdal
lat:
62.582085
lon:
6.93038
Open the place page for this point
id:
NSR:StopPlace:60567
name:
Tømte
label:
Tømte, Inderøy
category:
1 results
1. onstreetBus
municipality:
Inderøy
county:
Trøndelag
lat:
63.870282
lon:
11.217454
Open the place page for this point
id:
NSR:StopPlace:41903
name:
Tømra
label:
Tømra, Selbu
category:
1 results
1. onstreetBus
municipality:
Selbu
county:
Trøndelag
lat:
63.285188
lon:
11.073106
Open the place page for this point
id:
NSR:StopPlace:52048
name:
Tofta
label:
Tofta, Harstad
category:
1 results
1. onstreetBus
municipality:
Harstad
county:
Troms
lat:
68.803023
lon:
16.492126
Open the place page for this point
id:
NSR:StopPlace:8348
name:
Tomte
label:
Tomte, Løten
category:
1 results
1. onstreetBus
municipality:
Løten
county:
Innlandet
lat:
60.863298
lon:
11.302373
Open the place page for this point
id:
NSR:StopPlace:12488
name:
Tomte
label:
Tomte, Nordre Land
category:
1 results
1. onstreetBus
municipality:
Nordre Land
county:
Innlandet
lat:
60.895492
lon:
10.047136
Open the place page for this point
id:
NSR:StopPlace:1387
name:
Tømt
label:
Tømt, Indre Østfold
category:
1 results
1. onstreetBus
municipality:
Indre Østfold
county:
Østfold
lat:
59.624267
lon:
11.157635

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.