Ruisseau
Skelbæk
Crosses 1 administrative regions : Vordingborg
Total length
39km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- VordingborgSjælland · Denmark1.5 kmin this dpt
5 intersecting protected areas
The sea and coast between Præstø Fjord and Grønsund
IUCN Not ReportedBaltic Sea Protected Area (HELCOM)
Havet og kysten mellem Præstø Fjord og Grønsund
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Ulvsund, Grønsund og Farø Fjord
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Vordingborg Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Vordingborg Kommune public
IUCN IV§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
1 244 distinct species · 19 413 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 21 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 Skelbæk : 14 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 83 interactions GloBI sur 6 types (connectance 25.5%, filtre Serrano α=0.2). 12 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
39km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.