Wire
08:31ZTHECRADLEMTrump administration prepares $2.8 billion weapons sale to Israel08:31ZTHEPRINTINCIA Director Ratcliffe Calls Document Release 'Exceptional Transparency' Despite Redactions08:31ZWFWITNESSIsraeli forces entered the eastern neighborhood of Halta, searching homes08:30ZMEGATRONROHouthis claim they shot down a Saudi F-15 fighter jet over Marib08:29ZHINDUSTANTLionel Messi announces retirement from international football08:28ZCLASHREPOREU's von der Leyen Discusses Canada as Potential First Associate Member with Carney08:25ZNYT > WORLHouthis Say They Downed a Saudi Fighter Jet and Deny Targeting Mecca08:25ZDEUTSCHE WVon der Leyen eyes Canada as EU's first 'associate member'
  • S&P 500 ETF 0.16%
  • Nasdaq 0.78%
  • Nasdaq 100 0.65%
  • Dow ETF 0.09%
Terminal ↗
← The MonexusOpinion

The Telegram channel driving Russia's glide-bomb narrative

Three posts in 70 minutes from one Russian Telegram channel packaged Smuglyanka and Rubicon FAB strikes as branded battlefield content. The format is the message.

Three posts in 70 minutes from one Russian Telegram channel packaged Smuglyanka and Rubicon FAB strikes as branded battlefield content.
Three posts in 70 minutes from one Russian Telegram channel packaged Smuglyanka and Rubicon FAB strikes as branded battlefield content. DW / Photography

At 13:47 UTC on 14 July 2026, the Russian Telegram channel Two Majors posted a compilation of FAB strikes credited to two Russian Aerospace Forces units it identified only as Smuglyanka and Rubicon. By 14:10 UTC the same channel had pushed a more granular follow-up: a single FAB dropped on Gusinka village in Kondrashevskaya rural community, Kupiansk district, Kharkiv oblast, again attributed to those same units. By 14:55 UTC the channel had reposted the original compilation. Three posts, seventy minutes, one consistent message: the glide-bomb campaign in the Kupiansk sector is not a backdrop statistic but a branded tactical product, and the two units responsible are the brand.

The repetition matters. Telegram channels aligned with Russia's war effort have spent the last two years turning individual munitions into serialised content. A single FAB strike on a hamlet of no strategic consequence is, on its own, a footnote. The same strike packaged twice inside an hour, framed by a named unit and a known channel, becomes proof of method. The Two Majors format here, claim, republish, is the standard rhythm.

What Two Majors actually showed

The 13:47 compilation was a cut of FAB drops attributed to Smuglyanka and Rubicon, with no location set, no casualty figures, and no acknowledgment of any wider operation. The 14:10 post narrowed the lens to one village. Gusinka sits inside Kondrashevskaya rural community in Kupiansk district, an area that has sat on or near the line of contact in Kharkiv oblast since the 2022 cross-border offensive and the subsequent Ukrainian counter-offensives. The post again named Smuglyanka and Rubicon as the guiding units. The 14:55 repost was a verbatim re-share of the 13:47 compilation.

Two things follow from the sequencing. First, the channel is treating Smuglyanka and Rubicon as recurring authors. The unit names function the way a byline functions in a newsroom: this is whose work we are showing you. Second, the choice of Kupiansk district as the location for the more detailed post is deliberate. The Kupiansk axis is one of the few places along the northern front where Russian forces have been consistently pressing, and the village-level granularity gives the channel a foothold in the geography Ukrainian sources also use.

The counter-narrative readers should hold in mind

Two Majors is a Russian-aligned milblogger channel, not a neutral wire service. Its reporting carries no sourcing caveats of its own, no correction mechanism, and no editorial line independent of the war effort it covers. The unit names Smuglyanka and Rubicon have circulated inside Russian Telegram for months, but neither has been confirmed in Ukrainian General Staff briefings, in Western open-source intelligence outfits such as the Institute for the Study of War, or in the daily mapping products published by independent analysts tracking the Kharkiv front. That does not make the strikes imaginary; glide-bomb use along this axis is corroborated independently. It means the brand attribution is, at this point, a Russian-channel artefact rather than a verified fact.

Ukrainian-side reporting on Kupiansk district, where it surfaces, describes sustained FAB and KAB use against Kharkiv oblast positions and civilian infrastructure, but does not single out Smuglyanka or Rubicon as named units. The honest framing is: glide bombs are falling on this axis; the names attached to the operators are, for now, the messenger's claim.

What the packaging itself reveals

Coverage of the war routinely defers to the language of official spokespeople. In the Russian information space, the spokespeople are increasingly channels like Two Majors, and the spokes-units are increasingly named volunteer formations rather than conventional brigades. Smuglyanka and Rubicon are useful handles precisely because they let a channel attach a recurring identity to a strike campaign that the Russian Ministry of Defence still aggregates into impersonal daily summaries.

That is a structural shift, not a cosmetic one. The Russian state's preferred model for years was silent attribution: the MoD reports numbers of strikes and leaves the operational details opaque. The volunteer-channel model turns opacity into product. The unit becomes the author, the channel becomes the publisher, and the FAB becomes a serial release with a version number. A reader does not need to believe the brand to notice the change in how the war is being sold.

What to watch next

The next test is whether Smuglyanka and Rubicon surface in Ukrainian or Western reporting in a verifiable form. If they do, the Two Majors packaging turns out to have been early branding for real tactical units, and the channel's editorial lead becomes a story in its own right. If they do not, the names will probably keep circulating inside Russian-language Telegram, accumulating footage and reputation, while remaining unverifiable from the other side of the front.

Either way, the 14 July sequence is now on the record: three posts in seventy minutes, one village named, two units named, one consistent format. The campaign along the Kupiansk axis will continue. The Telegram channel covering it has already decided what kind of story it wants that campaign to be.

Monexus framed this as a media-and-messaging story: the named units and the channel format are themselves part of the battlefield product, and the Ukrainian front-line reporting on glide-bomb use is held separately from the Russian-channel brand attribution.

Wire provenance

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

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

Follow the event.

These dated source records provide context. They do not retrospectively verify this archive article.

Ukraine: the war and diplomacy

A dated voting record is evidence of one decision. Use the original UN record before turning it into an alignment label.

Visual explainer · historical vote of 2022-03-02
© 2026 Monexus Media · AI-native reporting from public-source material
The Monexus

Read with context.

Using this article and its related event records

Find the evidence behind a claim, inspect a dated position, or pick up the thread.

Source lookup is available to everyone. Members can request an AI explanation grounded in the retrieved material.

Browse event files →
The Telegram channel driving Russia's glide-bomb narrative - The Monexus