SituationKazakhstan +1

Shraddha Dubey Investigation and Linked Reports

Edition 19 Nov 2026 · Day 24Updated Nov 20, 13:33 UTC9 connections
Stories
9
Events
2
Entities
58
Countries
2
BLUFEditionUpdated Nov 20, 13:33 UTCDay 24
Frozen through 2026-11-19 UTC · published 2026-11-20 13:34 UTC · analysis as of 2026-11-19 10:31 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On 17 October, “Saharanpur link emerges in Shiva murder case involving fugitive model Shraddha Dubey” reported a Saharanpur connection in the Shiva murder case and named Shraddha Dubey. On 18 October, “Lucknow police check India-Nepal border CCTV over Shraddha Dubey’s suspected crossing” said police checked CCTV over a suspected crossing, not a confirmed one. On 20 October, “Shraddha Dubey found in Nagpur after changing locations from an Agra hotel” reported that she was found in Nagpur. A separate 20 October headline, “Crime Branch takes over probe involving Saurabh Das and Ashutosh Ranka,” reported a probe takeover involving those two men. On 22 October, “Shraddha Dubey evades police for 10 days after traveling over 3,000 km in a burqa” presented an account of her evasion. Separately, on 20 October, local residents and relatives of a deceased person blocked a road in Nuwakot and demanded compensation after a fatal crash; on 5 October, President Kassym-Jomart Tokayev appointed Omarbekov to lead Kazakhstan’s military General Staff.

Footnotes[6][5][4][3][2][8][9]
Assessment

The four Dubey headlines give the clearest connected investigative thread: they name her and the Shiva murder case, describe a suspected crossing, report her discovery in Nagpur, and present an evasion account. The headlines do not confirm that she crossed the border, and the evasion details remain an account presented by the 22 October headline. The Crime Branch headline names Saurabh Das and Ashutosh Ranka, but does not establish that its probe concerns Dubey’s case. The Nuwakot protest Event is linked to that Story, although their descriptions concern different matters; likewise, the Tokayev appointment Event is linked to a funeral-shooting headline that does not describe an appointment. The 28 October home-sealing headline does not name the triple-murder suspect, so it does not establish that the suspect was Dubey.

Footnotes[6][5][4][2][3][8][9][7][1]

Explanation originally captured 2026-11-19 · Evidence through 2026-11-19 UTC · Source edition sed_89dae02c22418c8f932d96c4d2379ae6

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

This retained edition
  • Scope

    A 24-day Situation represented by 2 coded Events carried across 9 member Stories.

  • Coded activity

    The coded activity is led by 01 · Make Public Statement (1) and PEACEFUL PROTEST (1).

  • Prominent subjects

    🇰🇿Kazakhstan and 🇳🇵Nepal are prominent in the retained actor and relationship evidence.

  • Entity coverage

    58 canonical Entities are linked to this edition.

Metric coverage. 2 coded Events · 1 CAMEO+ · 1 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3
min 3max 3
1 measured
Systemic importance0.1
min 0.1max 0.1
1 measured
Propagation potential0.26
min 0.26max 0.26
1 measured
Market sensitivity0.05
min 0.05max 0.05
1 measured

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

2 coded events — 1 CAMEO+ (1 political) · 1 conflict

  • Significance · 20.21
    min 0.17max 0.25
  • Magnitude · 13
    min 3max 3
  • Systemic · 10.1
    min 0.1max 0.1
  • Propagation · 10.26
    min 0.26max 0.26
  • Market · 10.05
    min 0.05max 0.05
  • Goldstein · 2-3.3
    min -6.5max 0
  • Fatalities · 10
    min 0max 0
  • Confidence · 20.77
    min 0.72max 0.82

Quad class over those 2 events · Verbal Conflict 1 · Verbal Cooperation 1. The four CAMEO+ scores are over the 1 CAMEO+ events only; the 1 conflict events have no such column.

Significance

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events

Magnitude

1 measured / 1 eligible · 0 missing · 1 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

1 measured / 1 eligible · 0 missing · 1 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

1 measured / 1 eligible · 0 missing · 1 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Market

1 measured / 1 eligible · 0 missing · 1 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 1 of 2 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

2 measured / 2 eligible · 0 missing · 0 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 2 of 2 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 · 1 not applicable

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 1 of 2 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

Confidence

2 measured / 2 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 2 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day7 reporting days · click a day to open or close it

2026-10-28analystlatest

Home-sealing and demolition reported in a triple-murder case

The headline reports authorities sealing a triple-murder suspect’s home and demolishing an illegal encroachment; it does not identify the suspect as Dubey.

10
Stories · vs day before
00
Events · vs day before
1
articles
The lay of the land

Situation timeline

Threads
All 7 daysarticlesstoriesevents
10-0510-0610-1710-2010-2210-28
Loading Situation timeline…

What kind of event · 2 coded types

over 2 coded events on this edition

  • Conflict1
    • PEACEFUL PROTEST1
  • Political1
    • 01 · Make Public Statement1

Countries · where it happened

