Ruisseau· 3 segments
Asbach
Crosses 3 administrative regions : Neckar-Odenwald-Kreis, Oberbergischer Kreis, Rhein-Neckar-Kreis
Total length
81km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
3
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- Neckar-Odenwald-KreisBaden-Württemberg · Germany2.5 kmin this dpt
- Oberbergischer KreisNordrhein-Westfalen · Germany1.7 kmin this dpt
- Rhein-Neckar-KreisBaden-Württemberg · Germany0.1 kmin this dpt
8 intersecting protected areas
Landscape Protection Area
Landscape Protection Area
Nördlicher Kraichgau
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Landscape Protection Area
NSG Wiehlaue Bruechermuehle
IUCN IVNature Reserve
NSG Asbachtal
IUCN IVNature Reserve
Nature Reserve
Grünlandkomplex westlich Löffelsterz
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
2 736 distinct species · 32 442 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 43 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 Asbach : 35 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 95 interactions GloBI sur 5 types (connectance 10.0%, filtre Serrano α=0.2). 9 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
81km
Max discharge
0,3m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.