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-21T23:16:40Z in 0.273 seconds.

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

Showing 2 of 2 results in compact format.

station_id:
97.1.0
latitude:
62.33236
longitude:
6.59336
station_id:
98.3.0
latitude:
62.35126
longitude:
6.83293

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-21T23:16:40.2030387Z

queryTime:

00:00:00.0014570

itemCount:

data:

2 results

Open the place page for this point
station_id:
97.1.0
stationName:
Fetvatn (Fitjavatnet)
latitude:
62.33236
longitude:
6.59336
utmEast_Z33:
65379
utmNorth_Z33:
6939517
masl:
1
riverName:
Velledalselva
councilNumber:
1528
councilName:
Sykkylven
countyName:
Møre og Romsdal
drainageBasinKey:
1504
hierarchy:
Velledalselva
lakeArea:
0
lakeName:
not reported by source
lakeNo:
1955
regineNo:
097.7B
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
89.05
drainageBasinAreaNorway:
89.05
gradient1085:
33.59
gradientBasin:
56.75
gradientRiver:
43.87
heightMinimum:
2
heightHypso10:
115
heightHypso20:
259
heightHypso30:
411
heightHypso40:
537
heightHypso50:
646
heightHypso60:
774
heightHypso70:
885
heightHypso80:
1045
heightHypso90:
1207
heightMaximum:
1586
lengthKmBasin:
13.52
lengthKmRiver:
17.78
percentAgricul:
4.42
percentBog:
0.61
percentEffBog:
not reported by source
percentEffLake:
1.54
percentForest:
36.95
percentGlacier:
3.2
percentLake:
2.29
percentMountain:
48.4
percentUrban:
0.09
utmZoneGravi:
33
utmEastGravi:
68754
utmNorthGravi:
6934095
utmZoneInlet:
33
utmEastInlet:
74922
utmNorthInlet:
6935017
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
249.71
specificDischarge:
88.86
regulationArea:
0
areaReservoirs:
0
volumeReservoirs:
0
regulationPartReservoirs:
0
transferAreaIn:
9.57
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
0
reservoirVolumeIn:
0
reservoirVolumeOut:
0
remainingArea:
0
numberReservoirs:
0
firstYearRegulation:
2010
catchmentRegTypeName:
Uregulert
owner:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
53
qStartYear:
1973
qEndYear:
2025
qm:
62.5764
q5:
75.6936
q10:
85.8417
q20:
95.3699
q50:
107.4104
hm:
2.1078
h5:
2.2174
h10:
2.2958
h20:
2.3653
h50:
2.4483
culQm:
88.7983
culQ5:
107.4122
culQ10:
121.8127
culQ20:
135.3336
culQ50:
152.4196
culHm:
2.3178
culH5:
2.4483
culH10:
2.5416
culH20:
2.6243
culH50:
2.7231
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1946-08-09T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1946-08-09T11:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-06-30T16:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1946-08-09T11:00:00Z
  dataToTime:
  2026-09-21T11: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:
  1946-08-09T11:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-06-30T16:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1946-08-09T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2024-04-08T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  1440
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-20T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  2
  unit:
  °C
  serieFrom:
  2003-06-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2003-10-25T19:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2003-10-25T20:00:00Z
  dataToTime:
  2026-09-21T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2003-10-26T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
Open the place page for this point
station_id:
98.3.0
stationName:
Nysetervatn
latitude:
62.35126
longitude:
6.83293
utmEast_Z33:
77982
utmNorth_Z33:
6940020
masl:
338
riverName:
Fausaelva
councilNumber:
1528
councilName:
Sykkylven
countyName:
Møre og Romsdal
drainageBasinKey:
1512
hierarchy:
Fausaelva
lakeArea:
2.36
lakeName:
Nysætervatnet
lakeNo:
1957
regineNo:
098.2C
reservoirNo:
622
reservoirName:
NYSETERVATN
stationTypeName:
Privat, pålagt
stationStatusName:
Aktiv
drainageBasinArea:
31.01
drainageBasinAreaNorway:
29.71
gradient1085:
34.12
gradientBasin:
30.47
gradientRiver:
46.78
heightMinimum:
336
heightHypso10:
350
heightHypso20:
389
heightHypso30:
440
heightHypso40:
511
heightHypso50:
581
heightHypso60:
634
heightHypso70:
728
heightHypso80:
808
heightHypso90:
924
heightMaximum:
1229
lengthKmBasin:
6.28
lengthKmRiver:
7.27
percentAgricul:
0
percentBog:
2.54
percentEffBog:
not reported by source
percentEffLake:
8.05
percentForest:
40.69
percentGlacier:
0
percentLake:
8.93
percentMountain:
41.88
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
75690
utmNorthGravi:
6939407
utmZoneInlet:
33
utmEastInlet:
75976
utmNorthInlet:
6937034
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
59.88
specificDischarge:
64.04
regulationArea:
29.64
areaReservoirs:
2.36
volumeReservoirs:
15.6
regulationPartReservoirs:
0.26
transferAreaIn:
0
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
2.36
reservoirVolumeIn:
0
reservoirVolumeOut:
15.6
remainingArea:
0
numberReservoirs:
1
firstYearRegulation:
1952
catchmentRegTypeName:
regulert m/magasinregulering
owner:
STRANDA ENERGI 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:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1949-01-05T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1949-01-05T11:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2024-05-02T00:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1949-01-05T11:00:00Z
  dataToTime:
  2026-09-19T11: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.