Ontologia

Rivière· 7 segments

Storbekken

Crosses 4 administrative regions : Meldal, Rennebu, Rindal, Surnadal

rivière

Total length

1 038km

Max discharge

51,7m³/s

Max Strahler

5

Segments matched

7

River geography4 admin regions · 0 communes

Parent watershed

hybas-20800361101308 km²

4 administrative regions crossed (GADM L2)

  • Surnadal
    Møre og Romsdal · Norway
    6.3 km
    in this dpt
  • Rindal
    Møre og Romsdal · Norway
    5.9 km
    in this dpt
  • Rennebu
    Sør-Trøndelag · Norway
    2.1 km
    in this dpt
  • Meldal
    Sør-Trøndelag · Norway
    0.5 km
    in this dpt

5 intersecting protected areas

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

Species present

605 distinct species · 2 427 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Storbekken : 29 espèces reliées par 50 interactions GloBI sur 4 types (connectance 8.4%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
50
Connectance
0.084
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

1 038km

Max discharge

51,7m³/s

Max Strahler

5

Segments matched

7

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