search_stations

Find NVE hydrological stations and their available time series.

Signature: search_stations(municipality: string, optional, default None; county: string, optional, default None; station_name: string, optional, default None; active_only: yes/no, optional, default True; limit: integer, items, optional, default 25; 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/nve/search_stations/?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0

Replace {municipality}, {county}, {station_name}, {active_only}, {limit}, {offset} 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/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0. Open this exact request as JSON.

Parameter	Requirement	JSON type	Description
`municipality`	optional	union	Municipality name (HydAPI field CouncilName).
`county`	optional	union	County name.
`station_name`	optional	union	Station name filter.
`active_only`	optional	boolean	Return only active stations by default.
`limit`	optional	integer	Maximum stations returned (default 25, maximum 100). Unit: items.
`offset`	optional	integer	Number of matching stations to skip (default 0). Unit: items.

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/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&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/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "nve",
  "operation": "search_stations",
  "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: NVE HydAPI. Retrieved 2026-09-20T23:14:23Z in 0.465 seconds.

Search scope: Municipality-filtered results cover all of TJELDSUND municipality.

Showing 2 of 2 results in compact format.

station_id:
189.1.0
latitude:
68.62028
longitude:
17.2503
station_id:
189.3.0
latitude:
68.6449
longitude:
16.72235

Show all fields in HTML

currentLink:

https://hydapi.nve.no/api/v1/Stations?CouncilName=TJELDSUND&Active=OnlyActive

apiVersion:

1.0

license:

https://data.norge.no/nlod/en

createdAt:

2026-09-20T23:14:23.4860562Z

queryTime:

00:00:00.0007301

itemCount:

data:

2 results

Open the place page for this point
station_id:
189.1.0
stationName:
Skoddebergvatnet
latitude:
68.62028
longitude:
17.2503
utmEast_Z33:
591532
utmNorth_Z33:
7613696
masl:
103
riverName:
Skoddebergvassdraget
councilNumber:
5512
councilName:
Tjeldsund
countyName:
Troms
drainageBasinKey:
2058
hierarchy:
Skoddebergvassdraget
lakeArea:
8.57
lakeName:
Skoaberjávri
lakeNo:
2363
regineNo:
189.D
reservoirNo:
744
reservoirName:
SKODDEBERGVATN
stationTypeName:
Privat, pålagt
stationStatusName:
Aktiv
drainageBasinArea:
107.31
drainageBasinAreaNorway:
107.31
gradient1085:
27.13
gradientBasin:
32.55
gradientRiver:
31.71
heightMinimum:
99
heightHypso10:
121
heightHypso20:
184
heightHypso30:
233
heightHypso40:
286
heightHypso50:
400
heightHypso60:
503
heightHypso70:
592
heightHypso80:
746
heightHypso90:
886
heightMaximum:
1283
lengthKmBasin:
10.13
lengthKmRiver:
17.16
percentAgricul:
0.1
percentBog:
8.09
percentEffBog:
not reported by source
percentEffLake:
8.58
percentForest:
41.96
percentGlacier:
0.9
percentLake:
10.74
percentMountain:
36.94
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
593100
utmNorthGravi:
7610683
utmZoneInlet:
33
utmEastInlet:
598411
utmNorthInlet:
7614728
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
129.04
specificDischarge:
38.07
regulationArea:
107.41
areaReservoirs:
8.56
volumeReservoirs:
56
regulationPartReservoirs:
0.43
transferAreaIn:
0
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
8.56
reservoirVolumeIn:
0
reservoirVolumeOut:
56
remainingArea:
0
numberReservoirs:
1
firstYearRegulation:
1953
catchmentRegTypeName:
regulert m/magasinregulering
owner:
NORDKRAFT MAGASIN 2 AS
qNumberOfYears:
not reported by source
qStartYear:
not reported by source
qEndYear:
not reported by source
qm:
not reported by source
q5:
not reported by source
q10:
not reported by source
q20:
not reported by source
q50:
not reported by source
hm:
not reported by source
h5:
not reported by source
h10:
not reported by source
h20:
not reported by source
h50:
not reported by source
culQm:
not reported by source
culQ5:
not reported by source
culQ10:
not reported by source
culQ20:
not reported by source
culQ50:
not reported by source
culHm:
not reported by source
culH5:
not reported by source
culH10:
not reported by source
culH20:
not reported by source
culH50:
not reported by source
seriesList:
1 results
1. parameterName:
  Magasinvolum
  parameter:
  1004
  versionNo:
  0
  unit:
  millioner m³
  serieFrom:
  not reported by source
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1928-09-01T11:00:00Z
  dataToTime:
  2022-12-18T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2021-02-01T01:00:00Z
  dataToTime:
  2022-12-18T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1928-09-01T11:00:00Z
  dataToTime:
  2022-12-18T11:00:00Z
Open the place page for this point
station_id:
189.3.0
stationName:
Tennevikvatn
latitude:
68.6449
longitude:
16.72235
utmEast_Z33:
569986
utmNorth_Z33:
7615747
masl:
40
riverName:
Tennevikelva
councilNumber:
5512
councilName:
Tjeldsund
countyName:
Troms
drainageBasinKey:
2060
hierarchy:
Tennevikelva
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
189.2A
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
85.41
drainageBasinAreaNorway:
85.41
gradient1085:
18.35
gradientBasin:
30.29
gradientRiver:
25.96
heightMinimum:
37
heightHypso10:
150
heightHypso20:
195
heightHypso30:
243
heightHypso40:
276
heightHypso50:
367
heightHypso60:
436
heightHypso70:
551
heightHypso80:
658
heightHypso90:
772
heightMaximum:
1303
lengthKmBasin:
12.9
lengthKmRiver:
23.54
percentAgricul:
0.41
percentBog:
4.15
percentEffBog:
not reported by source
percentEffLake:
3.28
percentForest:
39.47
percentGlacier:
0.04
percentLake:
8.73
percentMountain:
43.29
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
574137
utmNorthGravi:
7612851
utmZoneInlet:
33
utmEastInlet:
578749
utmNorthInlet:
7610484
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
100.89
specificDischarge:
37.48
regulationArea:
0
areaReservoirs:
0
volumeReservoirs:
0
regulationPartReservoirs:
0
transferAreaIn:
0
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
0
reservoirVolumeIn:
0
reservoirVolumeOut:
0
remainingArea:
0
numberReservoirs:
0
firstYearRegulation:
0
catchmentRegTypeName:
Uregulert
owner:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
47
qStartYear:
1978
qEndYear:
2025
qm:
21.0521
q5:
25.2983
q10:
28.3735
q20:
31.1793
q50:
34.6127
hm:
1.0952
h5:
1.1615
h10:
1.2056
h20:
1.2437
h50:
1.2877
culQm:
21.8609
culQ5:
26.2703
culQ10:
29.4636
culQ20:
32.3771
culQ50:
35.9425
culHm:
1.1083
culH5:
1.1757
culH10:
1.2207
culH20:
1.2593
culH50:
1.304
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1978-03-10T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1978-03-10T11:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1989-01-12T13:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1978-03-10T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
2. parameterName:
  Vannføring
  parameter:
  1001
  versionNo:
  1
  unit:
  m³/s
  serieFrom:
  not reported by source
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1978-03-10T11:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1989-01-12T13:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1978-03-10T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2024-06-25T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  2 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2025-12-16T12:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2025-12-16T13:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2006-09-21T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2006-09-20T23:30:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2006-09-21T00:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2006-09-21T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z

limit:

offset:

returned:

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_stations 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

Check parameter ID, unit, resolution and quality codes before interpreting observations.

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.