Rivière· 159 segments
Río Aguán
Crosses 12 administrative regions : Arenal, Bonito Oriental, Jocón, La Unión, Mangulile +7
Total length
336km
Max discharge
181,2m³/s
Max Strahler
5
Segments matched
159
River geography12 admin regions · 0 communes
12 administrative regions crossed (GADM L2)
- OlanchitoYoro · Honduras210.1 kmin this dpt
- YoroYoro · Honduras77.8 kmin this dpt
- MangulileOlancho · Honduras54.4 kmin this dpt
- TocoaColón · Honduras54.0 kmin this dpt
- TrujilloColón · Honduras43.7 kmin this dpt
- ArenalYoro · Honduras30.2 kmin this dpt
- JocónYoro · Honduras22.7 kmin this dpt
- SonagueraColón · Honduras21.2 kmin this dpt
- SabáColón · Honduras20.9 kmin this dpt
- La UniónOlancho · Honduras13.6 kmin this dpt
- YocónOlancho · Honduras5.6 kmin this dpt
- Bonito OrientalColón · Honduras3.7 kmin this dpt
2 intersecting protected areas
Pico Bonito
IUCN IINational Park
Colibrí Esmeralda Hondureño
IUCN IVWildlife Refuge
1 page = 1 named river (aggregation of 159 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
8 distinct species · 28 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 4 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 Río Aguán : 4 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 3 interactions GloBI sur 2 types (connectance 50.0%, filtre Serrano α=0.2).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
336km
Max discharge
181,2m³/s
Max Strahler
5
Segments matched
159
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.