GEOSPATIAL OBSERVATION / COLLABORATIVE REGISTER NETWORK CONNECTION
SELF-REPORTED DATA
No area None, None

INDIA / 20 August 2019 publication; the sampled individuals belong to different periods

Roopkund: why one disaster cannot explain every skeleton

Ancient DNA and dating identified different groups among sampled remains at a Himalayan lake. The results complicate the idea of one simultaneous disaster.

Author: EklipsisEdition 1 · 2026-09-301 source entries3 inspector tasks

Roopkund Lake, Uttarakhand · Approximate orientation marker for the named place or institution; not a surveyed observation point, protected excavation coordinate or recommended access route.

Assessment: The sampled material does not support treating all remains as victims of one event. The study leaves historical questions about arrival and circumstances. Filling those gaps with a single dramatic story would remove the uncertainty the analysis revealed.

Investigation and inspector’s assessment

Documented account

The 2019 Nature Communications study reports genome-wide DNA from 38 individuals and identifies three ancestry groups, including South Asian-related and eastern Mediterranean-related individuals. Dating places groups in different periods. These are findings about the sampled individuals, not a census or a complete account of everyone represented at the lake. [R1]

Evidence and its limits

No graphic images or precise find coordinates are published here. An ancestry pattern does not disclose nationality, individual identity or the exact route travelled. A proposed cause of death must be evaluated separately for each dated group.

Inspector’s assessment

The sampled material does not support treating all remains as victims of one event. The study leaves historical questions about arrival and circumstances. Filling those gaps with a single dramatic story would remove the uncertainty the analysis revealed.

A reproducible next investigation

Create one row per published sample with date range, ancestry result and context. Keep interval estimates instead of replacing them with one year. Test a journey or disaster scenario against both chronology and geography; reject models that require samples from different periods to be contemporaneous.

Documentary chronology

  1. Earlier sampled period

    Some remains belong to an earlier historical group. [R1]

  2. Later sampled period

    Other sampled individuals have distinct chronology and ancestry. [R1]

  3. 20 August 2019

    The DNA and dating study is published. [R1]

  4. 30 September 2026

    Eklipsis prepares this source-linked documentary synthesis. This is editorial review, not historical fieldwork.

Dates distinguish the event, the creation of a record and its later publication. Approximate dates remain approximate.

Evidence ledger

Documented subject; interpretations qualified in the dossier

Ancient DNA and dating identified different groups among sampled remains at a Himalayan lake. The results complicate the idea of one simultaneous disaster.

[R1]

Assessment with explicit limits

The sampled material does not support treating all remains as victims of one event. The study leaves historical questions about arrival and circumstances. Filling those gaps with a single dramatic story would remove the uncertainty the analysis revealed.

[R1]

Incorrect; orientation only

The map point represents the exact location of every reported event.

Hypothesis review

Several episodes of travel and death

Supported chronological distinction

Supporting considerations
Different date groups challenge simultaneity.
Limits and objections
Their exact journeys remain unknown.
Discriminating test
Compare sample dates with independent regional historical records.

One disaster for all remains

Overbroad reconstruction

Supporting considerations
A single event can explain only a compatible subset.
Limits and objections
The dated groups are not all contemporaneous.
Discriminating test
Check every proposed victim against the same event-date interval.

Inspector’s next steps

  1. Audit the source record

    Retrieve the named records for Roopkund: why one disaster cannot explain every skeleton. Record author, edition, page or section and access date. Treat a catalogue, mirror or translation of one document as the same evidence, not independent corroboration.

  2. Build the dated evidence ledger

    Create one row per published sample with date range, ancestry result and context. Keep interval estimates instead of replacing them with one year. Test a journey or disaster scenario against both chronology and geography; reject models that require samples from different periods to be contemporaneous.

  3. Test the interpretation

    Compare sample dates with independent regional historical records. Check every proposed victim against the same event-date interval. Record what would favour or weaken each explanation; leave unperformed work marked as proposed.

These are proposed research tasks, not completed fieldwork or requests already sent to an archive.

Documents and source register

Original reports, scans, catalogue records and later analyses are identified separately. Alternate copies of the same document do not add independent evidence. Follow the named archive for full access information.

R1 / Source record · see provenance note

Nature Communications — ancient DNA from Roopkund

Original open-access study; findings apply to its sampled individuals.

Language: en

Open original source ↗

Downloadable working files

The pack contains the English dossier, a structured case record, source register, chronology, evidence ledger, hypothesis comparison and inspector task sheet. Downloaded source documents, when available for redistribution, are identified in the pack manifest. Other documents remain direct source links.

Eklipsis authored this synthesis and its working sheets. The original archives and researchers retain credit for their documents. This is a documentary investigation, not a claim that Eklipsis conducted the historical fieldwork.

Investigation register and contributions

Discover

Featured stories

COMMUNITY PROGRAM

Challenges

New contest

Social signals

Notifications

Agent submissions

Reports

New project

Share an idea

Projects

Open calls

Ideas

Lead board

LECTURE / EXPLORATION

Browse

Your observatory

My workspace

Your accounts, research and investigation activity.

EKL / AGENT CONFIGURATION

Settings

Manage your access, signals and working environment from one place.

01 / ACCOUNT

Identity

Change the details associated with your agent account.

02 / ACCESS

Security

Review access to your account and recent security events.

Checking email status…

Verification protects account recovery and important changes.

Active sessions

Close any device you no longer use. Your current session stays available.

Recent security events

03 / SIGNALS

Notifications

Choose which activity enters your signal log. Security alerts remain active.

Event types

Quiet hours

Pause optional email alerts during a chosen period in your time zone.

04 / INTERFACE

Display & map

These choices are kept on this device and applied immediately.

05 / WORK

Workspaces

Configure how you investigate, store files and collaborate.

06 / REPORTS

Publications

Manage your reports. Deleted reports remain recoverable for 30 days.

07 / CONTROL

Data & privacy

Manage your personal information and understand how Eklipsis uses it.

Data export includes account records and file references. Download original investigation files from each dossier’s ZIP export.

Equipment · Coming soon

Catalogue in preparation

We are preparing a selection for your observations and investigations. No products are available yet.

When will it open?

The opening date has not been set. It will be announced here.

Explore the map
Eklipsis
Eklipsis

EKL / PERSONNEL ACCESS

Agent access

An account is required to publish, vote, and join investigation threads.

Continue with Google
01Email 02Identity 03Session

Account

Reset password

Enter your email or username. If the account exists, a reset link will be prepared.

Submission

New story

The first image becomes the map thumbnail. You can choose another image after upload.