Ruisseau· 13 segments
Lycksabäcken
Crosses 3 administrative regions : Lycksele, Sorsele, Storuman
Total length
68km
Max discharge
3,2m³/s
Max Strahler
3
Segments matched
13
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
10 intersecting protected areas
Vindelälven
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Vindelälven
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Vindelälven
IUCN Not AssignedNatura 2000 SCI
A550189
IUCN Not ApplicableVoluntary set-aside areas
A053373
IUCN Not ApplicableVoluntary set-aside areas
A316738
IUCN Not ApplicableVoluntary set-aside areas
A472694
IUCN Not ApplicableVoluntary set-aside areas
SK 865-2004
IUCN IaHabitat Protection Area
SK 312-2002
IUCN IaHabitat Protection Area
1 more protected areassorted by area
SK 209-2009
IUCN IVNature conservation agreement, Swedish Forest Agency
1 page = 1 named river (aggregation of 13 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
119 distinct species · 848 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 24 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 Lycksabäcken : 21 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 24 interactions GloBI sur 2 types (connectance 8.0%, filtre Serrano α=0.2). 4 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
68km
Max discharge
3,2m³/s
Max Strahler
3
Segments matched
13
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.