Ruisseau· 3 segments
Arvträskbäcken
Crosses 1 administrative regions : Sorsele
Total length
4km
Max discharge
2,1m³/s
Max Strahler
2
Segments matched
3
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- SorseleVästerbotten · Sweden12.2 kmin this dpt
11 intersecting protected areas
2001842 Vindelfjällen
IUCN IbNature Reserve
2047424 Blaiken
IUCN IbNature Reserve
1073656288
IUCN Not ApplicableVoluntary set-aside areas
1073680346
IUCN Not ApplicableVoluntary set-aside areas
1073656343
IUCN Not ApplicableVoluntary set-aside areas
1073656333
IUCN Not ApplicableVoluntary set-aside areas
A383276
IUCN Not ApplicableVoluntary set-aside areas
1073656294
IUCN Not ApplicableVoluntary set-aside areas
1073656259
IUCN Not ApplicableVoluntary set-aside areas
2 more protected areassorted by area
1073656311
IUCN Not ApplicableVoluntary set-aside areas
1073656293
IUCN Not ApplicableVoluntary set-aside areas
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
91 distinct species · 164 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 Arvträskbäcken : 19 espèces reliées par 26 interactions GloBI sur 3 types (connectance 8.7%, filtre Serrano α=0.2). 6 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
4km
Max discharge
2,1m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.