Ruisseau
Slătinicul Mare
Crosses 2 administrative regions : Drobeta-turnu Severin, Kladovo
Total length
3km
Max discharge
0m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- KladovoBorski · Serbia0.5 kmin this dpt
- Drobeta-turnu SeverinMehedinți · Romania0.0 kmin this dpt
9 intersecting protected areas
Natural park
Porțile de Fier
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Munții Almăjului - Locvei
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Djerdap
IUCN VWetland of International Importance (Ramsar Site)
DJERDAP
IUCN Not ReportedEmerald Network
Nacionalni park Djerdap
IUCN IINational Park
Cursul Dunării - Baziaș - Porțile de Fier
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Gura Vaii - Vârciorova
IUCN IVNature reserve
Fața Virului
IUCN IVNature reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
228 distinct species · 479 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 Slătinicul Mare : 19 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 63 interactions GloBI sur 5 types (connectance 14.5%, filtre Serrano α=0.2). 11 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
3km
Max discharge
0,0m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.