Fleuve· 75 segments
Koshi
Crosses 10 administrative regions : Bhagalpur, Katihar, Khagaria, Koshi, Madhepura +5
Total length
323km
Max discharge
2 293,1m³/s
Max Strahler
7
Segments matched
75
River geography10 admin regions · 0 communes
10 administrative regions crossed (GADM L2)
- BhagalpurBihar · India87.9 kmin this dpt
- SupaulBihar · India74.7 kmin this dpt
- SaharsaBihar · India74.4 kmin this dpt
- KhagariaBihar · India51.3 kmin this dpt
- SagarmathaEast · Nepal41.4 kmin this dpt
- KoshiEast · Nepal33.3 kmin this dpt
- MadhepuraBihar · India16.2 kmin this dpt
- KatiharBihar · India10.6 kmin this dpt
- PurniaBihar · India0.6 kmin this dpt
- SamastipurBihar · India0.0 kmin this dpt
3 intersecting protected areas
Koshi Tappu - Buffer Zone
IUCN VIWildlife Reserve - Buffer Zone
Koshi Tappu
IUCN IVWildlife Reserve
Koshi Tappu
IUCN Not ReportedWetland of International Importance (Ramsar Site)
1 page = 1 named river (aggregation of 75 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
64 distinct species · 173 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 22 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 Koshi : 19 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 18 interactions GloBI sur 4 types (connectance 7.8%, filtre Serrano α=0.2). 3 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
323km
Max discharge
2 293,1m³/s
Max Strahler
7
Segments matched
75
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.