Ruisseau· 5 segments
Udtjabäcken
Crosses 2 administrative regions : Arjeplog, Jokkmokk
Total length
23km
Max discharge
1,5m³/s
Max Strahler
2
Segments matched
5
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
11 intersecting protected areas
Udtja
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Udtja
IUCN IbNatura 2000 SCI
2001270 Udtja
IUCN IbNature Reserve
Piteälven
IUCN Not AssignedNatura 2000 SCI
Piteälven
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1073687236
IUCN Not ApplicableVoluntary set-aside areas
1073687348
IUCN Not ApplicableVoluntary set-aside areas
1073680714
IUCN Not ApplicableVoluntary set-aside areas
1073680738
IUCN Not ApplicableVoluntary set-aside areas
2 more protected areassorted by area
1073689032
IUCN Not ApplicableVoluntary set-aside areas
1073690209
IUCN Not ApplicableVoluntary set-aside areas
1 page = 1 named river (aggregation of 5 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
120 distinct species · 144 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 20 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 Udtjabäcken : 18 espèces reliées par 15 interactions GloBI sur 1 type (connectance 7.9%, filtre Serrano α=0.2). 2 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
23km
Max discharge
1,5m³/s
Max Strahler
2
Segments matched
5
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.