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-21T16:02:00Z in 0.130 seconds.

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:59092
name:
Gyland stasjon
label:
Gyland stasjon, Flekkefjord
category:
2 results
1. onstreetBus
2. railStation
municipality:
Flekkefjord
county:
Agder
lat:
58.38434
lon:
6.837198
Open the place page for this point
id:
NSR:StopPlace:60184
name:
Gyland kirke
label:
Gyland kirke, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.411177
lon:
6.791364
Open the place page for this point
id:
NSR:StopPlace:25740
name:
Gyland skole
label:
Gyland skole, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.376438
lon:
6.835106
Open the place page for this point
id:
NSR:StopPlace:25739
name:
Gyland Gård
label:
Gyland Gård, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.428342
lon:
6.838818
Open the place page for this point
id:
NSR:StopPlace:42287
name:
Gylland
label:
Gylland, Melhus
category:
1 results
1. onstreetBus
municipality:
Melhus
county:
Trøndelag
lat:
63.090086
lon:
10.249743
Open the place page for this point
id:
NSR:StopPlace:25746
name:
Gysland
label:
Gysland, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.30607
lon:
7.212508
Open the place page for this point
id:
NSR:StopPlace:44655
name:
Gilland
label:
Gilland, Meråker
category:
1 results
1. onstreetBus
municipality:
Meråker
county:
Trøndelag
lat:
63.300686
lon:
11.849718
Open the place page for this point
id:
NSR:StopPlace:17690
name:
Gusland
label:
Gusland, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
58.986356
lon:
9.914876
Open the place page for this point
id:
NSR:StopPlace:33475
name:
Gatland
label:
Gatland, Osterøy
category:
1 results
1. onstreetBus
municipality:
Osterøy
county:
Vestland
lat:
60.598372
lon:
5.483037
Open the place page for this point
id:
NSR:StopPlace:28763
name:
Gåsland
label:
Gåsland, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.413249
lon:
5.308228
Open the place page for this point
id:
NSR:StopPlace:29461
name:
Gåsland
label:
Gåsland, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.80169
lon:
5.166647

limit:

offset:

has_more_results:

truncated:

Show all fields in HTML

returned:

stops:

11 results

Open the place page for this point
id:
NSR:StopPlace:59092
name:
Gyland stasjon
label:
Gyland stasjon, Flekkefjord
category:
2 results
1. onstreetBus
2. railStation
municipality:
Flekkefjord
county:
Agder
lat:
58.38434
lon:
6.837198
Open the place page for this point
id:
NSR:StopPlace:60184
name:
Gyland kirke
label:
Gyland kirke, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.411177
lon:
6.791364
Open the place page for this point
id:
NSR:StopPlace:25740
name:
Gyland skole
label:
Gyland skole, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.376438
lon:
6.835106
Open the place page for this point
id:
NSR:StopPlace:25739
name:
Gyland Gård
label:
Gyland Gård, Flekkefjord
category:
1 results
1. onstreetBus
municipality:
Flekkefjord
county:
Agder
lat:
58.428342
lon:
6.838818
Open the place page for this point
id:
NSR:StopPlace:42287
name:
Gylland
label:
Gylland, Melhus
category:
1 results
1. onstreetBus
municipality:
Melhus
county:
Trøndelag
lat:
63.090086
lon:
10.249743
Open the place page for this point
id:
NSR:StopPlace:25746
name:
Gysland
label:
Gysland, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.30607
lon:
7.212508
Open the place page for this point
id:
NSR:StopPlace:44655
name:
Gilland
label:
Gilland, Meråker
category:
1 results
1. onstreetBus
municipality:
Meråker
county:
Trøndelag
lat:
63.300686
lon:
11.849718
Open the place page for this point
id:
NSR:StopPlace:17690
name:
Gusland
label:
Gusland, Larvik
category:
1 results
1. onstreetBus
municipality:
Larvik
county:
Vestfold
lat:
58.986356
lon:
9.914876
Open the place page for this point
id:
NSR:StopPlace:33475
name:
Gatland
label:
Gatland, Osterøy
category:
1 results
1. onstreetBus
municipality:
Osterøy
county:
Vestland
lat:
60.598372
lon:
5.483037
Open the place page for this point
id:
NSR:StopPlace:28763
name:
Gåsland
label:
Gåsland, Haugesund
category:
1 results
1. onstreetBus
municipality:
Haugesund
county:
Rogaland
lat:
59.413249
lon:
5.308228
Open the place page for this point
id:
NSR:StopPlace:29461
name:
Gåsland
label:
Gåsland, Bømlo
category:
1 results
1. onstreetBus
municipality:
Bømlo
county:
Vestland
lat:
59.80169
lon:
5.166647

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.