Methodology

About REAPERDRONES

A public, automated record of combat drone losses across active conflicts. Every entry links to its primary source. This site documents — it does not glorify, advocate, or take sides.

Verification tiers

Visually confirmed — photo or video evidence of the wreckage exists. Highest confidence.
Reported — credible outlets or official sources have reported the loss without published imagery. Medium confidence.
Claimed — only one party to the conflict has asserted the loss, with no independent corroboration. Lowest confidence.

Aggregate entries

Daily MoD and air force briefings often report bulk numbers — "47 Shahed drones intercepted overnight." A single entry can therefore represent N losses; the count appears in the table and as a badge on the entry page. Volume is the real story of modern drone warfare and tracking only one-off named-platform losses would dramatically understate it.

Sources

Data is aggregated daily from public RSS feeds, defence outlets, OSINT analysts, and official MoD/air force briefings. An LLM extracts structured incident data; entries are spot-checked but not individually verified beyond the cited source. If you find an entry you believe is incorrect, the source link will take you to the original report.

Editorial approach

REAPERDRONES tracks losses on every side of every conflict it covers. The point is documentation: drones are reshaping modern warfare and the public record of who lost what, when, and to whom is fragmented across Twitter threads, Telegram channels, and government statements. This is an attempt to consolidate it.

Real people operate these systems. Real consequences flow from their loss. Read accordingly.

Corrections

This is not original reporting. Every entry restates what a primary source has already published, and every entry links to that source. If you believe an entry is factually wrong, the issue almost always lies in the source material itself — please direct corrections to the publishing organisation linked at the bottom of each entry.

If a structural issue with the site itself surfaces (a broken link, a misclassified drone type, a mislabelled conflict), it will be picked up automatically as the daily intake refreshes.