3 measurements spanning 7 days, net +2. 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 579–581 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 02:17
581
+2
6 Aug 2026, 18:03
579
no change
6 Aug 2026, 07:06
579
first reading
Engagement
7 posts held, back to 26 January 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
308.1%
avg views ÷ 581 subscribers
Avg views / post
1,790
1 post measured
Reaction rate
2.46%
reactions ÷ views · ER floor
Posts in window
1
of 7 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 2 August 2026
Posts held
7 (26 January 2026 – 2 August 2026)
Views total
1,790
Reactions total
44
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 18:03 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.
Reaction mix
357 reactions across 7 posts, in 13 distinct kinds. The most used accounts for 18.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
65
18.2%
custom 5290006180763016612
57
16.0%
❤
57
16.0%
custom 5433865002240975895
55
15.4%
custom 5431803529608048331
46
12.9%
👍
34
9.52%
🫡
26
7.28%
👏
7
1.96%
👌
3
0.84%
🤝
3
0.84%
😭
2
0.56%
🌚
1
0.28%
🦄
1
0.28%
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 7 of the 7 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 357reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 26 January 2026 to 2 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.
Telegram Stars
Stars received
2
across the posts below
Posts paid on
2
of 7 we hold a reading for · 29%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Minamet_Terrora. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 7 most recent posts we hold for this entry, published 26 January 2026 to 2 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Вытрымка — вызначальная рыса для гор. А калі гэта ўкраінскія Карпаты, то велічныя краявіды застаюцца ў памяці назаўжды.
ГЦУ „Тэрор“ здзейсніла трохдзённы марш-кідок горнымі маршрутамі. Першыя двое сутак каманда ішла пад дажджом і пранізлівым ветрам, які прабіраў да самых костак. На трэці ж дзень горы сустрэлі спекай.
Але нішто не здольна зацьміць прыгажосць Карпат. Для беларускіх дабраахвотнікаў украінскія горы ўжо…
Вайна дыктуе свае правілы. Мы, як і багата іншых спецыялістаў, адаптуемся да яе рэалій. Немагчыма паспяхова апераваць на тэатры ваенных дзей, калі ты абмежаны ў сродках і, тым болей, навыках. Разнапланавасць у задачах: выведка, лагістыка і, вядома ж, „ударка“ — забралі на сябе БПЛА.
Яшчэ ўзімку большасць нашага калектыву прайшла навучанне на кіраванне ўдарнымі дронамі. А ўжо пачынаючы з вясны, мы выконваем баявыя за…
Падчас адваёвы акупаваных підарамі тэрыторыяў, нашая шляхта атрымала раненьні рознай ступені цяжкасьці. Вы можаце падтрымаць цяжка параненых беларусаў сваім данатам. З вашай падтрымкай хлопцы хутчэй адновяцца й вернуцца да выкананьня задачаў па зьнішчэньні маскоўскіх акупантаў.
https://send.monobank.ua/jar/6UsCsbuDXM
ДАЛУЧАЙСЯ | ПАДТРЫМАЙ
Instagram | YouTube
Telegram | LinkedIn
Bluesky | Threads
Праца гранатамётніка ў сучасных баявых дзеяньнях не губляе актуальнасьці, калі ўлічваць рэаліі і дастасоўваць іх да сыстэмы падрыхтоўкі.
Кадры трэнаваньня гранатамётнай справы БДК у складзе батальёну «Hatred».
ДАЛУЧАЙСЯ | ПАДТРЫМАЙ
Instagram | YouTube
Telegram | LinkedIn
Bluesky | Threads
⚡️Підрозділи ГУР у взаємодії з Силами оборони України зупинили наступ ворога на Запоріжжя у своїй смузі відповідальності
Упродовж трьох місяців воїни “Спецпідрозділу Тимура” ГУР МО України реалізовують комплексну оборонну операцію на Запорізькому напрямку.
Ціль розвідників – зірвати наступальні плани ворога та не допустити його просування до обласного центру.
⚔️В ході активних дій спецпризначенці ГУР ліквідували п…
У Кіеві цэнтральнымі вуліцамі прайшоў марш памяці Міхася Жызнеўскага ды ўсіх загінулых за Ўкраіну беларусаў.
Гэты марш адбываецца штогод. Сёлета удзел у ім прыйнялі мы — Беларускі Дабраахвотніцкі Корпус. Нажаль, не ўсе змаглі аддаць пашану беларускім героям, бо значная частка БДК знаходзіцца на баявой рабоце, дзе працягвае справу, якую распачалі нашыя загінулыя пабрацімы.
Нагадаем, што Міхась Жызнеўскі загінуў 22 с…
Футболка «БДК»
Кошт: 1300 грн
Для ўладальнікаў УБД / вайсковага білета: 1000 грн
Колеры: чырвоны, чорны, каёт Шаўкатрафарэтны друк, вольны крой, 100% бавоўна
Памеры: S, M, L, XL, XXL
Набываючы гэтую футболку, вы падтрымліваеце беларускіх дабраахвотнікаў і дапамагаеце нам закрываць баявыя патрэбы.
Замовіць.
БДК | ДАЛУЧАЙСЯ | ПАДТРЫМАЙ
Showing the 7 most recent of 7 posts we hold for @Minamet_Terrora. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 341,690 of 1,176,251entries 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
Names
Channels on the register whose handles appear in this channel's posts.
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.
Cite this entry
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“ГЦУ "ТЭРОР"” (@Minamet_Terrora), 581 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Minamet_Terrora.
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.
