Ontologia

Ruisseau· 2 segments

Zilupe / Сінюха

Crosses 3 administrative regions : Ludza, Sebezhskiy rayon, Vyerkhnyazdvinsk

ruisseau

Total length

8km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-20802751402042 km²

3 administrative regions crossed (GADM L2)

5 intersecting protected areas

  • Sebezhskij

    IUCN II

    National Park

  • Osveiski

    IUCN IV

    Wetland of International Importance (Ramsar Site)

  • Osveyskiy

    IUCN IV

    Nature Sanctuary or Partial Reserve

  • Nature Reserve

  • Grebļukalns

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

31 distinct species · 34 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 10 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 Zilupe / Сінюха : 10 espèces reliées par 7 interactions GloBI sur 3 types (connectance 15.6%, filtre Serrano α=0.2).

Espèces affichées
10
Interactions affichées
7
Connectance
0.156
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

8km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

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