Rivière
Nackbäcken
⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 5 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.
Crosses 1 administrative regions : Lycksele
Max discharge
195,6m³/s
Max Strahler
5
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- LyckseleVästerbotten · Sweden4.8 kmin this dpt
6 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
A024411
IUCN Not ApplicableVoluntary set-aside areas
A025842
IUCN Not ApplicableVoluntary set-aside areas
A607316
IUCN Not ApplicableVoluntary set-aside areas
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
121 distinct species · 230 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 32 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 Nackbäcken : 28 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 28 interactions GloBI sur 4 types (connectance 5.6%, 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)
Matched len.
3,9km
Max discharge
195,6m³/s
Max Strahler
5
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.