Ruisseau
Wipper
Crosses 2 administrative regions : Märkischer Kreis, Oberbergischer Kreis
Total length
199km
Max discharge
0,4m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Oberbergischer KreisNordrhein-Westfalen · Germany6.6 kmin this dpt
- Märkischer KreisNordrhein-Westfalen · Germany0.3 kmin this dpt
10 intersecting protected areas
Landscape Protection Area
Landscape Protection Area
LSG-Kierspe - Typ A
IUCN VLandscape Protection Area
Landscape Protection Area
LSG-Kierspe - Typ B
IUCN VLandscape Protection Area
Wupper und Wipper bei Wipperfürth
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
NSG Wupperaue
IUCN IVNature Reserve
NSG Wipperaue Eulenbecke
IUCN IVNature Reserve
NSG Steinbruch am Wahlberg
IUCN IVNature Reserve
1 more protected areassorted by area
NSG Wupperaue bei Gogarten
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
905 distinct species · 6 808 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 Wipper : 13 espèces reliées par 118 interactions GloBI sur 6 types (connectance 19.8%, filtre Serrano α=0.2). 22 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
199km
Max discharge
0,4m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.