search_stops

Search Norway's National Stop Register by stop name.

Signature: search_stops(query: string, required; limit: integer, items, optional, default 25; lang: one of: no, nb, nn, en, 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=25&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=25&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. Through this API: default 25, maximum 100.
`lang`	optional	string	Result language: "no" (default), "nb", "nn" 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=25&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=25&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=25&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-11-11T22:51:02Z in 0.204 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:62384
name:
Kjerringholmen ferjekai
label:
Kjerringholmen ferjekai, Hammerfest
category:
3 results
1. onstreetBus
2. harbourPort
3. ferryStop
municipality:
Hammerfest
county:
Finnmark
lat:
70.575555
lon:
23.572422
Open the place page for this point
id:
NSR:StopPlace:58548
name:
Sør-Tverrfjord kai
label:
Sør-Tverrfjord kai, Loppa
category:
2 results
1. ferryStop
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.219038
lon:
21.716548
Open the place page for this point
id:
NSR:StopPlace:62382
name:
Korsfjord ferjekai
label:
Korsfjord ferjekai, Alta
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.246378
lon:
23.393615
Open the place page for this point
id:
NSR:StopPlace:59707
name:
Tverrfjord ferjekai
label:
Tverrfjord ferjekai, Loppa
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.230396
lon:
22.268858
Open the place page for this point
id:
NSR:StopPlace:60479
name:
Øksfjord ferjekai
label:
Øksfjord ferjekai, Loppa
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.232921
lon:
22.358835
Open the place page for this point
id:
NSR:StopPlace:62383
name:
Nyvoll ferjekai
label:
Nyvoll ferjekai, Alta
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.226286
lon:
23.380601
Open the place page for this point
id:
NSR:StopPlace:56897
name:
Strømsnes ferjekai Akkarfjord
label:
Strømsnes ferjekai Akkarfjord, Hammerfest
category:
1 results
1. harbourPort
municipality:
Hammerfest
county:
Finnmark
lat:
70.601885
lon:
23.61825
Open the place page for this point
id:
NSR:StopPlace:57125
name:
Kongshus kai
label:
Kongshus kai, Alta
category:
1 results
1. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.143383
lon:
23.273132
Open the place page for this point
id:
NSR:StopPlace:57186
name:
Bergsfjord ferjekai
label:
Bergsfjord ferjekai, Loppa
category:
1 results
1. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.251844
lon:
21.784509
Open the place page for this point
id:
NSR:StopPlace:50302
name:
Lalia bru
label:
Lalia bru, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.323723
lon:
14.620161
Open the place page for this point
id:
NSR:StopPlace:45891
name:
Laplassen vegdele
label:
Laplassen vegdele, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.607427
lon:
11.125629

Show all fields in HTML

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:62384
name:
Kjerringholmen ferjekai
label:
Kjerringholmen ferjekai, Hammerfest
category:
3 results
1. onstreetBus
2. harbourPort
3. ferryStop
municipality:
Hammerfest
county:
Finnmark
lat:
70.575555
lon:
23.572422
Open the place page for this point
id:
NSR:StopPlace:58548
name:
Sør-Tverrfjord kai
label:
Sør-Tverrfjord kai, Loppa
category:
2 results
1. ferryStop
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.219038
lon:
21.716548
Open the place page for this point
id:
NSR:StopPlace:62382
name:
Korsfjord ferjekai
label:
Korsfjord ferjekai, Alta
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.246378
lon:
23.393615
Open the place page for this point
id:
NSR:StopPlace:59707
name:
Tverrfjord ferjekai
label:
Tverrfjord ferjekai, Loppa
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.230396
lon:
22.268858
Open the place page for this point
id:
NSR:StopPlace:60479
name:
Øksfjord ferjekai
label:
Øksfjord ferjekai, Loppa
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.232921
lon:
22.358835
Open the place page for this point
id:
NSR:StopPlace:62383
name:
Nyvoll ferjekai
label:
Nyvoll ferjekai, Alta
category:
2 results
1. onstreetBus
2. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.226286
lon:
23.380601
Open the place page for this point
id:
NSR:StopPlace:56897
name:
Strømsnes ferjekai Akkarfjord
label:
Strømsnes ferjekai Akkarfjord, Hammerfest
category:
1 results
1. harbourPort
municipality:
Hammerfest
county:
Finnmark
lat:
70.601885
lon:
23.61825
Open the place page for this point
id:
NSR:StopPlace:57125
name:
Kongshus kai
label:
Kongshus kai, Alta
category:
1 results
1. harbourPort
municipality:
Alta
county:
Finnmark
lat:
70.143383
lon:
23.273132
Open the place page for this point
id:
NSR:StopPlace:57186
name:
Bergsfjord ferjekai
label:
Bergsfjord ferjekai, Loppa
category:
1 results
1. harbourPort
municipality:
Loppa
county:
Finnmark
lat:
70.251844
lon:
21.784509
Open the place page for this point
id:
NSR:StopPlace:50302
name:
Lalia bru
label:
Lalia bru, Rana
category:
1 results
1. onstreetBus
municipality:
Rana
county:
Nordland
lat:
66.323723
lon:
14.620161
Open the place page for this point
id:
NSR:StopPlace:45891
name:
Laplassen vegdele
label:
Laplassen vegdele, Levanger
category:
1 results
1. onstreetBus
municipality:
Levanger
county:
Trøndelag
lat:
63.607427
lon:
11.125629

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.