Ruisseau· 2 segments
Euterbach
Crosses 3 administrative regions : Miltenberg, Odenwaldkreis, Rhein-Neckar-Kreis
Total length
7km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- OdenwaldkreisHessen · Germany3.9 kmin this dpt
- Rhein-Neckar-KreisBaden-Württemberg · Germany0.4 kmin this dpt
- MiltenbergBayern · Germany0.0 kmin this dpt
5 intersecting protected areas
Südlicher Odenwald
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Neckartal II - Eberbach
IUCN VLandscape Protection Area
Odenwald Eberbach
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Euterbach und Itterbach mit Nebenbächen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Leegwald und Höllklinge bei Kailbach
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
980 distinct species · 8 653 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 31 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 Euterbach : 23 espèces reliées par 68 interactions GloBI sur 7 types (connectance 14.6%, filtre Serrano α=0.2). 8 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
7km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.