Ontologia

Ruisseau

Lunterse Beek

Crosses 5 administrative regions : Ede, Renswoude, Scherpenzeel, Utrechtse Heuvelrug, Woudenberg

ruisseau

Total length

11km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

River geography5 admin regions · 0 communes

Parent watershed

hybas-20800232601668 km²

5 administrative regions crossed (GADM L2)

2 intersecting protected areas

  • NNN-GE

    IUCN Not Assigned

    Nature Reserves owned by professional nature management organizations

  • NNN-UT

    IUCN Not Assigned

    Nature Reserves owned by professional nature management organizations

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

Species present

2 396 distinct species · 39 917 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
40
Interactions affichées
123
Connectance
0.158
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

11km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

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