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:51:50Z in 0.142 seconds.

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

Showing 2 of 2 results in compact format.

station_id:
19.107.0
latitude:
58.43536
longitude:
8.70269
station_id:
19.127.0
latitude:
58.41074
longitude:
8.67014

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-20T23:51:50.7247695Z

queryTime:

00:00:00.0011303

itemCount:

data:

2 results

Open the place page for this point
station_id:
19.107.0
stationName:
Lilleelv
latitude:
58.43536
longitude:
8.70269
utmEast_Z33:
132635
utmNorth_Z33:
6494410
masl:
18
riverName:
Lilleelva
councilNumber:
4203
councilName:
Arendal
countyName:
Agder
drainageBasinKey:
770
hierarchy:
Lilleelva/Arendalsvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
019.A1Z
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
40.517
drainageBasinAreaNorway:
40.517
gradient1085:
4.34
gradientBasin:
15.91
gradientRiver:
5.23
heightMinimum:
12
heightHypso10:
64
heightHypso20:
76
heightHypso30:
89
heightHypso40:
97
heightHypso50:
111
heightHypso60:
119
heightHypso70:
131
heightHypso80:
138
heightHypso90:
151
heightMaximum:
206
lengthKmBasin:
13.94
lengthKmRiver:
17.22
percentAgricul:
4.17
percentBog:
1.38
percentEffBog:
not reported by source
percentEffLake:
1.96
percentForest:
85.39
percentGlacier:
0
percentLake:
4.98
percentMountain:
0
percentUrban:
0.8
utmZoneGravi:
33
utmEastGravi:
133006
utmNorthGravi:
6500984
utmZoneInlet:
33
utmEastInlet:
134990
utmNorthInlet:
6506766
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
31.65
specificDischarge:
24.75
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:
29
qStartYear:
1986
qEndYear:
2025
qm:
12.1672
q5:
15.4847
q10:
17.7372
q20:
19.7348
q50:
22.1028
hm:
2.6954
h5:
2.8977
h10:
3.0246
h20:
3.1315
h50:
3.2525
culQm:
13.6587
culQ5:
17.3829
culQ10:
19.9115
culQ20:
22.1539
culQ50:
24.8123
culHm:
2.7889
culH5:
3.0051
culH10:
3.1408
culH20:
3.255
culH50:
3.3843
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1983-10-21T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1983-10-21T09:30:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-10-21T10:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-10-22T11: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:
  1983-10-21T09:30:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-10-21T10:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-10-22T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2024-02-15T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2023-12-31T23:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2024-04-15T10:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2024-04-16T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2004-06-15T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2004-06-16T14:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-06-16T15:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-06-17T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
Open the place page for this point
station_id:
19.127.0
stationName:
Rygene total
latitude:
58.41074
longitude:
8.67014
utmEast_Z33:
130481
utmNorth_Z33:
6491855
masl:
19
riverName:
Arendalsvassdraget
councilNumber:
4203
councilName:
Arendal
countyName:
Agder
drainageBasinKey:
775
hierarchy:
Arendalsvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
019.A22
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Privat, pålagt
stationStatusName:
Aktiv
drainageBasinArea:
3946.203
drainageBasinAreaNorway:
3946.203
gradient1085:
3.81
gradientBasin:
23.97
gradientRiver:
5.81
heightMinimum:
35
heightHypso10:
290
heightHypso20:
367
heightHypso30:
437
heightHypso40:
552
heightHypso50:
706
heightHypso60:
750
heightHypso70:
802
heightHypso80:
862
heightHypso90:
962
heightMaximum:
1521
lengthKmBasin:
131.21
lengthKmRiver:
218.84
percentAgricul:
1
percentBog:
4.92
percentEffBog:
not reported by source
percentEffLake:
1.3
percentForest:
68.44
percentGlacier:
0
percentLake:
11.5
percentMountain:
10.22
percentUrban:
0.09
utmZoneGravi:
33
utmEastGravi:
113936
utmNorthGravi:
6561729
utmZoneInlet:
33
utmEastInlet:
73856
utmNorthInlet:
6608308
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
3558.21
specificDischarge:
28.57
regulationArea:
3946.19
areaReservoirs:
235.08
volumeReservoirs:
1353.1
regulationPartReservoirs:
0.38
transferAreaIn:
0
transferAreaOut:
3946.19
reservoirAreaIn:
0
reservoirAreaOut:
226.07
reservoirVolumeIn:
0
reservoirVolumeOut:
1353.1
remainingArea:
0
numberReservoirs:
33
firstYearRegulation:
1904
catchmentRegTypeName:
Regulert m/magasinregulering og overføringer
owner:
Å ENERGI VANNKRAFT AS
qNumberOfYears:
not reported by source
qStartYear:
not reported by source
qEndYear:
not reported by source
qm:
418
q5:
523
q10:
644
q20:
777
q50:
982
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:
443
culQ5:
554
culQ10:
682
culQ20:
824
culQ50:
1041
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:
2 results
1. parameterName:
  Vannføring
  parameter:
  1001
  versionNo:
  0
  unit:
  m³/s
  serieFrom:
  not reported by source
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1899-09-28T11:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2007-12-31T23:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1899-09-29T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
2. parameterName:
  Vannføring
  parameter:
  1001
  versionNo:
  1
  unit:
  m³/s
  serieFrom:
  1977-12-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1977-12-01T11:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2007-12-31T23:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1977-12-02T11: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.