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-22T12:27:06Z in 0.137 seconds.

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

Showing 2 of 2 results in compact format.

station_id:
12.188.0
latitude:
60.37315
longitude:
9.72676
station_id:
12.212.0
latitude:
60.47921
longitude:
9.4488

Show all fields in HTML

currentLink:

https://hydapi.nve.no/api/v1/Stations?CouncilName=FL%C3%85&Active=OnlyActive

apiVersion:

1.0

license:

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

createdAt:

2026-09-22T12:27:06.290308Z

queryTime:

00:00:00.0009013

itemCount:

data:

2 results

Open the place page for this point
station_id:
12.188.0
stationName:
Langtjernbekk
latitude:
60.37315
longitude:
9.72676
utmEast_Z33:
209400
utmNorth_Z33:
6704606
masl:
515
riverName:
Trommaldelva
councilNumber:
3320
councilName:
Flå
countyName:
Buskerud
drainageBasinKey:
513
hierarchy:
Trommaldelva/Hallingdalsvassdraget/Drammensvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
012.CB5C
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
4.67
drainageBasinAreaNorway:
4.67
gradient1085:
27.14
gradientBasin:
16.25
gradientRiver:
24.31
heightMinimum:
516
heightHypso10:
531
heightHypso20:
544
heightHypso30:
570
heightHypso40:
582
heightHypso50:
597
heightHypso60:
613
heightHypso70:
620
heightHypso80:
638
heightHypso90:
668
heightMaximum:
755
lengthKmBasin:
3.16
lengthKmRiver:
3.54
percentAgricul:
0
percentBog:
6.57
percentEffBog:
not reported by source
percentEffLake:
5.11
percentForest:
86.79
percentGlacier:
0
percentLake:
6.78
percentMountain:
0
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
210231
utmNorthGravi:
6703597
utmZoneInlet:
33
utmEastInlet:
210181
utmNorthInlet:
6701775
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
2.86
specificDischarge:
19.41
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:
52
qStartYear:
1974
qEndYear:
2025
qm:
1.1661
q5:
1.4391
q10:
1.5662
q20:
1.6613
q50:
1.7545
hm:
0.6352
h5:
0.6876
h10:
0.7099
h20:
0.7258
h50:
0.7409
culQm:
1.2561
culQ5:
1.5502
culQ10:
1.687
culQ20:
1.7894
culQ50:
1.8899
culHm:
0.6532
culH5:
0.7071
culH10:
0.73
culH20:
0.7464
culH50:
0.7619
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1973-10-03T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1973-10-03T14:30:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-10-03T15:00:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-10-04T11: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:
  1973-10-03T14:30:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-10-03T15:00:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1973-10-04T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2009-08-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2009-08-12T20:00:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2009-08-12T21:00:00Z
  dataToTime:
  2026-09-22T10:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2009-08-13T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
Open the place page for this point
station_id:
12.212.0
stationName:
Hangtjern
latitude:
60.47921
longitude:
9.4488
utmEast_Z33:
195102
utmNorth_Z33:
6717650
masl:
589
riverName:
Heieelvi
councilNumber:
3320
councilName:
Flå
countyName:
Buskerud
drainageBasinKey:
527
hierarchy:
Heieelvi/Hallingdalsvassdraget/Drammensvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
012.CC1D
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
11.02
drainageBasinAreaNorway:
11.02
gradient1085:
53.86
gradientBasin:
17.56
gradientRiver:
48.04
heightMinimum:
590
heightHypso10:
679
heightHypso20:
741
heightHypso30:
764
heightHypso40:
785
heightHypso50:
806
heightHypso60:
822
heightHypso70:
856
heightHypso80:
893
heightHypso90:
942
heightMaximum:
1047
lengthKmBasin:
4.4
lengthKmRiver:
5.5
percentAgricul:
0
percentBog:
12.21
percentEffBog:
not reported by source
percentEffLake:
0.7
percentForest:
80.39
percentGlacier:
0
percentLake:
2.51
percentMountain:
4.06
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
195521
utmNorthGravi:
6719655
utmZoneInlet:
33
utmEastInlet:
193918
utmNorthInlet:
6721162
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
7.69
specificDischarge:
22.11
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:
35
qStartYear:
1986
qEndYear:
2021
qm:
2.4368
q5:
3.1387
q10:
3.5315
q20:
3.8511
q50:
4.195
hm:
0.6529
h5:
0.7056
h10:
0.7323
h20:
0.7527
h50:
0.7737
culQm:
3.4597
culQ5:
4.4563
culQ10:
5.0141
culQ20:
5.4677
culQ50:
5.9561
culHm:
0.7275
culH5:
0.789
culH10:
0.82
culH20:
0.8438
culH50:
0.8682
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1986-04-16T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1986-04-16T11:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1986-04-16T14:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1986-04-16T11: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:
  1986-04-16T11:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1986-04-16T14:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1986-04-16T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2008-06-10T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2008-06-10T17:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2008-06-10T18:00:00Z
  dataToTime:
  2026-09-22T11:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2008-08-21T11:00:00Z
  dataToTime:
  2026-09-21T11: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.