Ruisseau
Vellingebäcken
Crosses 2 administrative regions : Malmö, Vellinge
Total length
3km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
9 intersecting protected areas
Falsterbo Peninsula with Måkläppen
IUCN Not ReportedBaltic Sea Protected Area (HELCOM)
Falsterbo-Foteviken
IUCN VNatura 2000 SPA
Falsterbo-Foteviken
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Falsterbohalvön
IUCN VNatura 2000 SCI
Falsterbohalvön
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Falsterbo-Foteviken
IUCN IbWetland of International Importance (Ramsar Site)
2027150 Foteviksområdet
IUCN VNature Reserve
Vellinge ängar
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Vellinge ängar
IUCN VNatura 2000 SCI
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 342 distinct species · 71 557 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 22 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 Vellingebäcken : 13 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 71 interactions GloBI sur 3 types (connectance 23.7%, 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
3km
Max discharge
0,2m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.