Ontologia

Ruisseau

Hörner Bach

Crosses 3 administrative regions : Borken, Grafschaft Bentheim, Steinfurt

ruisseau

Total length

3km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803614601606 km²

3 administrative regions crossed (GADM L2)

  • Steinfurt
    Nordrhein-Westfalen · Germany
    8.0 km
    in this dpt
  • Borken
    Nordrhein-Westfalen · Germany
    3.6 km
    in this dpt
  • Grafschaft Bentheim
    Niedersachsen · Germany
    0.7 km
    in this dpt

10 intersecting protected areas

1 more protected areas

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

Species present

714 distinct species · 3 848 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Hörner Bach : 16 espèces reliées par 94 interactions GloBI sur 6 types (connectance 20.2%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
94
Connectance
0.202
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

3km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

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