Ruisseau· 3 segments
Pääskylänjoki
Crosses 1 administrative regions : Pirkanmaa
Total length
5km
Max discharge
0,5m³/s
Max Strahler
2
Segments matched
3
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- PirkanmaaWestern Finland · Finland12.3 kmin this dpt
7 intersecting protected areas
Metsälain erityisen tärkeät elinympäristöt Pirkanmaa
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Metsälain erityisen tärkeät elinympäristöt Keski-Suomi
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Metsätalouden ympäristötukikohteet Pirkanmaa
IUCN Not AssignedForestry environmental aid contracts (OECM)
Tampinniemi suomi100
IUCN IVPrivate Nature Reserve
RÄMESALON LUONNONSUOJELUALUE
IUCN IVPrivate Nature Reserve
Puolitaipaleen metsä
IUCN IVPrivate Nature Reserve
Tampinniemen metsä
IUCN IVPrivate Nature Reserve
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
420 distinct species · 3 816 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 32 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 Pääskylänjoki : 26 espèces reliées par 71 interactions GloBI sur 5 types (connectance 14.3%, 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
5km
Max discharge
0,5m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.