Ontologia

Ruisseau· 2 segments

Hasseler Mühlenbach

Crosses 2 administrative regions : Gelsenkirchen, Recklinghausen

ruisseau

Total length

3km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

2

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080387720648 km²

2 administrative regions crossed (GADM L2)

  • Gelsenkirchen
    Nordrhein-Westfalen · Germany
    2.0 km
    in this dpt
  • Recklinghausen
    Nordrhein-Westfalen · Germany
    1.1 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

1 133 distinct species · 9 983 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 Hasseler Mühlenbach : 29 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 148 interactions GloBI sur 6 types (connectance 15.6%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
148
Connectance
0.156
Patrimoniales
1
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

3km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

2

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