Ontologia

Ruisseau· 2 segments

Karusilma oja

Crosses 4 administrative regions : Jõgeva (commune), Palamuse, Saare, Torma

ruisseau

Total length

12km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-20802513401056 km²

4 administrative regions crossed (GADM L2)

  • Torma
    Jõgeva · Estonia
    4.1 km
    in this dpt
  • Saare
    Jõgeva · Estonia
    1.4 km
    in this dpt
  • Jõgeva (commune)
    Jõgeva · Estonia
    0.6 km
    in this dpt
  • Palamuse
    Jõgeva · Estonia
    0.4 km
    in this dpt

7 intersecting protected areas

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

Species present

208 distinct species · 824 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Karusilma oja : 28 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 50 interactions GloBI sur 7 types (connectance 8.9%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
50
Connectance
0.089
Patrimoniales
1
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

12km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

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