Ruisseau· 9 segments
Tyrnävänjoki
Crosses 1 administrative regions : Northern Ostrobothnia
Total length
65km
Max discharge
8,5m³/s
Max Strahler
3
Segments matched
9
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Northern OstrobothniaOulu · Finland68.0 kmin this dpt
6 intersecting protected areas
Metsälain erityisen tärkeät elinympäristöt Pohjois-Pohjanmaa
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Veneneva-Pelso
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Veneneva-Pelso
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Veneneva-Pelso Mires
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Venenevan luonnonsuojelualue
IUCN IbState Nature Reserve
Metsätalouden ympäristötukikohteet Pohjois-Pohjanmaa
IUCN Not AssignedForestry environmental aid contracts (OECM)
1 page = 1 named river (aggregation of 9 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
298 distinct species · 1 165 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 35 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 Tyrnävänjoki : 20 espèces reliées par 139 interactions GloBI sur 5 types (connectance 18.8%, filtre Serrano α=0.2). 19 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
65km
Max discharge
8,5m³/s
Max Strahler
3
Segments matched
9
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.