Ontologia

Ruisseau· 2 segments

Heiligenbergerbeek

Crosses 2 administrative regions : Amersfoort, Leusden

ruisseau

Total length

9km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

River geography2 admin regions · 0 communes

Parent watershed

hybas-20800232601668 km²

2 administrative regions crossed (GADM L2)

  • Leusden
    Utrecht · Netherlands
    4.0 km
    in this dpt
  • Amersfoort
    Utrecht · Netherlands
    3.3 km
    in this dpt

2 intersecting protected areas

  • NNN-UT

    IUCN Not Assigned

    Nature Reserves owned by professional nature management organizations

  • National Park

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

Species present

6 070 distinct species · 420 994 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Heiligenbergerbeek : 28 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 95 interactions GloBI sur 5 types (connectance 16.0%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
95
Connectance
0.160
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

9km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

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