Skip to content
BC Hub
Powered by Pagefind
Defense & team strategy

Build and Conquer Drones vs C-RAM: A Recorded 72-Drone Raid

Follow the visible targeting and airborne counters in a dated 72-drone raid without treating the clip as a controlled interception test.

10/15/2026 Beta / dated sources BC Hub Editorial Last updated: 10/15/2026 3 min read

What does the raid actually show?

The title is 72 DRONES VS C-RAM AND MISSLES, but a title is not a statistical result. At 0:04, the HUD reads Shahed selected, 72 of 100 targets and zero ready, with a Fire 72 button. Later, the airborne view displays explosions and a different counter for drones still up.

72 selected targets, 0 ready and Fire 72 button in this particular raid. Not a controlled matchup.
Open full-size image

Warmense; 2026-10-03; 0:04. Watch the original recording. Game imagery © The Slop Company.

Position in the recording Visible state What it establishes
0:04 72 selected targets, 0 ready, Fire 72 Selection and readiness are separate fields
0:54 72 drones up An in-flight group is being tracked
1:24 Explosions, 43 drones up The tracked airborne count has fallen
1:44 24 drones up; building timers at defender The defense is not held constant throughout the clip
1:54 14 drones up A later remaining-flight count, not a final hit count
Airborne explosions with 43 drones up. The counter does not identify a unique cause for each removed drone.
Open full-size image

Warmense; 2026-10-03; 1:24. Watch the original recording. Game imagery © The Slop Company.

Why is this not an interception percentage?

The recording does not pair every removed drone with a selected defense, its ammunition state and a confirmed intercept. Arrival or impact, camera tracking changes and multiple defensive systems must be separated before a counter difference can be assigned to C-RAM. The final per-target damage and final outcome for every launched drone are not established by this sequence. Subtracting 43 from 72 is not a valid universal interception calculation.

What can an attacker learn from it?

Before committing a batch, read selected targets, ready inventory and the confirmation count. Observe how the group behaves in flight and distinguish a failed launch from a launch that encounters defense. Do not assume the clip’s older volley interface overrides the later October 15 waiting message. Preparing another group still requires the appropriate product and launcher state.

What can a defender learn from it?

Match the actual threat class to an appropriate system. The separately inspected CIWS card names drones and cruise missiles, while Arrow 3 explicitly excludes drones. New construction during a raid changes the defended state, so record system readiness and build completion when evaluating your own layout. This case supports careful observation and layered planning; it does not establish a guaranteed saturation recipe or a best swarm size.

Where should you go next?

Evidence & recording dates

Recorded values describe the source shown below. They may differ from your current game. Interpret numerical fields together with their version and context.

Related Articles

Was this helpful?