Ontologia

Fleuve· 40 segments

Есауловка

Crosses 4 administrative regions : Berezovskiy rayon, Manskiy rayon, Sosnovoborsk, Uyarskiy rayon

fleuve

Total length

187km

Max discharge

2 756,5m³/s

Max Strahler

8

Segments matched

40

River geography4 admin regions · 0 communes

Parent watershed

hybas-30805441201474 km²

4 administrative regions crossed (GADM L2)

  • Manskiy rayon
    Krasnoyarsk · Russia
    112.8 km
    in this dpt
  • Berezovskiy rayon
    Krasnoyarsk · Russia
    40.7 km
    in this dpt
  • Uyarskiy rayon
    Krasnoyarsk · Russia
    15.5 km
    in this dpt
  • Sosnovoborsk
    Krasnoyarsk · Russia
    0.3 km
    in this dpt

1 intersecting protected areas

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

Species present

32 distinct species · 38 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 15 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 Есауловка : 15 espèces reliées par 13 interactions GloBI sur 2 types (connectance 12.4%, filtre Serrano α=0.2).

Espèces affichées
15
Interactions affichées
13
Connectance
0.124
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

187km

Max discharge

2 756,5m³/s

Max Strahler

8

Segments matched

40

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