Ontologia

Ruisseau

Želobudzský potok

Crosses 2 administrative regions : Detva, Zvolen

ruisseau

Total length

7km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080465900802 km²

2 administrative regions crossed (GADM L2)

  • Zvolen
    Banskobystrický · Slovakia
    2.5 km
    in this dpt
  • Detva
    Banskobystrický · Slovakia
    1.8 km
    in this dpt

2 intersecting protected areas

  • Poľana

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Hradné lúky

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

587 distinct species · 2 292 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 24 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 Želobudzský potok : 19 espèces reliées par 78 interactions GloBI sur 4 types (connectance 28.3%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
24
Interactions affichées
78
Connectance
0.283
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

7km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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