GDELT CloudGDELT Cloud
Connected Situation / Through 2026-10-30

KM Virgo Ferry Disaster: Search, Identification and Investigation

stories
38
events
9
entities
131
connections
38
Retained edition
Evidence so far on 2026-10-30 UTC · updated 2026-10-30 00:26 UTC · analysis as of 2026-10-29 20:28 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On 13 September 2026, Indonesia lost contact with a passenger ship described in the Event as carrying 240 people, while “Indonesian passenger ferry carrying 243 people goes missing” gave a different passenger figure. South Kalimantan Governor Muhidin ordered hospitals and health facilities to prioritize Virgo victims that day. On 15 September, Indonesian search-and-rescue teams found ferry wreckage; “Ferry carrying 240 sinks in Indonesia, leaving six dead and 130 missing” reported an early toll. On 17 September, an Event described United States and Hong Kong teams searching for shipwreck victims, while “Indonesian rescue operation continues after ship capsizes, 129 missing” reported 129 missing. Basarnas deployed divers on 19 September, and “Divers recover three bodies as 126 remain missing from Indonesia ferry” reported three recoveries and 126 missing. On 22 September, “Virgo ship disaster update: five victims identified, four pending” reported identification in Banjarmasin. Indonesian police detained the ferry captain on 1 October, and “Indonesia police name four suspects in deadly Java Sea ferry sinking” reported four suspects named on 2 October.

Footnotes[22][19][26][20][24][16][23][14][25][11][28][8]
Assessment

The dated accounts trace a prolonged search and salvage operation, victim identification, and a criminal investigation. DVI work continued: South Kalimantan police retained the DVI team on 4 October, and a 9 October report said DNA testing on 10 bodies was still underway. They do not establish a reconciled passenger or casualty total: early reports differ, and later headlines give 64 dead and 71 missing, 78 dead and 57 missing, and 80 dead and 55 missing. The 1 October detention and the 2 October report naming four suspects establish investigative steps, not guilt or the cause of the sinking. The 6 October report says no victims were found on search day 23 and that Basarnas awaited wreckage salvage; it does not say the search had ended. The separate Anak Krakatau search concerned eight missing people and is not part of the Virgo disaster.

Footnotes[19][17][18][6][5][2][29][4][3][43][44][21]

Explanation originally captured 2026-10-29 · Evidence through 2026-10-30 UTC · Source edition sed_fc66aeacaa2c268dcd1bd50b3f8755cc

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 27-day Situation represented by 9 coded Events carried across 38 member Stories.

  • Coded activity

    The coded activity is led by IN02 · Transport Disruption (6) and CR08 · Arrest Charge Conviction or Sentencing (1).

  • Prominent subjects

    🇮🇩Indonesia is prominent in the retained actor and relationship evidence.

  • Entity coverage

    131 canonical Entities are linked to this edition.

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

Magnitude2.9
min 2max 5
8 measured
Systemic importance0.14
min 0.08max 0.23
9 measured
Propagation potential0.24
min 0max 0.41
9 measured
Market sensitivity0.09
min 0.05max 0.38
9 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 6 scores, distributions & definitions

How the coder scored the full retained Event set

9 coded events — 9 CAMEO+

  • Significance · 90.26
    min 0.16max 0.38
  • Magnitude · 82.9
    min 2max 5
  • Systemic · 90.14
    min 0.08max 0.23
  • Propagation · 90.24
    min 0max 0.41
  • Market · 90.09
    min 0.05max 0.38
  • Confidence · 90.63
    min 0.42max 0.94

No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 9 sit outside POLITICAL, where Goldstein and quad class are undefined.

Significance

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

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

across all 9 events

Magnitude

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

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

across all 9 events — every one of them CAMEO+

Systemic

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

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

across all 9 events — every one of them CAMEO+

Propagation

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

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

across all 9 events — every one of them CAMEO+

Market

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

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

across all 9 events — every one of them CAMEO+

Confidence

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

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

across all 9 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 day22 reporting days · click a day to open or close it

2026-10-09from the recordslatest

South Kalimantan DVI team explains how it identified hard-to-recognize Virgo victims

1 Story and 0 coded Events (0 / 0 against the day before). Widest coverage: South Kalimantan DVI team explains how it identified hard-to-recognize Virgo victims (2 articles).

South Kalimantan DVI team explains how it identified hard-to-recognize Virgo victims
10
Stories · vs day before
00
Events · vs day before
2
articles
The lay of the land

Situation timeline

Threads
All 22 daysarticlesstoriesevents
09-1309-1709-2109-2610-0110-09
Loading Situation timeline…

What kind of event · 4 coded types

