Rivière· 22 segments
Протока
Crosses 6 administrative regions : Bilotserkivs'ka, Bilotserkivs'kyi, Bilozers'kyi, Holoprystans'kyi, Tsiurupyns'kyi +1
Total length
459km
Max discharge
17,2m³/s
Max Strahler
4
Segments matched
22
River geography6 admin regions · 0 communes
6 administrative regions crossed (GADM L2)
- Vasyl'kivs'kyiKiev · Ukraine58.3 kmin this dpt
- Bilotserkivs'kyiKiev · Ukraine25.0 kmin this dpt
- Bilozers'kyiKherson · Ukraine8.6 kmin this dpt
- Bilotserkivs'kaKiev · Ukraine4.8 kmin this dpt
- Tsiurupyns'kyiKherson · Ukraine1.7 kmin this dpt
- Holoprystans'kyiKherson · Ukraine1.7 kmin this dpt
5 intersecting protected areas
Nyzhnodniprovskyi
IUCN Not ReportedNational nature park
Lower Dnipro
IUCN Not ReportedEmerald Network
Ros river valley
IUCN Not ReportedEmerald Network
Dnipro River Delta
IUCN IIWetland of International Importance (Ramsar Site)
Bobrove Ozero
IUCN Not ReportedZakaznyk
1 page = 1 named river (aggregation of 22 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
66 distinct species · 87 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 34 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 Протока : 32 espèces reliées par 31 interactions GloBI sur 4 types (connectance 5.5%, filtre Serrano α=0.2). 2 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
459km
Max discharge
17,2m³/s
Max Strahler
4
Segments matched
22
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.