Strikes, Smokescreens and the Steady Drumbeat of Daily Telegram War Logs

At 21:26 UTC on 15 June 2026, the Telegram channel @rybar_in_English published its nightly dispatch under a familiar header: Chronicles of the special military operation. The post, a short catalogue of battlefield events, claimed that Russian forces had carried out a combined strike on Ukrainian defence enterprises, including a hit inside Kyiv. The message was terse, eight lines, no images of the damage. By the standards of the channel, that is unremarkable: Rybar, named after its founder Mikhail Zvinchuk, has been producing a near-nightly log since the spring of 2022. The post is, however, a useful exhibit. It shows what the war sounds like when the cameras are off and the only author on duty is a Russian milblogger with a smartphone, an audience, and a translator.

For Western readers, the daily Rybar post has become a strange but unavoidable artefact. The channel is openly aligned with the Russian side, openly pro-war, and openly the kind of source that mainstream news desks would not quote without a long caveat. Yet the feeds of Reuters, the BBC, the Kyiv Independent, and the Institute for the Study of War (ISW) routinely parse Rybar's claims, sometimes within hours. It is, in plain terms, a primary source for the rhythm of the war that nobody trusts and almost everybody reads.

The shape of the daily log

The 15 June post follows a recognisable template. A short header: Chronicles of the special military operation. A date stamp. A one-line newsbeat: a strike. Then a bracketed list of struck objects, with targets and locations named in the clipped language of operational reporting — "defence enterprises," "on the territory of so-called Ukraine," "in the capital." The verb tense is unadorned. There is no admission of Russian civilian harm, no parallel description of the Ukrainian side's reported air-defence response, no mention of any Russian losses. The post is what it claims to be: a battlefield ledger from one side of the line, sent at the end of the working day.

What makes such a post newsworthy for non-Russian audiences is the regularity. By June 2026, Russian milblogger channels have become a de facto second wire service for the war. Rybar and its peers — Two Majors, WarGonzo, the Voennor Osvedomitel (Military Informant) account — each carry hundreds of thousands of subscribers. Their claims are often the first to surface about a strike, a village capture, or a Ukrainian deep-action. The information environment around the war is, in effect, a two-tier market: the Western wire services arrive later, with their own confirmation, their own sourcing, and their own picture desks; the Telegram feeds arrive first, in the native voice of the war, and are then either confirmed, refined, or quietly contradicted by everything that follows.

Why the Western wires parse the Russian channel

The willingness of Western news desks to lean on Russian milblogger content is partly a function of necessity. Ukraine's General Staff briefings are public, daily, and detailed, but they cover the front. Russian strategic strikes on Ukrainian infrastructure — power, rail, defence industry — happen behind the front. Initial reporting on such strikes often begins with the target's air-defence report, the mayor's Telegram channel, or a piece of geolocated video, but the cleanest read on what was aimed at is often the Russian side's own announcement, dropped on a Telegram channel and then amplified by TASS, RIA Novosti, and the Russian defence ministry's Zvezda outlet.

The practice has aged badly in some quarters. In 2024 and 2025, several European broadcasters drew criticism from Ukrainian civil-society groups for quoting Rybar and Two Majors on the record without sufficiently explicit framing. The argument from the Ukrainian side was straightforward: Russian milbloggers are not reporters, they are combatants with an audience strategy; the platforms that host their content are also the platforms that host the practical coordination of Russian air-strike packages, with drone operators and spotter channels sitting two clicks away from the propaganda layer. Mainstream news desks have, on the whole, adopted a compromise. They parse the channel's claims and check them against the Ukrainian Air Force, the Kyiv City Military Administration, and the relevant open-source-intelligence (OSINT) trackers. They do not, generally, run a Rybar line as a stand-alone fact.

The culture of the log, and what it carries with it

There is, however, a deeper question than sourcing hygiene. The persistence of a daily Russian-channel summary, in the same format, in the same tone, year after year, is itself a cultural object. The format is almost journalistic in structure — bullet points, dateline, source-coded attribution — but its purpose is performative. It is a daily receipt, delivered to a Russian and Russian-adjacent audience, that the war is being fought, that the leadership is being kept informed, that strikes are happening, that the tempo is being maintained. The phrase special military operation — the official Russian lexical choice for what the rest of the world calls the full-scale invasion — sits in the header as a kind of code, signalling to the Russian reader that the author is operating inside the permissible line.

The phrasing of the 15 June post — the territory of so-called Ukraine, in the capital — has the same function. The channel is reminding its readers, and reminding itself, of a discursive position: that the state it covers does not recognise the Ukrainian state in the form that Kyiv's government understands. Whether or not a reader accepts that frame, the post is doing something in front of them. The war, on this view, is not just a sequence of strikes. It is a sequence of strikes plus a daily act of framing, distributed on a free platform, read by both sides, and quietly shaping what each side thinks the other side is saying.

What the Western reader is left with

For a reader outside the Russian information space, the practical question is whether the content of a Rybar or Two Majors post is a reliable guide to what actually happened on the night in question. The honest answer is: usually partial, sometimes accurate, occasionally wrong, and almost always interesting. The 15 June strike claim, for instance, will, within hours, have a Ukrainian counter-version — air-defence intercept numbers, target locations, civil-infrastructure damage. Both accounts will end up in the next morning's Western news product, sourced to Ukrainian military briefings and to the Russian-aligned channel, with the appropriate caveats.

What is harder to weigh is the cumulative effect. Eighteen months into the daily-broadcast phase of the war, the Russian milblogger corpus has produced a steady background hum of strike claims, advance claims, after-action claims, and warnings of what is coming next. The Western wire services, working to tight deadlines, have at times lifted phrasing from those claims in ways that the channels themselves could not have predicted. The result is a slow bleed in which the line between what one side says happened, and what gets reported as having happened, narrows. The Telegram post is, in that sense, a small reminder: the channel that gets there first often sets the table for the channels that arrive later, even when nobody likes the food.

The desk note: Monexus runs the post as an exhibit, not as a report. Russian milblogger Telegrams are research material; the substance of any claim in them has to be cross-checked against Ukrainian and Western-wire reporting before it travels as fact on this site.

Wire provenance

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

• https://t.me/rybar_in_English