over 9 coded events on this edition

  • Infrastructure6
    • IN02 · Transport Disruption6
  • Crime1
    • CR08 · Arrest Charge Conviction or Sentencing1
  • Environment1
    • EN01 · Geophysical Hazard1
  • Health1
    • HE04 · Public Health Policy Action1

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
    AnalystVirgo ferry loss, search, salvage and casualty reports

    These Stories and linked Events cover the ferry loss, search and salvage activity, recoveries, and changing casualty reports.

    These Stories and linked Events cover the ferry loss, search and salvage activity, recoveries, and changing casualty reports.

    Footnotes[22][19][17][24][16][12][23][14][25][11][10][9]
  2. development
    AnalystVictim identification and police investigation

    These Stories report family DNA collection, victim identification and continued DVI work, captain detention, and the naming of four suspects.

    These Stories report family DNA collection, victim identification and continued DVI work, captain detention, and the naming of four suspects.

    Footnotes[15][28][8][1][29][4][3]
  3. unresolved
    AnalystSeparate Anak Krakatau missing-person search

    The Event and linked headline concern a search for eight people near Anak Krakatau, separate from the Virgo sinking.

    The Event and linked headline concern a search for eight people near Anak Krakatau, separate from the Virgo sinking.

    Footnotes[21][13]

Key actors

    Key Events

    1. contextAnalystIndonesia loses contact with passenger ship carrying 240 people

      Dated 13 September, this Event describes Indonesia losing contact with a passenger ship carrying 240 people; the linked headline gives 243.

      Dated 13 September, this Event describes Indonesia losing contact with a passenger ship carrying 240 people; the linked headline gives 243.

      Footnotes[22][19]
    2. contextAnalystSouth Kalimantan governor orders hospitals to prioritize Virgo victims

      On 13 September, South Kalimantan Governor Muhidin ordered hospitals and health facilities to prioritize Virgo victims.

      On 13 September, South Kalimantan Governor Muhidin ordered hospitals and health facilities to prioritize Virgo victims.

      Footnotes[26][20]
    3. contextAnalystIndonesian rescuers find missing ferry wreckage as search continues

      Dated 15 September, this Event describes Indonesian search-and-rescue teams finding ferry wreckage as the search continued.

      Dated 15 September, this Event describes Indonesian search-and-rescue teams finding ferry wreckage as the search continued.

      Footnotes[24][16]
    4. contextAnalystUnited States and Hong Kong teams search for Indonesia shipwreck victims

      Dated 17 September, this Event describes United States and Hong Kong teams searching for shipwreck victims; the linked headline reports 129 missing.

      Dated 17 September, this Event describes United States and Hong Kong teams searching for shipwreck victims; the linked headline reports 129 missing.

      Footnotes[23][14]
    5. contextAnalystIndonesia deploys divers to search for KM Virgo victims

      Dated 19 September, this Event describes Basarnas deploying divers; the linked headline reports three bodies recovered and 126 missing.

      Dated 19 September, this Event describes Basarnas deploying divers; the linked headline reports three bodies recovered and 126 missing.

      Footnotes[25][11]

    Notable connections

    Evidenced relationships involving significant participants beyond the central cast.

    1. The loss-of-contact Event links to “Indonesian passenger ferry carrying 243 people goes missing.” · reporting linkAnalystIndonesia loses contact with passenger ship carrying 240 people → Indonesian passenger ferry carrying 243 people goes missing

      The headline gives 243 people, while the Event title gives 240.

      The headline gives 243 people, while the Event title gives 240.

      Footnotes[22][19]
    2. The hospital-priority Event links to the Story about Muhidin’s order. · reporting linkAnalystSouth Kalimantan governor orders hospitals to prioritize Virgo victims → South Kalimantan orders hospitals to prioritize Virgo Transport 8 crash victims

      The headline reports South Kalimantan’s order to prioritize Virgo victims at hospitals.

      The headline reports South Kalimantan’s order to prioritize Virgo victims at hospitals.

      Footnotes[26][20]
    3. The search Event links to “Indonesian rescue operation continues after ship capsizes, 129 missing.” · reporting linkAnalystUnited States and Hong Kong teams search for Indonesia shipwreck victims → Indonesian rescue operation continues after ship capsizes, 129 missing

      The Event describes United States and Hong Kong teams searching; the Story headline reports 129 missing.

      The Event describes United States and Hong Kong teams searching; the Story headline reports 129 missing.

      Footnotes[23][14]
    4. The Basarnas diver-deployment Event links to the recovery and missing-person headline. · reporting linkAnalystIndonesia deploys divers to search for KM Virgo victims → Divers recover three bodies as 126 remain missing from Indonesia ferry

      The linked Story headline reports three bodies recovered and 126 missing.

      The linked Story headline reports three bodies recovered and 126 missing.

      Footnotes[25][11]
    5. The Banjarmasin victim-identification Event links to “Virgo ship disaster update: five victims identified, four pending. · reporting linkAnalystVirgo Transport 8 victims identified in Banjarmasin → Virgo ship disaster update: five victims identified, four pending

      The Story headline reports five victims identified and four pending.

      The Story headline reports five victims identified and four pending.

      Footnotes[28][8]

    Current related Situations

    Explore all →

    Finding connected developments…

    Compared with currently maintained Situation membership; this list is not part of the retained edition above.

    How a Situation is put together38 Stories · 9 Events · 38 membership connections · 341 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 131 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.