Ruisseau· 18 segments
Jukskei River
Crosses 4 administrative regions : City of Johannesburg, City of Tshwane, Ekurhuleni, West Rand
Total length
66km
Max discharge
0,9m³/s
Max Strahler
3
Segments matched
18
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- City of JohannesburgGauteng · South Africa50.7 kmin this dpt
- City of TshwaneGauteng · South Africa13.0 kmin this dpt
- EkurhuleniGauteng · South Africa8.4 kmin this dpt
- West RandGauteng · South Africa0.0 kmin this dpt
4 intersecting protected areas
Diepsloot Nature Reserve
IUCN Not ReportedNature Reserve
Crocodile River Reserve Central Nature Reserve Cluster
IUCN Not ReportedNature Reserve
Crocodile River Reserve Protected Environment
IUCN Not ReportedProtected Environment
Crocodile River Reserve Doornrandje Nature Reserve Cluster
IUCN Not ReportedNature Reserve
1 page = 1 named river (aggregation of 18 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 021 distinct species · 14 681 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 37 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).
Indicateurs du tissu écologique
Tissu écologique de Jukskei River : 30 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 37 interactions GloBI sur 4 types (connectance 5.3%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
66km
Max discharge
0,9m³/s
Max Strahler
3
Segments matched
18
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.