Fleuve· 509 segments
هلمند رود
Crosses 25 administrative regions : Char Burjak, Chora, Day Kundi, Dihrawud, Disho +20
Endorheicfleuve
Total length
1 318km
Max discharge
491,4m³/s
Max Strahler
7
Segments matched
509
River geography25 admin regions · 0 communes
25 administrative regions crossed (GADM L2)
- RegHilmand · Afghanistan262.1 kmin this dpt
- Char BurjakNimroz · Afghanistan257.8 kmin this dpt
- ShahristanDaykundi · Afghanistan218.0 kmin this dpt
- GizabDaykundi · Afghanistan205.8 kmin this dpt
- DihrawudUruzgan · Afghanistan164.3 kmin this dpt
- Markazi BihsudWardak · Afghanistan141.1 kmin this dpt
- Nahri SarrajHilmand · Afghanistan131.4 kmin this dpt
- WarasBamyan · Afghanistan129.3 kmin this dpt
- Shahidi HasasUruzgan · Afghanistan112.1 kmin this dpt
- GarmserHilmand · Afghanistan101.2 kmin this dpt
- SanginHilmand · Afghanistan88.5 kmin this dpt
- Hisa-i-Awali BihsudWardak · Afghanistan77.2 kmin this dpt
- LashkargahHilmand · Afghanistan77.0 kmin this dpt
- DishoHilmand · Afghanistan72.6 kmin this dpt
- JalrezWardak · Afghanistan58.0 kmin this dpt
- KajakiHilmand · Afghanistan35.2 kmin this dpt
- NawurGhazni · Afghanistan24.8 kmin this dpt
- Nawa-i-Barak ZayiHilmand · Afghanistan21.7 kmin this dpt
- Nad AliHilmand · Afghanistan13.2 kmin this dpt
- Musa QalaHilmand · Afghanistan12.0 kmin this dpt
- Day KundiDaykundi · Afghanistan6.2 kmin this dpt
- ZabolSistan and Baluchestan · Iran4.5 kmin this dpt
- ZaranjNimroz · Afghanistan3.6 kmin this dpt
- NeshUruzgan · Afghanistan0.0 kmin this dpt
- ChoraUruzgan · Afghanistan0.0 kmin this dpt
1 page = 1 named river (aggregation of 509 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
0 distinct species · 0 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Graphe en cours d’indexation
Calcul du tissu écologique de cette entité.
Le graphe apparaîtra automatiquement dès que le calcul est terminé (rafraîchissement toutes les 2s).
Hydrology (HydroRIVERS v10)
Total length
1 318km
Max discharge
491,4m³/s
Max Strahler
7
Segments matched
509
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.