Ruisseau· 11 segments
Kivijoki
Crosses 2 administrative regions : Lapland, Northern Ostrobothnia
Total length
127km
Max discharge
7m³/s
Max Strahler
3
Segments matched
11
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- LaplandLapland · Finland22.6 kmin this dpt
- Northern OstrobothniaOulu · Finland13.7 kmin this dpt
6 intersecting protected areas
Litokaira
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Litokaira
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Protected Mire
Metsälain erityisen tärkeät elinympäristöt Pohjois-Pohjanmaa
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Metsätalouden ympäristötukikohteet Pohjois-Pohjanmaa
IUCN Not AssignedForestry environmental aid contracts (OECM)
Vääränaho
IUCN IVPrivate Nature Reserve
1 page = 1 named river (aggregation of 11 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
99 distinct species · 288 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 33 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Kivijoki : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 40 interactions GloBI sur 4 types (connectance 7.1%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
127km
Max discharge
7,0m³/s
Max Strahler
3
Segments matched
11
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.