Ruisseau· 2 segments
Kesselbach
Crosses 2 administrative regions : Hochsauerlandkreis, Rheingau-Taunus-Kreis
Total length
115km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
2
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Rheingau-Taunus-KreisHessen · Germany4.7 kmin this dpt
- HochsauerlandkreisNordrhein-Westfalen · Germany1.4 kmin this dpt
13 intersecting protected areas
LSG-Meschede
IUCN VLandscape Protection Area
Ruhr
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Landscape Protection Area
Nature Reserve
Wenne
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
NSG Freienohler Ruhrtal
IUCN IVNature Reserve
Landscape Protection Area
Landscape Protection Area
Landscape Protection Area
4 more protected areassorted by area
Landscape Protection Area
Landscape Protection Area
Landscape Protection Area
Landscape Protection Area
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
749 distinct species · 2 109 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 32 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 Kesselbach : 18 espèces reliées par 133 interactions GloBI sur 6 types (connectance 22.4%, filtre Serrano α=0.2). 17 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
115km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.