Published: August 27, 2026
Last updated: August 27, 2026
Latest update: A preliminary technical report from Nepal's Flood Forecasting Division has reconstructed the extraordinary journey of the August 26 Bhotekoshi flood—from a river blockage on the Tibet side through Rasuwa, the Trishuli corridor and finally to Devghat. The assessment estimates that approximately 20 million cubic metres of additional floodwater passed through Devghat during the event.
A catastrophic flood that began near the Nepal–China border on August 26, 2026, did not remain confined to Rasuwa.
Within hours, the flood surge travelled through the Bhotekoshi River, entered the Trishuli River system, passed through downstream areas of Dhading and Nuwakot, moved through Muglin, and eventually reached the Narayani–Devghat area in Chitwan.
The scale and speed of the event have shocked communities across Nepal.
The latest Nepal Police figures reported by Radio Nepal put the death toll at 162, while international reporting has subsequently put the toll at at least 165 across Nepal and the affected Tibet region. Hundreds of people remain missing or unaccounted for, including foreign tourists, security personnel and hydropower workers.
But one of the most important developments on August 27 is not simply the death toll.
It is the release of a preliminary technical reconstruction of the flood's journey.
The Bhotekoshi Flood Was a River-System Disaster
The August 26 event is often described simply as the Rasuwa flood or Bhotekoshi flood.
That description is accurate, but incomplete.
The technical report from Nepal's Flood Forecasting Division shows that the event developed into a much larger river-system emergency.
The broad pathway was:
Tibet → Lhende/Bhotekoshi → Rasuwa → Trishuli → Dhading/Nuwakot → Muglin → Narayani → Devghat
The flood did not travel at one constant speed. It moved through a complex Himalayan river network, reaching different monitoring stations and settlements at different times.
The technical assessment says approximately 20 million cubic metres of additional water passed through Devghat during the flood.
That makes the event important not only for Rasuwa but for understanding flood risk across a substantial section of central Nepal.
Where Did the Bhotekoshi Flood Start?
The initial flood entered the Bhotekoshi system from the Tibet side of the Nepal–China border.
According to Nepal's preliminary technical assessment, a river blockage on the Tibet side created a lake. That lake subsequently burst, releasing a large volume of water downstream.
Earlier satellite-based analysis had indicated that debris blocked the river approximately 20 kilometres upstream of the Miteri Bridge, creating a temporary lake before the sudden release. Nepal's Department of Hydrology and Meteorology described an ice avalanche and subsequent debris-lake formation as a possible trigger.
This is important because the disaster was not simply a conventional rain-fed flood.
The emerging evidence points toward a high-altitude cascading hazard involving ice, rock, debris, river blockage and sudden water release.
The exact physical sequence remains under investigation.
What Happened Before the Flood?
One of the most intriguing details in the technical reconstruction is the timing of a 4.4-magnitude earthquake.
Nepal's Department of Mines and Geology recorded the earthquake at approximately:
8:37 a.m. on August 26
The flood entered the Bhotekoshi system shortly afterward.
However, the presence of an earthquake does not automatically mean that the earthquake caused the flood.
The relationship between the seismic signal, glacier/ice collapse and subsequent river blockage is still being investigated.
International reporting has also highlighted evidence indicating that the seismic signal was associated with a glacier-related collapse rather than a conventional earthquake-driven flood.
Therefore, readers should distinguish between:
Earthquake detected → glacier/ice/debris event → river blockage → sudden release → flood surge
and the much simpler but potentially inaccurate statement:
“An earthquake caused the flood.”
The scientific investigation is still developing.
Bhotekoshi Flood Timeline: From Tibet to Devghat
The newly released technical report provides one of the most useful pieces of information for understanding the disaster: a timeline of how the flood moved downstream.
8:37 a.m. — Earthquake recorded
A 4.4-magnitude earthquake was recorded by Nepal's Department of Mines and Geology.
This occurred shortly before the major flood information reached authorities.
8:40 a.m. — Last Bhotekoshi-Syafrubesi water-level reading
The last recorded water level at the Bhotekoshi-Syafrubesi monitoring station was approximately:
1.62 metres
For comparison:
- Warning level: 6 metres
- Danger level: 7 metres
This is one of the extraordinary aspects of the event.
The monitoring station did not record a gradual rise toward the danger threshold before communications were lost.
8:50 a.m. — Monitoring data stopped
Data transmission from the Bhotekoshi-Syafrubesi station stopped.
The station was subsequently among the hydrological monitoring facilities damaged or swept away by the flood.
This meant authorities lost direct measurements from one of the most important locations in the disaster zone.
Around 9:00 a.m. — Major flood information received
Authorities received information that a massive flood was entering the Bhotekoshi from the Tibet side.
This was the critical moment for downstream warning.
The Flood Forecasting Division began issuing alerts to vulnerable communities.
679,295 Emergency SMS Messages Were Sent
One of the most important but less-publicized aspects of the disaster response was Nepal's early-warning communication.
According to the technical report, authorities coordinated with Nepal Telecom and Ncell to send:
679,295 early-warning SMS messages
These included:
- 435,635 messages through Nepal Telecom
- 243,660 messages through Ncell
The alerts targeted vulnerable communities in:
- Rasuwa
- Nuwakot
- Dhading
- Chitwan
The Flood Forecasting Division said the timely warnings helped many people save their lives.
This may become an important case study in disaster risk reduction in Nepal.
The flood was extraordinarily destructive, but early warnings may have prevented an even higher death toll.
9:15–9:16 a.m. — Trishuli Corridor Alerts
Authorities began sending early-warning messages to communities along the Trishuli corridor toward Muglin.
This demonstrates that officials understood the flood was no longer only a Rasuwa emergency.
The danger was moving downstream.
9:20 a.m. — Betrawati Monitoring Station Lost
The Betrawati hydrological station stopped transmitting data.
Its last recorded water level was:
3.55 metres
The warning level was 4.1 metres, while the danger level was 5 metres.
Again, the monitoring system was disrupted as the flood moved downstream.
10:28 a.m. — Flood Reached Galchhi
The flood was reported in the Galchhi area of Dhading.
Authorities issued additional warnings for communities around:
- the Prithvi Highway;
- the Muglin–Narayangadh road;
- the Trishuli River corridor.
This was a major escalation because the flood was now affecting transportation routes connecting central Nepal.
11:26 a.m. — Fhurke Khola Crossed Warning Level
At the Fhurke Khola monitoring station in the Malekhu area, water levels crossed the warning threshold.
The river system was continuing to respond to the enormous flood surge.
11:43 a.m. — Danger Level Crossed at Malekhu
At approximately 11:43 a.m., water levels at the Fhurke/Malekhu station crossed the danger level.
The station and its bridge were subsequently swept away.
This illustrates the extraordinary force of the flood.
Monitoring infrastructure designed to measure river conditions was itself destroyed by the event.
11:50 a.m. — Flood Reached Malekhu Bazaar
The flood reached the Malekhu Bazaar area.
By this point, the flood had travelled a considerable distance downstream from its origin.
The event was no longer a localized Himalayan disaster.
It had become a major central Nepal river emergency.
1:00 p.m. — Flood Passed Muglin
At approximately 1:00 p.m., the flood passed Muglin.
Muglin is strategically important because it sits at a major road junction connecting several parts of Nepal.
Flooding in this region therefore has implications beyond immediate riverbank settlements.
It can affect:
- highways;
- tourism;
- freight transportation;
- emergency access;
- supply chains;
- Kathmandu–Pokhara connectivity.
1:35 p.m. — Authorities Warned of Continuing Risk
At around 1:35 p.m., authorities again warned that the lake created by the river blockage on the China side had not completely drained.
That meant the initial flood could not necessarily be treated as the end of the danger.
Officials warned of the possibility of additional increased flows in the Bhotekoshi–Trishuli system.
This remains one of the most important reasons residents downstream should continue monitoring official warnings.
2:14 p.m. — Kalikhola Reached Danger Level
At the Kalikhola monitoring station in Dhading, the water level crossed the danger threshold of:
12.1 metres
It eventually reached:
12.3 metres
This became one of the critical downstream measurements of the event.
3:20 p.m. — Flood Reached Devghat
Approximately six and a half hours after the earthquake was recorded, the flood reached the:
Narayani–Devghat area
This is one of the most significant points in the entire flood story.
The flood that began in the high Himalayas near the Tibet border had now travelled through the Bhotekoshi and Trishuli systems and reached the Narayani basin at Devghat.
4:00 p.m. — Devghat Water Level Peaked
At approximately 4:00 p.m., the Devghat hydrological station recorded a peak water level of:
6.57 metres
The level subsequently began falling.
By approximately 6:30 p.m., the water level had returned to around 4 metres, considered normal at the station.
How Much Water Reached Devghat?
This is perhaps the most striking statistic from the preliminary technical assessment.
Approximately 20 million cubic metres of additional floodwater
passed through the Devghat area during the event.
That is approximately:
20 billion litres of additional water
because one cubic metre equals 1,000 litres.
But even that number does not fully capture the destructive nature of the event.
The flood also carried:
- rock;
- mud;
- soil;
- ice;
- trees;
- construction debris;
- vehicles;
- infrastructure material.
That made the surge substantially more destructive than a simple increase in clean river water.
The Flood Destroyed Four Hydrological Monitoring Stations
The technical report says four hydrological monitoring stations were swept away:
- Rasuwa Bhotekoshi
- Rasuwa Syafrubesi
- Nuwakot Betrawati
- Dhading Malekhu/Fhurke
The stations were damaged or destroyed along with bridges and other infrastructure, making direct measurement impossible at those locations.
This creates a major challenge for reconstructing the flood.
Scientists and authorities have to combine:
- remaining station data;
- satellite imagery;
- eyewitness reports;
- downstream measurements;
- topographic information;
- hydrological modelling;
- infrastructure damage;
- field observations.
The Complete Bhotekoshi-to-Devghat Flood Route
The best way to understand the disaster is to follow the water.
1. Tibet
A blockage formed in the river system.
↓
2. Lhende river system
The blockage and subsequent release produced the initial surge.
↓
3. Bhotekoshi River
The surge entered Nepal's Rasuwa district.
↓
4. Timure and Rasuwagadhi area
The border corridor suffered catastrophic destruction.
↓
5. Syafrubesi and downstream Rasuwa
Communities and infrastructure along the river were affected.
↓
6. Trishuli corridor
The flood continued downstream.
↓
7. Betrawati / Nuwakot
The flood affected monitoring infrastructure and communities.
↓
8. Galchhi / Dhading
The flood reached Galchhi at approximately 10:28 a.m.
↓
9. Malekhu
The flood reached Malekhu Bazaar around 11:50 a.m.
↓
10. Muglin
The flood passed Muglin around 1:00 p.m.
↓
11. Narayani River
The flood continued into the larger river system.
↓
12. Devghat
The flood reached Devghat around 3:20 p.m.
This is why calling the event simply the “Rasuwa flood” understates its geographic scale.
Why Did the Flood Travel So Far?
Nepal's Himalayan river systems have a distinctive physical characteristic:
Steep elevation gradients.
Water released at high elevation can travel rapidly downstream.
The Bhotekoshi and Trishuli systems also form connected river corridors.
Once a major surge entered the system, gravity and the existing river channels helped carry it downstream.
The flood therefore propagated through multiple districts rather than remaining around its point of origin.
Why Was Rasuwa Hit So Hard?
Rasuwa sits in a steep Himalayan landscape close to the Nepal–China border.
Several risk factors overlap:
- steep terrain;
- narrow river valleys;
- settlements close to rivers;
- roads following river corridors;
- bridges crossing major waterways;
- hydropower infrastructure;
- international border infrastructure;
- tourism and pilgrimage routes.
This means that a sudden upstream flood can affect multiple critical systems simultaneously.
The August 2026 event damaged or destroyed roads, bridges, settlements, hydropower infrastructure and border facilities. Recent reporting has documented 19 motorable bridges and about 40 kilometres of road damage in the disaster area.
Why Were Foreign Tourists Among the Missing?
The Rasuwa corridor is an important route for travellers heading toward the Tibet border and Mount Kailash–Lake Mansarovar pilgrimage region.
Consequently, a large number of foreign nationals were travelling through or staying in the affected region when the disaster occurred.
International reporting now says more than 800 foreigners are among those missing across Nepal and Tibet, including nationals from countries such as India, the United States, Australia, Britain and Canada.
This makes the flood an international disaster rather than solely a domestic Nepalese emergency.
Related:
Nepal Flood Missing Tourists: 403 Unaccounted for From 15+ Countries — Full Nationality List and Latest Updates
That article should be updated as official nationality figures change.
Nepal Flood Death Toll: Latest Situation
The casualty figures have changed rapidly because rescue teams continue to reach previously isolated areas and recover bodies.
As of August 27:
- Nepal Police reported 162 confirmed deaths in its morning update.
- International reporting later placed the broader death toll at at least 165, including deaths in Nepal and Tibet.
- Hundreds remain missing or unaccounted for.
These numbers should be treated as time-sensitive.
For a disaster still undergoing rescue and recovery, a difference between two reports does not necessarily indicate that one source is false. Figures can differ because of:
- reporting time;
- geographical coverage;
- recovered versus identified bodies;
- Nepal-only versus Nepal-plus-Tibet totals;
- duplicate or newly reconciled missing-person records.
For that reason, this article will prioritize the latest official Nepal Police/NDRRMA information while clearly displaying the update time.
The Flood Also Threatened Nepal's Hydropower Infrastructure
The Bhotekoshi corridor contains significant hydropower infrastructure.
The disaster damaged hydropower facilities and left workers unaccounted for.
Recent reporting has indicated that 12 hydropower plants were shut down, with approximately 196 workers missing in connection with affected projects.
This creates consequences beyond the immediate humanitarian emergency.
The disaster can affect:
- electricity generation;
- construction projects;
- investment;
- local employment;
- roads and transmission infrastructure;
- regional economic activity.
The final economic cost is still being assessed.
Was This a Normal Monsoon Flood?
No—not in the conventional sense.
The August 26 event occurred during Nepal's monsoon season, but the emerging technical evidence points toward a sudden upstream blockage and release associated with an ice/debris event rather than a simple rainfall-driven rise in the river.
The Department of Hydrology and Meteorology had earlier indicated that there was not exceptionally heavy rainfall in the immediate Rasuwa area immediately before the disaster.
This is one reason the event generated such a rapid and difficult-to-predict surge.
Was It a Glacial Lake Outburst Flood?
This question requires caution.
A glacial lake outburst flood, or GLOF, occurs when water stored in a glacial lake is suddenly released.
The current evidence suggests that an ice avalanche and debris blockage may have created a temporary lake that subsequently burst.
However, it is still preferable to describe the exact mechanism as under investigation rather than definitively labeling the disaster a classic GLOF.
The distinction is scientifically important.
A possible sequence is:
ice/glacier collapse → debris enters river → river blockage → temporary lake → sudden breach → flood/debris surge
Further satellite and field analysis should clarify the process.
Is Another Bhotekoshi Flood Possible?
Authorities have warned that the danger may not be completely over.
The preliminary technical report says the lake created by the blockage on the China side had not fully drained, and authorities warned that additional increased flows could occur in the Bhotekoshi–Trishuli system.
This does not mean another catastrophic flood is certain.
It means that people downstream should continue to take official warnings seriously.
Communities near:
- Bhotekoshi;
- Trishuli;
- Kalikhola;
- Malekhu;
- Muglin;
- Narayani;
should monitor official flood forecasts and evacuation instructions.
What the 2026 Bhotekoshi Flood Teaches Nepal
The disaster highlights a major challenge for Himalayan countries:
A hazard can begin far upstream and become a national emergency hundreds of kilometres away.
An event near a remote glacier or mountain river can affect:
villages → highways → hydropower → border crossings → tourism → major rivers → downstream cities
within a matter of hours.
This makes early-warning systems essential.
The fact that authorities were able to send nearly 680,000 warning SMS messages is particularly significant.
Future systems could potentially become even more sophisticated by combining:
- satellite monitoring;
- seismic data;
- glacier surveillance;
- river sensors;
- automatic cameras;
- artificial intelligence;
- hydrological modelling;
- mobile alerts;
- cross-border information sharing.
Why the Tibet–Nepal Border Matters
The flood demonstrates how natural disasters do not respect international borders.
The physical trigger occurred on or near the Tibet side, while some of the most devastating consequences occurred in Nepal.
The flood also affected China's Gyirong area, where authorities have reported deaths and missing people and continued concern about landslide and water hazards.
This means effective disaster preparedness in the Himalayan region requires:
Nepal–China information sharing + satellite monitoring + hydrological data + early warning + coordinated rescue
rather than isolated national systems.
Nepal Flood Map: The Journey in One View
For readers trying to understand where the flood travelled, the most useful geographic sequence is:
Tibet
Initial blockage/lake formation
↓
Lhende River system
Sudden release
↓
Bhotekoshi River
Rasuwa
↓
Rasuwagadhi / Timure
Nepal–China border region
↓
Syafrubesi
Major affected area
↓
Trishuli River
Downstream flood corridor
↓
Betrawati / Nuwakot
↓
Galchhi / Dhading
↓
Malekhu
↓
Muglin
↓
Narayani River
↓
Devghat
This route is particularly useful for understanding why communities far from Rasuwa were warned about the approaching flood.
The 20 Million Cubic Metre Question
Perhaps the simplest way to understand the scale is this:
Approximately 20 billion litres of additional water passed through Devghat.
That is not necessarily the total volume released at the source. It is the preliminary estimate of additional floodwater passing through the Devghat area, according to the technical assessment.
That distinction matters.
The figure should therefore not be presented as:
“The flood contained exactly 20 billion litres.”
Instead:
“A preliminary technical assessment estimates that around 20 million cubic metres—about 20 billion litres—of additional floodwater passed through Devghat during the event.”
That is the scientifically responsible wording.
What Remains Unknown?
Despite the growing amount of information, major questions remain.
1. What exactly caused the initial blockage?
Was it primarily:
- glacier collapse?
- ice avalanche?
- rock avalanche?
- landslide?
- a combination?
2. How large was the temporary lake?
Satellite and field analysis is required.
3. How quickly did the blockage fail?
The precise timing remains under reconstruction.
4. How much water was released at the source?
The 20-million-cubic-metre estimate applies to additional water passing through Devghat, not necessarily the exact source volume.
5. What is the final death toll?
Search-and-rescue operations are still underway.
6. How many people remain missing?
Lists are being reconciled.
7. Could another surge occur?
Authorities continue to monitor the upstream blockage and river system.
Frequently Asked Questions
How far did the Bhotekoshi flood travel?
The flood travelled from the Tibet-side river system through Rasuwa's Bhotekoshi corridor, into the Trishuli system, through areas including Dhading and Nuwakot and onward toward Muglin and the Narayani–Devghat area.
Did the Bhotekoshi flood reach Devghat?
Yes. The technical report says the flood reached the Narayani–Devghat area at approximately 3:20 p.m. on August 26, with the Devghat water level peaking at 6.57 metres around 4:00 p.m.
How much water passed through Devghat?
A preliminary assessment estimates approximately 20 million cubic metres, equivalent to around 20 billion litres, of additional floodwater passed through Devghat during the event.
What river did the flood enter after Bhotekoshi?
The flood propagated into the Trishuli River system and eventually reached the Narayani–Devghat area.
When did the flood reach Muglin?
The technical report says the flood passed Muglin at approximately 1:00 p.m.
When did the flood reach Devghat?
It reached the Narayani–Devghat area at approximately 3:20 p.m.
What caused the Bhotekoshi flood?
Preliminary evidence points to a river blockage on the Tibet side, reportedly associated with an ice/debris event, followed by the sudden release of water. The exact mechanism remains under investigation.
Was the flood caused by an earthquake?
A 4.4-magnitude earthquake was recorded at 8:37 a.m., shortly before the flood information was received. However, the relationship between the seismic event and the glacier/ice collapse is still being investigated.
Are people still at risk?
Yes. Authorities have warned that the upstream lake formed by the blockage had not fully drained and urged continued vigilance along the Bhotekoshi–Trishuli–Narayani system.
Final Takeaway
The August 26, 2026 Bhotekoshi flood was far larger geographically than a single Rasuwa disaster.
It was a rapidly propagating Himalayan river-system event that began near the Tibet border, devastated the Bhotekoshi corridor, moved into the Trishuli system, passed through Dhading and Nuwakot, reached Muglin and eventually arrived at Devghat.
The preliminary technical assessment provides a remarkable measurement of its scale:
Around 20 million cubic metres of additional floodwater passed through Devghat.
The flood also destroyed four hydrological monitoring stations, damaged bridges and roads, affected hydropower infrastructure, displaced communities and contributed to a death toll that has already exceeded 160, with hundreds still missing.
Most importantly, the disaster demonstrates how a high-altitude event can rapidly become a multi-district emergency hundreds of kilometres downstream.
For Nepal, the event is likely to become an important case study in glacial hazards, flash-flood forecasting, early-warning systems, transboundary disaster management and Himalayan climate risk.