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-03T14:42:44Z in 0.394 seconds.

returned:

stops:

12 results

Open the place page for this point
id:
NSR:StopPlace:25347
name:
Skoie
label:
Skoie, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.068105
lon:
7.553556
Open the place page for this point
id:
NSR:StopPlace:61977
name:
Skoieveien nord
label:
Skoieveien nord, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.067968
lon:
7.534955
Open the place page for this point
id:
NSR:StopPlace:62255
name:
Skoieveien syd
label:
Skoieveien syd, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.057852
lon:
7.568515
Open the place page for this point
id:
NSR:StopPlace:25096
name:
Skeie
label:
Skeie, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.464961
lon:
7.231115
Open the place page for this point
id:
NSR:StopPlace:29535
name:
Skeie
label:
Skeie, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.283655
lon:
5.302829
Open the place page for this point
id:
NSR:StopPlace:41117
name:
Skoge
label:
Skoge, Sande
category:
1 results
1. onstreetBus
municipality:
Sande
county:
Møre og Romsdal
lat:
62.2194
lon:
5.696693
Open the place page for this point
id:
NSR:StopPlace:29440
name:
Skoge
label:
Skoge, Øygarden
category:
1 results
1. onstreetBus
municipality:
Øygarden
county:
Vestland
lat:
60.26776
lon:
5.087553
Open the place page for this point
id:
NSR:StopPlace:29538
name:
Skeie
label:
Skeie, Bjørnafjorden
category:
1 results
1. onstreetBus
municipality:
Bjørnafjorden
county:
Vestland
lat:
60.173052
lon:
5.416801
Open the place page for this point
id:
NSR:StopPlace:26309
name:
Skeie
label:
Skeie, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.696256
lon:
5.552438
Open the place page for this point
id:
NSR:StopPlace:35152
name:
Skeie
label:
Skeie, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.44046
lon:
6.75803
Open the place page for this point
id:
NSR:StopPlace:25091
name:
Skeie
label:
Skeie, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.048354
lon:
7.583397
Open the place page for this point
id:
NSR:StopPlace:29541
name:
Skeie
label:
Skeie, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.366497
lon:
6.090401

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:25347
name:
Skoie
label:
Skoie, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.068105
lon:
7.553556
Open the place page for this point
id:
NSR:StopPlace:61977
name:
Skoieveien nord
label:
Skoieveien nord, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.067968
lon:
7.534955
Open the place page for this point
id:
NSR:StopPlace:62255
name:
Skoieveien syd
label:
Skoieveien syd, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.057852
lon:
7.568515
Open the place page for this point
id:
NSR:StopPlace:25096
name:
Skeie
label:
Skeie, Hægebostad
category:
1 results
1. onstreetBus
municipality:
Hægebostad
county:
Agder
lat:
58.464961
lon:
7.231115
Open the place page for this point
id:
NSR:StopPlace:29535
name:
Skeie
label:
Skeie, Bergen
category:
1 results
1. onstreetBus
municipality:
Bergen
county:
Vestland
lat:
60.283655
lon:
5.302829
Open the place page for this point
id:
NSR:StopPlace:41117
name:
Skoge
label:
Skoge, Sande
category:
1 results
1. onstreetBus
municipality:
Sande
county:
Møre og Romsdal
lat:
62.2194
lon:
5.696693
Open the place page for this point
id:
NSR:StopPlace:29440
name:
Skoge
label:
Skoge, Øygarden
category:
1 results
1. onstreetBus
municipality:
Øygarden
county:
Vestland
lat:
60.26776
lon:
5.087553
Open the place page for this point
id:
NSR:StopPlace:29538
name:
Skeie
label:
Skeie, Bjørnafjorden
category:
1 results
1. onstreetBus
municipality:
Bjørnafjorden
county:
Vestland
lat:
60.173052
lon:
5.416801
Open the place page for this point
id:
NSR:StopPlace:26309
name:
Skeie
label:
Skeie, Klepp
category:
1 results
1. onstreetBus
municipality:
Klepp
county:
Rogaland
lat:
58.696256
lon:
5.552438
Open the place page for this point
id:
NSR:StopPlace:35152
name:
Skeie
label:
Skeie, Sogndal
category:
1 results
1. onstreetBus
municipality:
Sogndal
county:
Vestland
lat:
61.44046
lon:
6.75803
Open the place page for this point
id:
NSR:StopPlace:25091
name:
Skeie
label:
Skeie, Lindesnes
category:
1 results
1. onstreetBus
municipality:
Lindesnes
county:
Agder
lat:
58.048354
lon:
7.583397
Open the place page for this point
id:
NSR:StopPlace:29541
name:
Skeie
label:
Skeie, Kvam
category:
1 results
1. onstreetBus
municipality:
Kvam
county:
Vestland
lat:
60.366497
lon:
6.090401

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.