12 measurements spanning 11 days, net -306. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 95,345–95,743 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Aug 2026, 10:36
95,391
-46
15 Aug 2026, 18:17
95,437
-29
14 Aug 2026, 04:48
95,466
-45
12 Aug 2026, 22:03
95,511
-22
11 Aug 2026, 23:12
95,533
-30
10 Aug 2026, 21:31
95,563
-37
9 Aug 2026, 21:31
95,600
-31
8 Aug 2026, 20:26
95,631
-32
7 Aug 2026, 22:06
95,663
+1
7 Aug 2026, 00:15
95,662
-35
6 Aug 2026, 02:00
95,697
no change
6 Aug 2026, 01:47
95,697
first reading
Engagement
193 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
2.73%
avg views ÷ 95,391 subscribers
Avg views / post
2,600
193 posts measured
Reaction rate
5.24%
reactions ÷ views · ER floor
Posts in window
193
of 193 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 August 2026
Posts held
193 (5 August 2026 – 17 August 2026)
Views total
501,984
Reactions total
26,291
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Aug 2026, 10:19 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Video runtime
53m 34s
Average length
32s
Measured directly from 102 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
23,776 reactions across 174 posts, in 7 distinct kinds. The most used accounts for 37.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
8,903
37.4%
👏
7,913
33.3%
🔥
3,991
16.8%
🥰
2,627
11.0%
🤬
149
0.627%
😢
118
0.496%
😱
75
0.315%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 193 of the 193 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 26,291reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 193 most recent posts we hold, published 5 August 2026 to 17 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🎖🎖 by Russian Defence Ministry on progress of special military operation as of 17 August 2026
Part 2 (👉 see Part 1)
🚩 As a result of resolute actions of the Tsentr Group's units, the village of Andreyevskaya Obshchina of the Donetsk People's Republic has been liberated.
🔥The Group's units inflicted losses on manpower and hardware of three mechanised brigades, a jaeger brigade, an assault brigade, three assault reg…
The Armed Forces of the Russian Federation continue the special military operation.
📍The Sever Group of Forces improved its tactical situation. The Group's units inflicted losses on manpower and hardware of two mechanised brigades, two airmobile brigades of the AFU, and a territorial defence brigade near Velikaya Chernetchina, Pershe Travnya, Pisarevka, Ulanovo, and Khoten in Sumy region.
💥 In Kharkov region, Russi…
🔥 Geran UAVs mop up enemy positions
🎯 In the crosshairs of our birds:
▫️a depot of unmanned aerial vehicles in Dmitrovka of Dnepropetrovsk region,
▫️a temporary deployment area of the AFU in Dobropolye.
🔹 Russian Defence Ministry
'They thought it was theirs'
💬 Warrant officer of an assault company Aleksandr Petrov described the details of liberation of Petrovka in the Donetsk People's Republic. During the assault, the servicemen lured the enemy with Ukrainian speech. The enemy thought that his troops were everywhere, so he got captured and surrendered without a fight.
↗️ Due to a sudden encirclement from all sides, the assault group caught …
❗️The Armed Forces of the Russian Federation continue to launch strikes against the port infrastructure and vessels, used in the interests of the Armed Forces of Ukraine.
Last night, attack unmanned aerial vehicles hit:
▫️a Tarantul-class patrol boat, which ensured safety of vessels during a sea passage and at places of unloading, as well as fuel tanks in the port of Odessa;
▫️a berth terminal, where ships with mi…
🎮 From gamepad to combat drone: how gaming experience helps on front line
💥 The Zapad Group's FPV fighter drones daily destroy dozens of AFU drones, covering our troops.The secret of success lies in unexpected background.
'It's probably because of the fact that I played a lot in computer games that made me learn very quickly. Especially, it was super easy for me to use the joystick,' says the UAV operator with the …
❗️The Armed Forces of the Russian Federation continue to carry out strikes against port infrastructure and naval vessels used in the interests of the Armed Forces of Ukraine.
During the day, strike UAVs hit:
▪️ in Belgorod‑Dnestrovsky (40 km southwest of Odessa) – a production workshop, a depot of warheads and components for uncrewed surface vehicles used to launch attacks on naval vessels and power infrastructure …
👏66👍29🥰18🔥15🤬1
Showing the 12 most recent of 193 posts we hold for @mod_russia_en. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 23,892 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 51 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 16 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Slavyangrad @Slavyangrad · 114,094 Telegram ranks this channel #9 of 81 here — alongside 80 others — read 14 August 2026
Israel Defense Forces @idfofficial · 163,212 Telegram ranks this channel #35 of 81 here — alongside 80 others — read 12 August 2026
Intel Slava @intelslava · 394,872 Telegram ranks this channel #46 of 84 here — alongside 83 others — read 10 August 2026
Geopolitics Prime | Iran & Ukraine News Updates @geopolitics_prime · 295,068 Telegram ranks this channel #47 of 86 here — alongside 85 others — read 10 August 2026
BRICS News @bricsnews · 152,744 Telegram ranks this channel #53 of 84 here — alongside 83 others — read 12 August 2026
Intel Republic @Intel_Republic12 · 99,100 Telegram ranks this channel #57 of 83 here — alongside 82 others — read 15 August 2026
Press TV @presstv · 93,810 Telegram ranks this channel #58 of 81 here — alongside 80 others — read 16 August 2026
DD Geopolitics @DDGeopolitics · 191,414 Telegram ranks this channel #58 of 84 here — alongside 83 others — read 11 August 2026
/CIG/ Telegram | Counter Intelligence Global @CIG_telegram · 116,535 Telegram ranks this channel #60 of 70 here — alongside 69 others — read 14 August 2026
Middle East Spectator — MES @middle_east_spectator · 385,195 Telegram ranks this channel #68 of 84 here — alongside 83 others — read 10 August 2026
Bellum Acta - Intel, Urgent News and Archives ✝️ #FreeVenezuela @BellumActaNews · 115,685 Telegram ranks this channel #69 of 72 here — alongside 71 others — read 14 August 2026
GAZA NOW IN ENGLISH @gazaalanpa · 178,280 Telegram ranks this channel #69 of 72 here — alongside 71 others — read 12 August 2026
Global News Monitor @warmonitors · 155,050 Telegram ranks this channel #79 of 82 here — alongside 81 others — read 12 August 2026
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
2 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
SS-N-26 Strobile(de.wikipedia.org) “…ракеты«Оникс» в рамках спецоперации]''MoD Russia: ''[https://t.me/mod_russia_en/1248 The Russian MoD said it launched Oniks missiles from Bastion…” read 16 August 2026
Eastern front of the Russo-Ukrainian war (2022–present)(en.wikipedia.org) “…Mi-8|Mi-8 helicopter]] in Yakovlivka on 8 December.{{cite news|url=https://t.me/mod_russia_en/5329|work=Russian Ministry of Defense|date=8 December 2022|access-date=11…” read 16 August 2026
Hacker News
This handle was named 2 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 August 2026 — this
entry's latest reading, not the date you are reading this.
“MoD Russia” (@mod_russia_en), 95,391 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/mod_russia_en.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.