Ontologia

Ruisseau· 18 segments

Кесьма

Crosses 4 administrative regions : Sandovskiy rayon, Ves'egonskiy rayon, Water body

ruisseau

Total length

92km

Max discharge

4,7m³/s

Max Strahler

3

Segments matched

18

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080253320678 km²

4 administrative regions crossed (GADM L2)

  • Ves'egonskiy rayon
    Tver' · Russia
    67.6 km
    in this dpt
  • Water body
    Tver' · Russia
    2.6 km
    in this dpt
  • Sandovskiy rayon
    Tver' · Russia
    1.0 km
    in this dpt
  • Water body
    Vologda · Russia
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

55 distinct species · 73 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 28 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 Кесьма : 24 espèces reliées par 39 interactions GloBI sur 4 types (connectance 10.3%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
28
Interactions affichées
39
Connectance
0.103
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

92km

Max discharge

4,7m³/s

Max Strahler

3

Segments matched

18

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