Countries · who is acting

Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystShiva murder case: reports naming Shraddha Dubey

    These headlines name Shraddha Dubey and describe a Saharanpur connection, a check of border CCTV over a suspected crossing, her reported discovery in Nagpur, and an account of evasion. The headlines support presenting them together as a Dubey investigation thread, but do not confirm every reported detail.

    These headlines name Shraddha Dubey and describe a Saharanpur connection, a check of border CCTV over a suspected crossing, her reported discovery in Nagpur, and an account of evasion. The headlines support presenting them together as a Dubey investigation thread, but do not confirm every reported detail.

    Footnotes[6][5][4][2]
  2. development
    AnalystCrime Branch probe headline and Nuwakot protest Event

    The headline reports a Crime Branch takeover involving Saurabh Das and Ashutosh Ranka. Its linked Event describes a Nuwakot road blockade after a fatal crash, not the probe named in the headline.

    The headline reports a Crime Branch takeover involving Saurabh Das and Ashutosh Ranka. Its linked Event describes a Nuwakot road blockade after a fatal crash, not the probe named in the headline.

    Footnotes[3][8]
  3. unresolved
    AnalystHome-sealing action in a triple-murder case

    The headline reports authorities sealing a triple-murder suspect’s home and demolishing an illegal encroachment. It does not name the suspect.

    The headline reports authorities sealing a triple-murder suspect’s home and demolishing an illegal encroachment. It does not name the suspect.

    Footnotes[1]
  4. unresolved
    AnalystKazakhstan appointment Event and funeral-shooting headline

    The Event describes Tokayev appointing Omarbekov, while the linked headline describes a man shot dead at a funeral gathering. Those descriptions do not establish a shared incident.

    The Event describes Tokayev appointing Omarbekov, while the linked headline describes a man shot dead at a funeral gathering. Those descriptions do not establish a shared incident.

    Footnotes[9][7]

Key actors

    Key Events

    1. contextAnalystNuwakot residents block road after fatal crash, demand compensation

      On 20 October, local residents and relatives of a deceased person blocked a road in Nuwakot and demanded compensation after a fatal crash.

      On 20 October, local residents and relatives of a deceased person blocked a road in Nuwakot and demanded compensation after a fatal crash.

      Footnotes[8]
    2. contextAnalystTokayev appoints Omarbekov to lead Kazakhstan’s military General Staff

      On 5 October, President Kassym-Jomart Tokayev appointed Omarbekov to lead Kazakhstan’s military General Staff.

      On 5 October, President Kassym-Jomart Tokayev appointed Omarbekov to lead Kazakhstan’s military General Staff.

      Footnotes[9]

    Notable connections

    Evidenced relationships involving significant participants beyond the central cast.

    1. Both headlines name Shraddha Dubey and refer to the Shiva murder case; the border crossing is described as suspected · analytical connectionAnalystSaharanpur link emerges in Shiva murder case involving fugitive model Shraddha Dubey → Lucknow police check India-Nepal border CCTV over Shraddha Dubey’s suspected crossing

      The 17 October headline names the Shiva murder case involving Dubey; the 18 October headline names Dubey and describes a suspected crossing.

      The 17 October headline names the Shiva murder case involving Dubey; the 18 October headline names Dubey and describes a suspected crossing.

      Footnotes[6][5]
    2. The Event is linked to the Crime Branch Story, but their descriptions do not establish a shared incident · reporting linkAnalystNuwakot residents block road after fatal crash, demand compensation → Crime Branch takes over probe involving Saurabh Das and Ashutosh Ranka

      The Event describes a Nuwakot road blockade after a fatal crash; the Story headline concerns a Crime Branch probe involving Saurabh Das and Ashutosh Ranka.

      The Event describes a Nuwakot road blockade after a fatal crash; the Story headline concerns a Crime Branch probe involving Saurabh Das and Ashutosh Ranka.

      Footnotes[8][3]
    3. The appointment Event is linked to a funeral-shooting headline, but the descriptions do not match · reporting linkAnalystTokayev appoints Omarbekov to lead Kazakhstan’s military General Staff → Man shot dead at funeral gathering attended by about 50 people

      The Event describes Tokayev appointing Omarbekov; the headline describes a man shot dead at a funeral gathering.

      The Event describes Tokayev appointing Omarbekov; the headline describes a man shot dead at a funeral gathering.

      Footnotes[9][7]
    4. Shraddha Dubey is mentioned in the Story; this does not establish Event participation · reporting linkAnalystShraddha Dubey → Saharanpur link emerges in Shiva murder case involving fugitive model Shraddha Dubey

      The Story headline names Shraddha Dubey, and the Entity is associated with that Story as a mention, not as a recorded Event participant.

      The Story headline names Shraddha Dubey, and the Entity is associated with that Story as a mention, not as a recorded Event participant.

      Footnotes[10][6]
    Shraddha Dubey Investigation and Linked Reports share card
    Share · 19 Nov 2026

    Shraddha Dubey Investigation and Linked Reports, in one card

    How a Situation is put together9 Stories · 2 Events · 9 membership connections · 74 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 58 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.