International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 44% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
34 measurements spanning 43 days, net +1,671. 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 19,751–21,987 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
17 Sept 2026, 13:56
21,684
-8
15 Sept 2026, 11:41
21,692
+301
13 Sept 2026, 17:55
21,391
-38
11 Sept 2026, 21:58
21,429
-37
9 Sept 2026, 13:00
21,466
-263
6 Sept 2026, 04:00
21,729
+203
3 Sept 2026, 21:41
21,526
+28
2 Sept 2026, 11:24
21,498
+76
1 Sept 2026, 14:18
21,422
+140
31 Aug 2026, 12:16
21,282
+182
30 Aug 2026, 12:46
21,100
+191
29 Aug 2026, 09:53
20,909
+152
28 Aug 2026, 11:25
20,757
+124
27 Aug 2026, 08:12
20,633
-228
26 Aug 2026, 07:27
20,861
+280
25 Aug 2026, 05:05
20,581
+123
24 Aug 2026, 04:04
20,458
+174
22 Aug 2026, 12:07
20,284
+131
20 Aug 2026, 23:56
20,153
-249
20 Aug 2026, 00:28
20,402
first reading
Engagement
232 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 58 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
36.2%
avg views ÷ 21,684 subscribers
Avg views / post
7,850
101 posts measured
Reaction rate
3.09%
reactions ÷ views · ER floor
Posts in window
102
of 232 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 3 September 2026
Posts held
232 (5 August 2026 – 3 September 2026)
Views total
792,870
Reactions total
24,511
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 15:30 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
59m 48s
Average length
47s
Measured directly from 77 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
55,585 reactions across 224 posts, in 38 distinct kinds. The most used accounts for 25.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
14,407
25.9%
❤
7,342
13.2%
🤬
6,803
12.2%
😁
5,329
9.59%
🤣
4,666
8.39%
👍
3,778
6.80%
💯
3,176
5.71%
🤡
1,837
3.30%
😢
1,411
2.54%
🤔
1,204
2.17%
🙏
1,196
2.15%
🤯
773
1.39%
💔
575
1.03%
🫡
544
0.979%
😡
476
0.856%
👏
447
0.804%
😭
285
0.513%
🥰
285
0.513%
🎉
263
0.473%
👀
163
0.293%
18 further kinds
625
1.12%
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 231 of the 232 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 57,154 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 232 most recent posts we hold, published 5 August 2026 to 3 September 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.
🇺🇦 На Куп'янському напрямку маємо ще +4 км² звільненої української землі
Бійці 23-го штурмового полку Р.У.Г 2-го корпусу НГУ «Хартія» продовжують рухатися вперед – цього разу зачистили нові ділянки між Дворічною та Западним.
Раніше тут уже вдалося звільнити 9,5 км², а тепер загальний результат зріс до 13,5 км².
На одній із ділянок бійці Р.У.Г працювали разом із 35-ю окремою бригадою морської піхоти.
Чудова операц…
Заступник командира РДК Каплунов оприлюднив відеозвернення, - РБК-Україна
В ньому він заявив, що був "викрадений співробітниками СБУ" 23 серпня. Каплунов стверджує, що за його інформацією, перші 3 доби з ним "безпосередньо працював генерал Поклад (очільник СБУ - ред.) шляхом психологічного та фізичного тиску". Він стверджує, що СБУ намагалася дискредитувати заступника спецпідрозділу "Тимура" Дмитра Іванова та безпос…
У Сочі сьогодні відпрацювали БЕКи ВМС України по судну забезпечення рф NEFRIT
Це елемент російської морської та енергетичної інфраструктури, який забезпечував нафтогазові операції, обслуговував офшорні об’єкти, перевозив вантажі й персонал та виконував підводно-технічні роботи.
Голос Майора ✙
Тепер до хороших новин.
Командира 22-ї важкої бомбардувальної авіаційної дивізії дальньої авіації ВКС рф генерал-майор Варпахович Микола Миколайович було підстрелено
Зараз він госпіталізований у важкому стані.
Він причетний до військових злочинів проти цивільних в Україні. Зокрема він відповідальний за ракетний удар по Умані 28 квітня 2023 року, що вбив 24 людини.
Також підпорядковані йому сили скоїли масований р…
Адвокат Степана Каплунова Тарас Боровський прокоментував опубліковані СБУ матеріали
За його словами, відео із Каплуновим було записане під тиском, погрозами та після майже 10 днів утримання із заклеєними очима й у кайданках.
Щодо опублікованих скриншотів листування Боровський заявив, що невідомо, з якого саме телефона вони зроблені, а телефоном Каплунова під час його утримання, за словами адвоката, заволоділи співр…
Отже, що ми маємо станом на зараз по історії з СБУ та ГУР
СБУ та Степан Каплунов фактично підтверджують головне – його перевіряли через можливі зв'язки з ФСБ. Але далі версії суттєво розходяться.
😎 СБУ заявляє, що Каплунов контактував із російськими спецслужбами та отримав завдання підготувати замах на одного з лідерів російського опозиційного руху, а також ліквідацію інших українських військових за гроші. За версі…
🔴 Запрошуємо до перегляду нового випуску
Вибори на ТОТ стартували, вже проголосували тисячі окупантів. Гауляйтери Сальдо, Пушилін і Балицький в прольоті. Чому в Донецьк завели кандидатів з Москви?
Чому для путіна вибори на окупованих територіях – ключовий момент?
Керівник Центру вивчення окупації Петро Андрющенко в інтерв'ю Андрію Ткачуку розповів, що мобілізаця в росії вже почалась завдяки хитрому маневру Кремля.…
Щодо сьогоднішньої абсолютно ганебної ситуації між окремими підрозділами СБУ та ГУР, яка сталася в Києві: має бути відповідальність, в тому числі кадрові рішення керівників спецслужб щодо учасників того, що сталося, та мають бути внутрішні розслідування в обох службах, — Зеленський.
Генеральний прокурор і Державне бюро розслідувань зʼясують всі деталі: будуть перевірені всі свідчення та заяви учасників цієї історії,…
💯79❤28🤔14😁13🤡5🙏2
Showing the 12 most recent of 232 posts we hold for @voice_of_major. 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.
Posts edited after publishing
@voice_of_major edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
29 August 2026
Most recent edit
2 September 2026
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 232 most recent posts we hold, published 5 August 2026 to 3 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 22 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.
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.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Голос Майора ✙” (@voice_of_major), 21,684 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/voice_of_major.
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.