Ontologia

Ruisseau· 2 segments

Linderbeek

Crosses 3 administrative regions : Hellendoorn, Ommen, Twenterand

ruisseau

Total length

10km

Max discharge

4m³/s

Max Strahler

3

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803645501120 km²

3 administrative regions crossed (GADM L2)

  • Twenterand
    Overijssel · Netherlands
    7.4 km
    in this dpt
  • Ommen
    Overijssel · Netherlands
    1.3 km
    in this dpt
  • Hellendoorn
    Overijssel · Netherlands
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

1 429 distinct species · 12 904 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 Linderbeek : 25 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 142 interactions GloBI sur 5 types (connectance 15.7%, filtre Serrano α=0.2). 18 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
142
Connectance
0.157
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

10km

Max discharge

4,0m³/s

Max Strahler

3

Segments matched

2

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