<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><id>https://droneincidents.com/feeds/incident/auto-ru-2026-10-13-310da5da0e.xml</id><title>DroneLedger: Drone wave reported in Moscow, Russia</title><link rel="self" type="application/atom+xml" href="https://droneincidents.com/feeds/incident/auto-ru-2026-10-13-310da5da0e.xml"/><link rel="alternate" type="text/html" href="https://droneincidents.com/incident/auto-ru-2026-10-13-310da5da0e/"/><updated>2026-10-13T00:00:00Z</updated><author><name>DroneLedger</name></author><entry><id>tag:droneincidents.com,2026:revision/auto-ru-2026-10-13-310da5da0e/4</id><title>Drone wave reported in Moscow, Russia: revision 4</title><link rel="alternate" type="text/html" href="https://droneincidents.com/incident/auto-ru-2026-10-13-310da5da0e/v4/"/><updated>2026-10-13T00:00:00Z</updated><summary>Place refined from country to city level: the cited reports describe an attack on Moscow itself (falling debris in the city, a refinery hit in Kapotnya), not only drones heading towards it. City level only.</summary></entry><entry><id>tag:droneincidents.com,2026:revision/auto-ru-2026-10-13-310da5da0e/3</id><title>Drone wave reported in Moscow, Russia: revision 3</title><link rel="alternate" type="text/html" href="https://droneincidents.com/incident/auto-ru-2026-10-13-310da5da0e/v3/"/><updated>2026-10-13T00:00:00Z</updated><summary>Removed a drone count: the source gives several running figures from the same speaker (or a partial 'another N'), so a single number would misstate the total.</summary></entry><entry><id>tag:droneincidents.com,2026:revision/auto-ru-2026-10-13-310da5da0e/2</id><title>Drone wave reported in Moscow, Russia: revision 2</title><link rel="alternate" type="text/html" href="https://droneincidents.com/incident/auto-ru-2026-10-13-310da5da0e/v2/"/><updated>2026-10-13T00:00:00Z</updated><summary>Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.</summary></entry></feed>
