search_stations

Find NVE hydrological stations and their available time series.

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).
`offset`	optional	integer	Number of matching stations to skip (default 0).

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": "..."}
}

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-08-03T06:10:45Z in 0.419 seconds.

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

Showing 1 of 1 results in compact format.

latitude:
61.00576
longitude:
5.19215

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-08-03T06:10:45.3494436Z

queryTime:

00:00:00.0022316

itemCount:

data:

1 results

Open the place page for this point
stationId:
68.2.0
stationName:
Havelandselv
latitude:
61.00576
longitude:
5.19215
utmEast_Z33:
-28988
utmNorth_Z33:
6803173
masl:
10
riverName:
Nordgulelva
councilNumber:
4635
councilName:
Gulen
countyName:
Vestland
drainageBasinKey:
1213
hierarchy:
Nordgulelva
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
068.7Z
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
21
drainageBasinAreaNorway:
21.004
gradient1085:
63.18
gradientBasin:
46.29
gradientRiver:
68.05
heightMinimum:
0
heightHypso10:
139
heightHypso20:
229
heightHypso30:
339
heightHypso40:
426
heightHypso50:
514
heightHypso60:
546
heightHypso70:
574
heightHypso80:
605
heightHypso90:
642
heightMaximum:
721
lengthKmBasin:
4.76
lengthKmRiver:
7.26
percentAgricul:
2.79
percentBog:
0.25
percentEffBog:
not reported by source
percentEffLake:
0.92
percentForest:
33.22
percentGlacier:
0
percentLake:
4.61
percentMountain:
49.92
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
-27816
utmNorthGravi:
6804795
utmZoneInlet:
33
utmEastInlet:
-27317
utmNorthInlet:
6807065
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
82.95
specificDischarge:
125.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:
44
qStartYear:
1964
qEndYear:
2024
qm:
28.9887
q5:
37.969
q10:
43.96
q20:
49.232
q50:
55.4275
hm:
2.1276
h5:
2.234
h10:
2.2964
h20:
2.3471
h50:
2.4025
culQm:
49.4687
culQ5:
64.7936
culQ10:
75.0171
culQ20:
84.0137
culQ50:
94.5863
culHm:
2.3493
culH5:
2.4792
culH10:
2.5554
culH20:
2.6172
culH50:
2.6848
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1998-01-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1998-01-01T11:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1998-06-03T14:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1998-01-01T11:00:00Z
  dataToTime:
  2026-08-02T11: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:
  1998-01-01T11:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1998-06-03T14:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1998-01-01T11:00:00Z
  dataToTime:
  2026-08-02T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2024-01-12T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  1440
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-20T11:00:00Z
  dataToTime:
  2026-08-03T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2006-10-18T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2006-10-18T12:45:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2006-10-18T14:00:00Z
  dataToTime:
  2026-08-03T05:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2006-10-19T11:00:00Z
  dataToTime:
  2026-08-02T11:00:00Z

limit:

offset:

returned:

has_more_results:

truncated:

Will you use the result in generated code?

Open the same result as JSON

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.