Rivière
Elsterflutbett
Crosses 2 administrative regions : Leipzig, Leipzig (Kreisfreie Stadt)
Total length
4km
Max discharge
17m³/s
Max Strahler
4
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Leipzig (Kreisfreie Stadt)Sachsen · Germany8.2 kmin this dpt
- LeipzigSachsen · Germany4.8 kmin this dpt
8 intersecting protected areas
Leipziger Auwald
IUCN VLandscape Protection Area
Leipziger Auwald
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Elsteraue
IUCN VLandscape Protection Area
Leipziger Auensystem
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Elsteraue südlich Zwenkau
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Elsteraue bei Groitzsch
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Elster- und Pleiße-Auwald
IUCN IVNature Reserve
Lehmlache Lauer
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 003 distinct species · 26 358 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 36 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 Elsterflutbett : 25 espèces reliées par 67 interactions GloBI sur 5 types (connectance 10.6%, 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
4km
Max discharge
17,0m³/s
Max Strahler
4
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.