Ruisseau· 13 segments
Грузький Яланчик
Crosses 4 administrative regions : Neklinovskiy rayon, Novoazovs'kyi, Starobeshivs'kyi, Tel'manivs'kyi
Total length
180km
Max discharge
5,2m³/s
Max Strahler
3
Segments matched
13
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- Tel'manivs'kyiDonets'k · Ukraine33.5 kmin this dpt
- Novoazovs'kyiDonets'k · Ukraine17.3 kmin this dpt
- Starobeshivs'kyiDonets'k · Ukraine8.7 kmin this dpt
- Neklinovskiy rayonRostov · Russia0.0 kmin this dpt
7 intersecting protected areas
Meotyda
IUCN Not ReportedEmerald Network
Kryva Bay and Kryva Spit
IUCN IIWetland of International Importance (Ramsar Site)
Meotyda
IUCN Not ReportedNational nature park
Ukrainskyi Stepovyi Nature Reserve
IUCN Not ReportedEmerald Network
Ukrainskyi stepovyi
IUCN Not ReportedNature reserve
Dzherelo bilia sela Konkove
IUCN Not ReportedNatural monument
Pechera
IUCN Not ReportedNatural monument
1 page = 1 named river (aggregation of 13 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
10 distinct species · 20 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 3 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 Грузький Яланчик : 3 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 2 interactions GloBI sur 1 type (connectance 66.7%, filtre Serrano α=0.2).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
180km
Max discharge
5,2m³/s
Max Strahler
3
Segments matched
13
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.