Better tools. Better news.
Sunday, November 22, 2026 · UTC
Finance

Himalaya Tsunami in Nepal Kills Over 1,000, Thousands Still Missing

A massive flood in Nepal killed over 1,000 people and left thousands missing as rescue efforts struggle.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 8 placed sources from 2 publishers.
As of 2026-09-02 03:00 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
The flood in Nepal, described as a 'Himalaya Tsunami,' has killed at least 1,000 people as of August 26, with thousands still missing. [1] In 1791, Gorkha forces invaded Tibet again but were met with a Chinese response of over 10,000 troops that overwhelmed them, forcing a retreat through the terrain now devastated by the Rasuwa disaster. [2] Aid worker Sudama Karki Cchetri stated that the flood wave descended in seven minutes, leaving no chance for survival for those caught in it. [3] Kamala Tamang, a survivor from Brabal, reported that 26 residents of her village are missing, and she believes they are dead after three days of no contact. [4] Sudama Karki Cchetri, an aid worker, reported that a 12-person family was rescued from a partially submerged house in Betrawoti by the Nepalese army. [5] Chinese state media reported 16 deaths and around 550 missing people following the glacial avalanche in Kyirong, Tibet. [6] Students for a Free Tibet - India and International Tibet Network stated that China exercises iron-fist control on media and information in Tibet to maintain stability. [7] Tibetan community members and environmental researchers expressed concern over the challenges in accessing verified updated information on the impact of a glacial avalanche that struck Kyirong, Tibet, and Rasuwa district of Nepal last month. [8]
Proof8 sources · 2 publishers
What this stands on
  1. The flood in Nepal, described as a 'Himalaya Tsunami,' has killed at least 1,000 people as of August 26, with thousands still missing. · DER STANDARD
  2. In 1791, Gorkha forces invaded Tibet again but were met with a Chinese response of over 10,000 troops that overwhelmed them, forcing a retreat through the terrain now devastated by the Rasuwa disaster. · Hindustan Times
  3. Aid worker Sudama Karki Cchetri stated that the flood wave descended in seven minutes, leaving no chance for survival for those caught in it. · DER STANDARD
  4. Kamala Tamang, a survivor from Brabal, reported that 26 residents of her village are missing, and she believes they are dead after three days of no contact. · DER STANDARD
  5. Sudama Karki Cchetri, an aid worker, reported that a 12-person family was rescued from a partially submerged house in Betrawoti by the Nepalese army. · DER STANDARD
  6. Chinese state media reported 16 deaths and around 550 missing people following the glacial avalanche in Kyirong, Tibet. · Hindustan Times
  7. Students for a Free Tibet - India and International Tibet Network stated that China exercises iron-fist control on media and information in Tibet to maintain stability. · Hindustan Times
  8. Tibetan community members and environmental researchers expressed concern over the challenges in accessing verified updated information on the impact of a glacial avalanche that struck Kyirong, Tibet, and Rasuwa district of Nepal last month. · Hindustan Times
1 of the 2 publishers publishes from India. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
1 of the 2 publishers publishes from India. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)548aa8cc9d2d301bb894743ae9c835b63e1bc6291d34f5fdf85942faa062cfb2
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.