Ruisseau· 4 segments
Tuurinluoma
Crosses 2 administrative regions : Ostrobothnia, Southern Ostrobothnia
Total length
14km
Max discharge
1,1m³/s
Max Strahler
2
Segments matched
4
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- OstrobothniaWestern Finland · Finland18.7 kmin this dpt
- Southern OstrobothniaWestern Finland · Finland5.3 kmin this dpt
6 intersecting protected areas
Levanevan luonnonsuojelualue
IUCN IbState Nature Reserve
Levaneva
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Levaneva
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Levaneva Mires
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Metsälain erityisen tärkeät elinympäristöt Pohjanmaa
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Levaneva 1
IUCN IVPrivate Nature Reserve
1 page = 1 named river (aggregation of 4 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
109 distinct species · 702 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 30 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 Tuurinluoma : 24 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 47 interactions GloBI sur 4 types (connectance 10.8%, filtre Serrano α=0.2). 6 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
14km
Max discharge
1,1m³/s
Max Strahler
2
Segments matched
4
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.