Russian strike drones stockpiled overnight before June 24 massed attack, milbloggers say

At 04:06 UTC on 24 June 2026, the Russian-aligned Telegram channel Two Majors posted a morning situation report claiming that Russian forces had spent several days stockpiling long-range strike UAVs, a pattern that — the channel argued — was already visible in the reduced daily count of downed drones being reported by the Ukrainian defence ministry. By 04:38 UTC, the channel Rybar carried a near-identical line in its own morning summary, and an English-language mirror of the same post appeared on the @rybar_in_English feed at 04:39 UTC. The three messages, all posted within a 33-minute window, constitute a coordinated framing of an expected wave of Russian air strikes later in the day.

The claim is one-sided — every named source is Russian-aligned, and the only counter-data point the channels cite is the Ukrainian ministry's own daily drone-intercept tally, which the channels read as evidence of an imminent, larger strike. Ukrainian air force and General Staff figures for the same 24-hour window have not yet been independently verified in the source material Monexus reviewed. Read together, the three messages are best understood not as dispatches from the battlefield but as a piece of pre-strike signalling directed at Russian-language audiences: the channels are telling readers that what looks like a quiet day for Russian aviation is, in fact, the loading phase of a heavier attack.

What the two channels actually said

Two Majors opened at 04:06 UTC with the framing that "the enemy spent several days stockpiling strike UAVs," and pointed to "the reduced statistics of downed drones reported by the defence ministry" as the tell. The wording is ambiguous about which "defence ministry" is meant — in milblogger shorthand, "the defence ministry" usually denotes the Russian MoD, but in a sentence that begins by calling Russia "the enemy" it could be read as referring to Ukraine. Rybar's 04:38 UTC post is structurally identical: it describes a multi-day build-up of "attack UAVs" and again attributes the inference to a falling count of intercepts from "the defense department." The English-language mirror at @rybar_in_English at 04:39 UTC repeats the formulation a third time, this time naming "the defense ministry" explicitly. Across the three posts, the only numerical claim is implied — that daily intercept numbers are currently lower than the recent run rate — and the only specific allegation is that the gap reflects Russian stockpiling rather than a genuine lull in launches.

The three Telegram feeds are widely followed Russian milblogger operations. Two Majors (Два майора) is read as broadly pro-Kremlin and is often cited for frontline operational colour from the Russian side. Rybar, run by Denis Grigorenko (though presented as a channel rather than a personal account), publishes daily situation reports that blend confirmed reporting with pro-Russian interpretation, and operates an English-language mirror under the @rybar_in_English handle. All three feeds should be read as counter-claim material, not as stand-alone factual ground. They are useful in this case less for what they say about Russian intent than for what their convergence tells us about how Russia's information space prepares its audience for an attack wave.

The pattern the channels are pointing at

Long-range strike UAVs — chiefly the Iranian-designed Shahed-136 and its Russian-produced Geran-2 analogue — are now the dominant instrument of Russian deep-strike on Ukrainian energy, rail and port infrastructure. The pattern the two channels are flagging is a familiar one in this war: a sequence of low-volume nights during which Russian launch rates fall noticeably, followed within 24 to 72 hours by a much heavier barrage. Two operational mechanisms make the lull-stockpile-barrage pattern plausible. First, the Shahed-class airframe is cheap and modular, and Russia has standing industrial contracts in place to deliver them in batches; a temporary dip in launch tempo does not constrain supply, it frees it. Second, the conditions required for a massed strike — favourable upper-level winds, available launch platforms, command-level authorisation — are typically decided in Moscow several days in advance, and milbloggers with contacts in Russian airbases and command nodes are often the first to notice the queue forming.

The framing the channels choose is also revealing. By attributing the inference to the enemy's own published intercept statistics, the channels are borrowing a piece of Ukrainian public data to make a Russian-side claim. It is a small but telling move: the Russian information space is in this case citing Kyiv's own numbers, on the assumption that the interpretation — stockpiling, not lull — is the point on which their audience needs to be brought onside before the next barrage lands and the underlying numbers spike again. If a heavy wave of strikes does follow later on 24 June, the channels will be able to say, after the fact, that they had warned the audience in advance. If it does not, the framing can be quietly dropped, since no specific launch count, time or target was named in any of the three posts.

What the Ukrainian side says — and what it doesn't

The source material Monexus reviewed does not include an official Ukrainian Air Force morning briefing for 24 June 2026, nor a General Staff statement on overnight drone activity that explicitly addresses the stockpile claim. The Ukrainian defence ministry's daily drone-intercept count, which the milbloggers cite as the load-bearing data point, has in previous months shown multi-day dips followed by single-night spikes in the dozens — a tempo consistent with the kind of stockpiling pattern the channels describe. But the present article cannot confirm that the 23–24 June run rate was anomalously low, only that two Russian-aligned channels are claiming it was, and that the public Ukrainian data they point to is not in evidence in the source set. Any firm conclusion that a wave of strikes was imminent as of 04:39 UTC would require either an official Ukrainian statement or independent OSINT on launch activity at Russian forward operating bases — neither of which is present here.

What we verified / what we could not

Verified from the source set: That the channels Two Majors, Rybar, and the @rybar_in_English mirror each posted, between 04:06 and 04:39 UTC on 24 June 2026, a claim that Russian forces had spent several days stockpiling strike UAVs; that all three posts pointed to reduced daily drone-intercept figures from "the defence ministry" as the supporting evidence; and that the three posts use near-identical language, consistent with a shared underlying talking point rather than independent reporting.

Could not verify from the source set: The actual run rate of Ukrainian drone intercepts over the days leading up to 24 June 2026; whether a massed Russian strike followed later in the day; any official Ukrainian Air Force or General Staff comment on the stockpile claim; the identity of the author of the stockpile assertion within Two Majors or Rybar; the precise weapon system the channels mean by "strike UAVs" (Shahed-136, Geran-2, or another platform); and the operational source inside Russian airbases that the two channels would, in a transparent reporting environment, name.

Stakes

If the stockpile claim is borne out by events later on 24 June, the practical stakes are familiar ones: civilian energy infrastructure, port facilities and rail junctions in the rear of Ukraine will be the likely targets, with cascading effects on power rationing, grain export logistics and refugee movement. The information stakes are different and arguably more durable. Two of Russia's most-read milblogger channels are, in real time, demonstrating a coordination routine — same line, same frame, same supporting data point — within 33 minutes of each other. For an audience trying to read Russian intent in the hours before a strike wave, the relevant signal is not the drone count but the synchronisation. Monexus framed this as a piece of Russian information-space signalling, with the three Telegram posts read as counter-claim material and the underlying Ukrainian intercept data flagged as unverified in the source set; mainstream wire outlets have not yet published a comparable item as of the time of writing.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/two_majors
• https://t.me/rybar
• https://t.me/rybar_in_English