Ruisseau· 3 segments
Ohrenbach
Crosses 3 administrative regions : Bayreuth, Miltenberg, Odenwaldkreis
Total length
14km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
3
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- MiltenbergBayern · Germany8.0 kmin this dpt
- BayreuthBayern · Germany1.9 kmin this dpt
- OdenwaldkreisHessen · Germany0.9 kmin this dpt
6 intersecting protected areas
Landscape Protection Area
LSG "Oberes Rotmaintal"
IUCN VLandscape Protection Area
Rotmain-, Mistelbach- und Ölschnitztal um Bayreuth
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Täler der Odenwald-Bäche um Amorbach
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Geierstal von Vielbrunn
IUCN IVNature Reserve
Ohrenbach zwischen Bremhof und Ohrenbach
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
949 distinct species · 2 571 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 26 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 Ohrenbach : 20 espèces reliées par 54 interactions GloBI sur 5 types (connectance 16.6%, filtre Serrano α=0.2). 6 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
14km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.