Ontologia

Ruisseau

Ophover Mühlenbach

Crosses 3 administrative regions : Köln, Leverkusen, Rheinisch-Bergischer Kreis

ruisseau

Total length

4km

Max discharge

1,7m³/s

Max Strahler

2

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803998102002 km²

3 administrative regions crossed (GADM L2)

  • Leverkusen
    Nordrhein-Westfalen · Germany
    10.5 km
    in this dpt
  • Rheinisch-Bergischer Kreis
    Nordrhein-Westfalen · Germany
    2.8 km
    in this dpt
  • Köln
    Nordrhein-Westfalen · Germany
    0.0 km
    in this dpt

30 intersecting protected areas

21 more protected areas

1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.

Species present

1 451 distinct species · 15 906 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Ophover Mühlenbach : 30 espèces reliées par 93 interactions GloBI sur 6 types (connectance 10.8%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
93
Connectance
0.108
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

4km

Max discharge

1,7m³/s

Max Strahler

2

Segments matched

1

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.