Ruisseau· 2 segments
Kelhujoki
Crosses 1 administrative regions : Lapland
Total length
14km
Max discharge
2,6m³/s
Max Strahler
3
Segments matched
2
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- LaplandLapland · Finland15.7 kmin this dpt
7 intersecting protected areas
Tornionjoen-Muonionjoen vesistöalue
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Metsälain erityisen tärkeät elinympäristöt Lappi
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Protected Mire
Wetland of International Importance (Ramsar Site)
Teuravuoma-Kivijärvenvuoma
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Teuravuoma-Kivijärvenvuoma
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Välimaan luonnonsuojelualue
IUCN IVPrivate Nature Reserve
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
84 distinct species · 335 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 27 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 Kelhujoki : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 22 interactions GloBI sur 3 types (connectance 6.3%, filtre Serrano α=0.2). 1 bulle taxonomique (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
14km
Max discharge
2,6m³/s
Max Strahler
3
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.