Ruisseau· 5 segments
Негованка
Crosses 4 administrative regions : Pavlikeni, Sevlievo, Suhindol, Veliko Tarnovo
Total length
37km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
5
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- PavlikeniVeliko Tarnovo · Bulgaria19.9 kmin this dpt
- SevlievoGabrovo · Bulgaria18.5 kmin this dpt
- Veliko TarnovoVeliko Tarnovo · Bulgaria9.1 kmin this dpt
- SuhindolVeliko Tarnovo · Bulgaria0.9 kmin this dpt
8 intersecting protected areas
Reka Rositsa
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Emen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Protected Site
Emenski kanion
IUCN IIINatural Monument
Komitskite dupki
IUCN VIProtected Site
Momin skok
IUCN IIINatural Monument
Ponorite
IUCN IIINatural Monument
Peshtera Musina
IUCN IIINatural Monument
1 page = 1 named river (aggregation of 5 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
202 distinct species · 342 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 40 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 Негованка : 27 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 129 interactions GloBI sur 5 types (connectance 15.7%, filtre Serrano α=0.2). 14 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
37km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
5
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.