Ruisseau
Sularpsbäcken
Crosses 2 administrative regions : Eslöv, Lund
Total length
8km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
11 intersecting protected areas
Kungsmarken
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Kungsmarken
IUCN IVNatura 2000 SCI
2001532 Kungsmarken
IUCN IVNature Reserve
2042006 Flyinge ängar
IUCN IVNature Reserve
Fågelsångsdalen
IUCN IVNatura 2000 SCI
Fågelsångsdalen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
2001533 Fågelsångsdalen
IUCN IVNature Reserve
2021949 Sularpskärret
IUCN Not AssignedNature Reserve
2001535 Maskängen
IUCN IVNature Reserve
2 more protected areassorted by area
Sularpskärret
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Sularpskärret
IUCN Not AssignedNatura 2000 SCI
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
5 459 distinct species · 121 049 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 33 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 Sularpsbäcken : 24 espèces reliées par 68 interactions GloBI sur 4 types (connectance 12.1%, filtre Serrano α=0.2). 10 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
8km
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.