Ontologia

Ruisseau· 4 segments

Duolbakjuhka

Crosses 2 administrative regions : Arjeplog, Sorsele

ruisseau

Total length

11km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

4

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080145220478 km²

2 administrative regions crossed (GADM L2)

  • Arjeplog
    Norrbotten · Sweden
    12.8 km
    in this dpt
  • Sorsele
    Västerbotten · Sweden
    0.0 km
    in this dpt

11 intersecting protected areas

2 more protected areas

  • Laisälven

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Laisälven

    IUCN Not Assigned

    Natura 2000 SCI

1 page = 1 named river (aggregation of 4 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

113 distinct species · 145 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 27 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Duolbakjuhka : 20 espèces reliées par 46 interactions GloBI sur 3 types (connectance 13.1%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
27
Interactions affichées
46
Connectance
0.131
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

11km

Max discharge

1,4m³/s

Max Strahler

2

Segments matched

4

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.