Ruisseau· 3 segments
Телиця
Crosses 2 administrative regions : Dubens'kyi, Shums'kyi
Total length
16km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
3
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Shums'kyiTernopil' · Ukraine9.5 kmin this dpt
- Dubens'kyiRivne · Ukraine5.2 kmin this dpt
10 intersecting protected areas
Ostrozka prohidna dolyna
IUCN Not ReportedEmerald Network
Kremenetski hory
IUCN Not ReportedNational nature park
Kremenetski Hory National Nature Park
IUCN Not ReportedEmerald Network
Mizotskyi kriazh
IUCN Not ReportedZakaznyk
Volynskyi
IUCN Not ReportedZakaznyk
Stizhotski chornytsi № 1
IUCN Not ReportedZakaznyk
Stizhotski chornytsi № 2
IUCN Not ReportedZakaznyk
Antonivetskyi sosniak
IUCN Not ReportedNatural monument
Danylova hora
IUCN Not ReportedNatural monument
1 more protected areassorted by area
Hora Uniias
IUCN Not ReportedNatural monument
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
60 distinct species · 149 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 29 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 Телиця : 26 espèces reliées par 34 interactions GloBI sur 2 types (connectance 8.4%, filtre Serrano α=0.2). 3 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
16km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.