Ruisseau
Maglemose Rende
Crosses 2 administrative regions : Hørsholm, Rudersdal
Total length
5km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
7 intersecting protected areas
W
IUCN IVMarine Strategy Area
Rudersdal Kommune public
IUCN IV§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Hørsholm Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Rudersdal Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Folehave skov
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Maglemosen
IUCN VProtected by conservation order, excl. Church surroundings
Kohavevej
IUCN IVProtected by conservation order, excl. Church surroundings
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
3 739 distinct species · 47 844 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).
Indicateurs du tissu écologique
Tissu écologique de Maglemose Rende : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 92 interactions GloBI sur 6 types (connectance 12.4%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
5km
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.