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-21T04:22:16Z in 0.154 seconds.

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

Showing 2 of 2 results in compact format.

station_id:
18.10.0
latitude:
58.88343
longitude:
9.03313
station_id:
18.11.0
latitude:
58.93208
longitude:
8.85938

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-21T04:22:16.2528165Z

queryTime:

00:00:00.0007933

itemCount:

data:

2 results

Open the place page for this point
station_id:
18.10.0
stationName:
Gjerstad
latitude:
58.88343
longitude:
9.03313
utmEast_Z33:
156322
utmNorth_Z33:
6542414
masl:
51
riverName:
Gjerstadvassdraget
councilNumber:
4211
councilName:
Gjerstad
countyName:
Agder
drainageBasinKey:
718
hierarchy:
Gjerstadvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
018.2E10
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
235.89
drainageBasinAreaNorway:
235.89
gradient1085:
12.79
gradientBasin:
23.43
gradientRiver:
18.89
heightMinimum:
37
heightHypso10:
172
heightHypso20:
232
heightHypso30:
276
heightHypso40:
327
heightHypso50:
365
heightHypso60:
395
heightHypso70:
440
heightHypso80:
476
heightHypso90:
514
heightMaximum:
656
lengthKmBasin:
21.15
lengthKmRiver:
30.87
percentAgricul:
1.39
percentBog:
4.89
percentEffBog:
not reported by source
percentEffLake:
0.16
percentForest:
81.58
percentGlacier:
0
percentLake:
3.68
percentMountain:
3
percentUrban:
0.02
utmZoneGravi:
33
utmEastGravi:
149568
utmNorthGravi:
6549060
utmZoneInlet:
33
utmEastInlet:
141720
utmNorthInlet:
6552343
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
186.06
specificDischarge:
24.96
regulationArea:
0
areaReservoirs:
0.6
volumeReservoirs:
0
regulationPartReservoirs:
0
transferAreaIn:
0
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
0
reservoirVolumeIn:
0
reservoirVolumeOut:
0
remainingArea:
0
numberReservoirs:
1
firstYearRegulation:
0
catchmentRegTypeName:
regulert m/magasinregulering
owner:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
42
qStartYear:
1982
qEndYear:
2025
qm:
89.8418
q5:
107.051
q10:
122.2019
q20:
137.2278
q50:
157.4203
hm:
3.7279
h5:
4.063
h10:
4.3422
h20:
4.6069
h50:
4.9467
culQm:
113.7559
culQ5:
135.5459
culQ10:
154.7297
culQ20:
173.7553
culQ50:
199.3226
culHm:
4.1882
culH5:
4.5778
culH10:
4.9024
culH20:
5.2101
culH50:
5.6051
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1980-11-06T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1980-11-06T11:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1985-01-01T00:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1980-11-06T11: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:
  1980-11-06T11:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1985-01-01T00:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1980-11-06T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  1996-09-06T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1996-09-06T09:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1996-09-06T10:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1996-09-07T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
Open the place page for this point
station_id:
18.11.0
stationName:
Tjellingtjernbekk
latitude:
58.93208
longitude:
8.85938
utmEast_Z33:
146830
utmNorth_Z33:
6548724
masl:
223
riverName:
Gjerstadvassdraget
councilNumber:
4211
councilName:
Gjerstad
countyName:
Agder
drainageBasinKey:
719
hierarchy:
Gjerstadvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
018.2F
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
1.95
drainageBasinAreaNorway:
1.95
gradient1085:
74.4
gradientBasin:
22.04
gradientRiver:
72.78
heightMinimum:
222
heightHypso10:
279
heightHypso20:
310
heightHypso30:
349
heightHypso40:
380
heightHypso50:
397
heightHypso60:
421
heightHypso70:
437
heightHypso80:
450
heightHypso90:
466
heightMaximum:
501
lengthKmBasin:
2.4
lengthKmRiver:
1.65
percentAgricul:
0
percentBog:
4.72
percentEffBog:
not reported by source
percentEffLake:
1.51
percentForest:
68.08
percentGlacier:
0
percentLake:
1.99
percentMountain:
10.48
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
147471
utmNorthGravi:
6549831
utmZoneInlet:
33
utmEastInlet:
147784
utmNorthInlet:
6549846
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
1.48
specificDischarge:
24.05
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:
43
qStartYear:
1982
qEndYear:
2025
qm:
0.9767
q5:
1.1684
q10:
1.3534
q20:
1.5439
q50:
1.8108
hm:
0.701
h5:
0.7526
h10:
0.7857
h20:
0.8162
h50:
0.8552
culQm:
1.6259
culQ5:
1.9451
culQ10:
2.253
culQ20:
2.57
culQ50:
3.0144
culHm:
0.8286
culH5:
0.8735
culH10:
0.9127
culH20:
0.9498
culH50:
0.9972
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1981-09-10T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1981-09-09T23:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1981-09-10T00:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1981-09-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:
  1981-09-09T23:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1981-09-10T00:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1981-09-10T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2005-04-10T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2005-06-30T00:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-06-30T01:00:00Z
  dataToTime:
  2026-09-21T03:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-06-30T11: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.