Channel
@verumreactor
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,486subscribers
+39 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001454631267 |
|---|---|
| Type | Channel |
| Username | @verumreactor |
| Created | 8 January 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/verumreactor |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 03:17 | 4,486 | +30 |
| 14 Sept 2026, 03:19 | 4,456 | +10 |
| 10 Sept 2026, 08:40 | 4,446 | +3 |
| 5 Sept 2026, 09:36 | 4,443 | +1 |
| 1 Sept 2026, 04:03 | 4,442 | -3 |
| 28 Aug 2026, 22:15 | 4,445 | -3 |
| 25 Aug 2026, 15:29 | 4,448 | +8 |
| 22 Aug 2026, 23:53 | 4,440 | -9 |
| 19 Aug 2026, 05:33 | 4,449 | -2 |
| 16 Aug 2026, 07:54 | 4,451 | +3 |
| 12 Aug 2026, 23:12 | 4,448 | -3 |
| 6 Aug 2026, 14:42 | 4,451 | +4 |
| 6 Aug 2026, 04:03 | 4,447 | no change |
| 6 Aug 2026, 01:17 | 4,447 | first reading |
75 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 6 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 75 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 49 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.
35 reactions across 21 posts, in 6 distinct kinds. The most used accounts for 34.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 12 | 34.3% | |
| 👍 | 8 | 22.9% | |
| ❤ | 7 | 20.0% | |
| 🙏 | 4 | 11.4% | |
| 👏 | 3 | 8.57% | |
| 😢 | 1 | 2.86% |
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 29 of the 75 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 75 most recent posts we hold, published 5 August 2026 to 8 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.
#эксклюзив 📍н.п. Алексеево-Дружковка 🎯 Бойцы Южной группировки войск сжигают НРТК противника, не оставляя шансов на пополнение запасов ⭐️Наш сайт verumreactor ⭐️Мы вКонтакте ⭐️Мы в МАХ ⭐️Наш Дзен⭐️Наш форум
Кадры боевой работы оптоволоконщиков по живой силе ВСУ Фото от @lost_armour
Видеообращение адресовано военнослужащим 425-го отдельного штурмового полка «Скала». Вы разбиты, деморализованы. Ваши жизни – давно уже просто цифры в отчётах командира. Пока вас мешают с землёй на позициях, в штабе готовят телеграммы для ваших родных. Бросайте позиции и сдавайтесь в плен. Сохраните свои жизни.
Расчёты БПЛА Южной группировки войск уничтожили боевиков ВСУ Южный рубеж
👍1
Кадры со стороны врага. Обстановка на дороге с Краматорска на Алексеево-Дружковку @voenacher
👍2
Славянск под постоянным давлением. Южная группировка сжимает кольцо ➖ На Славянском направлении российские подразделения продолжают активные действия. Штурмовые группы работают в районах Закитного, Кривой Луки, Ризниковки и в направлении Николаевки и Рай-Александровки. Николаевка остаётся ключевым "восточным воротами" к городу - именно здесь сейчас идут самые жёсткие бои. ➖ Южная группировка войск вместе с соседними …
#эксклюзив 📍н.п. Краматорск 🎯 Бойцы Южной группировки войск уничтожили антенну, обеспечивающую сигнал для FPV дронов противника ⭐️Наш сайт verumreactor ⭐️Мы вКонтакте ⭐️Мы в МАХ ⭐️Наш Дзен⭐️Наш форум
Красиво танк горит - задача выполнена! @gorb_squad
Воздушные бои все сильнее набирают обороты. Парни десятками в день крошат тяжелые дроны противника спасая жизни наших парней и обрубая логистику. Работаем! @crewruss1a
Последствия ночного удара по автомобильному мосту через реку Торец в Славянске, в районе «Химпрома». Кадры со стороны противника. @voenkorKotenok
Кадры уничтожения пунктов управления БпЛА ВСУ в районе Алексеево-Дружковки расчётами ударных дронов Южной группировки войск Укрытия, из которых работали расчёты беспилотных летательных аппаратов украинских боевиков были выявлены по взлётам и посадкам квадрокоптеров противника. По местам укрытий и пунктов управления беспилотников ВСУ успешно отработали расчёты БпЛА. @RtrDonetsk
⚡️ Трамп фактически подтвердил: ракет для систем Patriot Киев не получит. Журналист попытался надавить на жалость: «Зеленский говорит, что его стране срочно нужны ракеты». Американский президент осадил сразу: «Нам они тоже нужны». И припомнил, как администрация Байдена спустила на Украину боеприпасов на 300 миллиардов долларов, практически опустошив склады США. 🤡 Пока Зеленский продолжает разъезжать по миру с протян…
Showing the 12 most recent of 75 posts we hold for @verumreactor. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 8 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.
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.
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.
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“verumreactor” (@verumreactor), 4,486 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/verumreactor.
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.