Ontologia

Ruisseau· 4 segments

Borșa

Crosses 5 administrative regions : Aschileu Mare, Bontida, Borsa, Dragu, Vultureni

ruisseau

Total length

44km

Max discharge

1,7m³/s

Max Strahler

3

Segments matched

4

River geography5 admin regions · 0 communes

Parent watershed

hybas-2080510460641 km²

5 administrative regions crossed (GADM L2)

  • Borsa
    Cluj · Romania
    13.9 km
    in this dpt
  • Bontida
    Cluj · Romania
    6.5 km
    in this dpt
  • Aschileu Mare
    Cluj · Romania
    5.3 km
    in this dpt
  • Vultureni
    Cluj · Romania
    2.3 km
    in this dpt
  • Dragu
    Sălaj · Romania
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

34 distinct species · 50 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 16 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 Borșa : 15 espèces reliées par 12 interactions GloBI sur 3 types (connectance 10.0%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
16
Interactions affichées
12
Connectance
0.100
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

44km

Max discharge

1,7m³/s

Max Strahler

3

Segments matched

4

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