At least 13 killed in Russian attack on Dnipro train station

A Russian missile or drone attack targeted the train station in Dnipro, resulting in at least 13 fatalities. This incident represents a significant escalation in attacks on Ukrainian civilian infrastructure. The casualty count is based on media reporting of the event.

Happened:

First reported:

Last updated:

Time: reported 11:47Z · occurred 2026-10-29 (hour)

Location: Dnipro, Ukraine

Basemap: Esri.

Conflict: Russia-Ukraine War

Category: airstrike

Severity: CRITICAL

Status: CONFIRMED

Killed: 13-14

MEDIA COUNTTOWN

Source: Al Jazeera

Also reported by: The Guardian

Merged reports:
  • Russian drone kills 14 on rail platform in Dnipro 2026-10-30 00:00 UTC
  • Russian drone strikes railway platform in Dnipro 2026-10-30 00:00 UTC
  • At least 14 killed in Russian missile attack on Dnipro train station 2026-10-29 00:00 UTC
  • Russian drone attack hits Dnipro train station (The Guardian) merged 2026-10-30 15:05 UTC
  • Russian Missile Attack on Dnipro Train Station (Al Jazeera) merged 2026-10-30 02:02 UTC
  • Russian attack on Dnipro train station (Al Jazeera) merged 2026-10-30 00:04 UTC
  • Russian Attack on Dnipro Train Station (Al Jazeera) merged 2026-10-29 23:02 UTC
  • Russian missile attack on Dnipro train station (Al Jazeera) merged 2026-10-29 19:05 UTC
  • Russian missile attack on Dnipro train station (Al Jazeera) merged 2026-10-29 17:02 UTC
  • Russian missile attack on Dnipro train station (Al Jazeera) merged 2026-10-29 16:02 UTC
  • Russian missile attack on Dnipro train station (Al Jazeera) merged 2026-10-29 15:02 UTC
  • Russian missile strike on Dnipro train station kills at least 13 (Al Jazeera) merged 2026-10-29 14:04 UTC
  • Russian missile attack on Dnipro train station (Al Jazeera) merged 2026-10-29 13:04 UTC
Revisions:
  • 2026-11-03 geocoder: nominatim → nominatim (regeocode_wrong_feature)
  • 2026-11-03 geocode_confidence: 0.6739536939969055 → 0.656021262640693 (regeocode_wrong_feature)
  • 2026-11-03 geo_precision: 4 → 2 (regeocode_wrong_feature)
  • 2026-11-03 lng: 30.6121981 → 35.0417711 (regeocode_wrong_feature)
  • 2026-11-03 lat: 51.5567163 → 48.4680221 (regeocode_wrong_feature)
  • 2026-11-03 merged_count: 41 → 42 (manual_merge)
  • 2026-11-03 merged_count: 10 → 41 (manual_merge)
  • 2026-11-03 killed_max: 13 → 14 (manual_merge)
  • 2026-11-03 casualties: 13 → 14 (manual_merge)
  • 2026-10-30 merged_count: 9 → 10 (dedupe_merge)
  • 2026-10-30 merged_count: 8 → 9 (dedupe_merge)
  • 2026-10-30 merged_count: 7 → 8 (dedupe_merge)
  • 2026-10-29 merged_count: 6 → 7 (dedupe_merge)
  • 2026-10-29 merged_count: 5 → 6 (dedupe_merge)
  • 2026-10-29 merged_count: 4 → 5 (dedupe_merge)
  • 2026-10-29 merged_count: 3 → 4 (dedupe_merge)
  • 2026-10-29 merged_count: 2 → 3 (dedupe_merge)
  • 2026-10-29 merged_count: 1 → 2 (dedupe_merge)
  • 2026-10-29 merged_count: 0 → 1 (dedupe_merge)

Share: XWhatsAppTelegram

How we count and locate events

Discuss in #warheatmap on EFnet

View this event on the live WAR 3.0 conflict map