Significance
175 measured / 175 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 175 events
Connected Situation / Through 2026-10-26
Nepal–Tibet Flood Emergency, Rescue and Recovery
- stories
- 375
- events
- 175
- entities
- 743
- connections
- 375
Evidence so far on 2026-10-26 UTC · updated 2026-10-26 08:22 UTC · analysis as of 2026-10-25 17:30 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
A report dated 2026-08-30 said China sent rescue experts and aid to Nepal; a separate 2026-08-31 event record dates the tunnel-expert deployment, linked to “537 workers missing in Nepal floods at Rasuwa and Nuwakot hydropower projects.” On 2026-09-02, Nepal formally sought climate compensation from major emitters; “Nepal Himalayan flood death toll rises; 4,462 still missing” gave a separate missing-person estimate. The Chinese People’s Liberation Army deployment to Gyirong county after the Xizang mudslide is dated 2026-09-04, while “Mudslide strands Nepalese border residents in China's Tibet; aid delivered” describes the border-area impacts. On 2026-09-15, the Nepal Army dug through the flooded Chilime tunnel to rescue workers and Nepal Police launched a Bhotekoshi rehabilitation campaign; “Bhotekoshi floods leave Nepal’s private sector bearing most losses” describes the wider local impact. On 2026-09-19, the Nepal Electricity Authority described flood damage to hydropower projects while maintaining electricity exports. Recovery milestones included the start of Betrawati Bailey bridge installation, reported in “Bailey bridge installation begins in Betrawati, Nepal” on 2026-10-02, and the bridge’s opening, reported in “Bailey bridge opens in Nepal to replace flood-damaged Betrawati bridge” on 2026-10-11.
Footnotes[19][12][16][10][20][6][21][24][4][17][3][2]Assessment
The core is a severe Nepal flood emergency that extended from rescue and searches into damage response and specific recovery works: the tunnel operations and hydropower effects are distinct parts of that account. The Jilong/Tibet mudslide had its own affected residents and response, while a Gyirong glacial-lake burst sent renewed flooding toward Nepal; the cross-border hazard is connected, but its toll should not be combined with Nepal’s. “Nepal Himalayan flood death toll rises; 4,462 still missing” and “More than 5,000 missing after Nepal flood disaster” give different dated estimates, not a reconciled total. Likewise, “537 workers missing in Nepal floods at Rasuwa and Nuwakot hydropower projects” and “Nepal flash floods trap 46 hydropower tunnel workers at Rasuwagadhi plant” do not establish that the figures describe the same group. Nepal’s compensation request and the foreign minister’s reported rejection of a climate-compensation demand are distinct positions; the reports do not settle their relationship. The Betrawati reports establish bridge installation and opening milestones, not completion of wider recovery.
Footnotes[19][21][17][6][13][10][7][12][9][16][11][8]Explanation originally captured 2026-10-25 · Evidence through 2026-10-26 UTC · Source edition sed_d0cac3b39893ca205f63f30633d0fe99
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 54-day Situation represented by 175 coded Events carried across 375 member Stories.
- Coded activity
The coded activity is led by EN02 · Meteorological Hazard (64) and EN01 · Geophysical Hazard (20).
- Prominent subjects
United Nations, China, and Nepal Police are prominent in the retained actor and relationship evidence.
- Entity coverage
743 canonical Entities are linked to this edition.
Metric coverage. 175 coded Events · 174 CAMEO+ · 1 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3.1
min 1max 7
Systemic importance0.17
min 0.05max 0.63
Propagation potential0.37
min 0max 0.78
Market sensitivity0.09
min 0.05max 0.5
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 8 scores, distributions & definitions
How the coder scored the full retained Event set
175 coded events — 174 CAMEO+ (46 political) · 1 conflict
- Significance · 1750.33min 0.11max 0.57
- Magnitude · 1743.1min 1max 7
- Systemic · 1740.17min 0.05max 0.63
- Propagation · 1740.37min 0max 0.78
- Market · 1740.09min 0.05max 0.5
- Goldstein · 472.7min -6.5max 7.4
- Fatalities · 10min 0max 0
- Confidence · 1750.72min 0.32max 0.99
Quad class over those 47 events · Verbal Cooperation 20 · Material Cooperation 16 · Verbal Conflict 10 · Material Conflict 1. 128 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 174 CAMEO+ events only; the 1 conflict events have no such column.
Magnitude
174 measured / 174 eligible · 0 missing · 1 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 174 of 175 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
174 measured / 174 eligible · 0 missing · 1 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 174 of 175 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
174 measured / 174 eligible · 0 missing · 1 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 174 of 175 events coded in the CAMEO+ family; the conflict family has no such column
Market
174 measured / 174 eligible · 0 missing · 1 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 174 of 175 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
47 measured / 47 eligible · 0 missing · 128 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 47 of 175 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
1 measured / 1 eligible · 0 missing · 174 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 1 of 175 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
175 measured / 175 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 175 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day50 reporting days · click a day to open or close it
2026-10-18from the recordslatest
Nepal's Tatopani border crossing to open for three days
1 Story and 0 coded Events (-2 / 0 against the day before). Widest coverage: Nepal's Tatopani border crossing to open for three days (4 articles).
- 1-2
- Stories · vs day before
- 00
- Events · vs day before
- 4
- articles
The lay of the land
Situation timeline
Threads
All 50 daysarticlesstoriesevents
08-2609-0509-1509-2410-0610-18
Loading Situation timeline…
What kind of event · 42 coded types
over 175 coded events on this edition
- Environment92
- EN02 · Meteorological Hazard64
- EN01 · Geophysical Hazard20
- EN05 · Environmental Policy or Agreement5
- EN03 · Climate Event2
- EN04 · Environmental Pollution Event1
- Political46
- 073 · Provide Humanitarian Aid13
- 01 · Make Public Statement3
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
- development
AnalystSearch and rescue at hydropower tunnels
Reports describe trapped or missing hydropower workers, tunnel searches and rescue activity; the reported worker figures are not reconciled.
- development
- development
AnalystClimate-compensation claims and positions
Nepal’s compensation requests and the foreign minister’s reported position are distinct claims; their relationship is unresolved.
Key actors
- UN
RuleUnited Nations
Recorded as actor in 1 coded Event, including United Nations requests aid for flood-hit Nepal.
Recorded as actor in 1 coded Event, including United Nations requests aid for flood-hit Nepal.
Footnotes[?] - 🇨🇳
- NP
RuleNepal Police
Recorded as actor in 3 coded Events, including Nepal Police launch rehabilitation campaign in Bhotekoshi flood zone.
Recorded as actor in 3 coded Events, including Nepal Police launch rehabilitation campaign in Bhotekoshi flood zone.
Footnotes[?][24][?] - SK
RuleShisir Khanal
Recorded as actor in 1 coded Event, including Nepal foreign minister praises China’s disaster assistance.
Recorded as actor in 1 coded Event, including Nepal foreign minister praises China’s disaster assistance.
Footnotes[?] - 🇺🇸
RuleUnited States
Recorded as actor and target in 4 coded Events, including Nepal formally seeks climate compensation from major emitters.
Recorded as actor and target in 4 coded Events, including Nepal formally seeks climate compensation from major emitters.
Footnotes[16][?][?][?]
Key Events
contextAnalystChina sends tunnel experts to Nepal rescue operation
China sent tunnel experts to Nepal’s rescue operation on 2026-08-31.
China sent tunnel experts to Nepal’s rescue operation on 2026-08-31.
Footnotes[19]
contextAnalystChina provides Nepal disaster information and rescue support
China provided Nepal with disaster information and rescue support; the event is dated 2026-08-31.
China provided Nepal with disaster information and rescue support; the event is dated 2026-08-31.
Footnotes[23]contextAnalystNepal formally seeks climate compensation from major emitters
Nepal formally sought climate compensation from major emitters on 2026-09-02.
Nepal formally sought climate compensation from major emitters on 2026-09-02.
Footnotes[16]
contextAnalystChinese military deploys hundreds after Xizang mudslide
The Chinese People’s Liberation Army deployment to Gyirong county after the Xizang mudslide is dated 2026-09-04.
The Chinese People’s Liberation Army deployment to Gyirong county after the Xizang mudslide is dated 2026-09-04.
Footnotes[20]
contextAnalystNepali Army clears tunnel debris after Nepal flash floods
The Nepali Army cleared tunnel debris after the floods on 2026-09-13.
The Nepali Army cleared tunnel debris after the floods on 2026-09-13.
Footnotes[18]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The tunnel-experts Event is linked to “537 workers missing in Nepal floods at Rasuwa and Nuwakot hydropower projects.” · reporting linkAnalystChina sends tunnel experts to Nepal rescue operation → 537 workers missing in Nepal floods at Rasuwa and Nuwakot hydropower projects
The linked headline reports missing workers; it does not establish that the experts addressed every worker named.
The Rasuwagadhi workers Event is linked to “Nepal flash floods trap 46 hydropower tunnel workers at Rasuwagadhi plant.” · reporting linkAnalystNepal Electricity Authority says 46 hydropower workers may survive → Nepal flash floods trap 46 hydropower tunnel workers at Rasuwagadhi plant
The linked headline concerns Rasuwagadhi workers; it does not reconcile their figure with the separate 537-worker report.
The climate-compensation Event is linked to “Nepal Himalayan flood death toll rises; 4,462 still missing.” · reporting linkAnalystNepal formally seeks climate compensation from major emitters → Nepal Himalayan flood death toll rises; 4,462 still missing
The linked Story also reports a missing-person estimate; it does not reconcile that estimate with other reports.
The Chinese military deployment Event is linked to “Mudslide strands Nepalese border residents in China's Tibet; aid d.” · reporting linkAnalystChinese military deploys hundreds after Xizang mudslide → Mudslide strands Nepalese border residents in China's Tibet; aid delivered
The linked Story concerns Tibet border-region effects and aid; it does not make that disaster part of Nepal’s flood toll.
The tunnel-debris Event is linked to “Nepal tunnel survivor recounts ordeal and second chance at life.” · reporting linkAnalystNepali Army clears tunnel debris after Nepal flash floods → Nepal tunnel survivor recounts ordeal and second chance at life
The Story recounts a survivor’s experience; it does not establish that the survivor was among the workers in every other tunnel account.
How a Situation is put together375 Stories · 175 Events · 375 membership connections · 3,376 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 743 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.