Ontologia

Rivière· 91 segments

Hadejia River

Crosses 21 administrative regions : Ajingi, Auyo, Dawakin Kudu, Gabasawa, Gaya +16

Endorheicrivière

Total length

340km

Max discharge

80,3m³/s

Max Strahler

5

Segments matched

91

River geography21 admin regions · 0 communes

Parent watershed

hybas-10807305501347 km²

21 administrative regions crossed (GADM L2)

  • Kabo
    Kano · Nigeria
    52.0 km
    in this dpt
  • Dawakin Kudu
    Kano · Nigeria
    48.8 km
    in this dpt
  • Ringim
    Jigawa · Nigeria
    46.8 km
    in this dpt
  • Miga
    Jigawa · Nigeria
    43.8 km
    in this dpt
  • Wudil
    Kano · Nigeria
    36.7 km
    in this dpt
  • Kaugama
    Jigawa · Nigeria
    35.1 km
    in this dpt
  • Kiru
    Kano · Nigeria
    34.5 km
    in this dpt
  • Taura
    Jigawa · Nigeria
    32.0 km
    in this dpt
  • Gabasawa
    Kano · Nigeria
    28.5 km
    in this dpt
  • Ajingi
    Kano · Nigeria
    28.0 km
    in this dpt
  • Madobi
    Kano · Nigeria
    21.5 km
    in this dpt
  • Kumbotso
    Kano · Nigeria
    17.8 km
    in this dpt
  • Karaye
    Kano · Nigeria
    13.2 km
    in this dpt
  • Auyo
    Jigawa · Nigeria
    10.0 km
    in this dpt
  • Warawa
    Kano · Nigeria
    7.3 km
    in this dpt
  • Gaya
    Kano · Nigeria
    5.2 km
    in this dpt
  • Rimin Gado
    Kano · Nigeria
    4.1 km
    in this dpt
  • Gezawa
    Kano · Nigeria
    3.4 km
    in this dpt
  • Jahun
    Jigawa · Nigeria
    3.0 km
    in this dpt
  • Tofa
    Kano · Nigeria
    0.0 km
    in this dpt
  • Kura
    Kano · Nigeria
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

1 distinct species · 1 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Not enough documented interactions to build a meaningful graph for this territory.

Hydrology (HydroRIVERS v10)

Total length

340km

Max discharge

80,3m³/s

Max Strahler

5

Segments matched

91

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