Telegram RegisterThe public register of Telegram
Telegram profile photo for Ратное Дело

Channel

Ратное Дело

@ratnoe_delo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

23,908subscribers

+219 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001186590094
TypeChannel
Username@ratnoe_delo
Created22 July 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ratnoe_delo

Topic

Other / unclassifiable — 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 93% 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

23,68923,95423,821.56 August 2026 — 23,689 subscribers6 August 2026 — 23,693 subscribers7 August 2026 — 23,691 subscribers8 August 2026 — 23,696 subscribers9 August 2026 — 23,700 subscribers10 August 2026 — 23,699 subscribers12 August 2026 — 23,704 subscribers13 August 2026 — 23,725 subscribers14 August 2026 — 23,744 subscribers16 August 2026 — 23,754 subscribers17 August 2026 — 23,767 subscribers18 August 2026 — 23,771 subscribers19 August 2026 — 23,779 subscribers20 August 2026 — 23,825 subscribers21 August 2026 — 23,832 subscribers23 August 2026 — 23,877 subscribers24 August 2026 — 23,902 subscribers25 August 2026 — 23,908 subscribers26 August 2026 — 23,909 subscribers27 August 2026 — 23,947 subscribers28 August 2026 — 23,950 subscribers29 August 2026 — 23,951 subscribers30 August 2026 — 23,954 subscribers1 September 2026 — 23,947 subscribers4 September 2026 — 23,946 subscribers7 September 2026 — 23,939 subscribers10 September 2026 — 23,927 subscribers12 September 2026 — 23,924 subscribers14 September 2026 — 23,926 subscribers16 September 2026 — 23,912 subscribers18 September 2026 — 23,908 subscribers23,9086 August 202618 September 2026
31 measurements spanning 43 days, net +219. 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 23,649–23,994 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
18 Sept 2026, 05:5723,908-4
16 Sept 2026, 02:0023,912-14
14 Sept 2026, 08:1523,926+2
12 Sept 2026, 20:0023,924-3
10 Sept 2026, 17:5723,927-12
7 Sept 2026, 13:3623,939-7
4 Sept 2026, 18:1423,946-1
1 Sept 2026, 01:1823,947-7
30 Aug 2026, 21:5723,954+3
29 Aug 2026, 20:0523,951+1
28 Aug 2026, 18:4623,950+3
27 Aug 2026, 19:1823,947+38
26 Aug 2026, 20:0423,909+1
25 Aug 2026, 17:1723,908+6
24 Aug 2026, 18:5423,902+25
23 Aug 2026, 03:4823,877+45
21 Aug 2026, 13:1623,832+7
20 Aug 2026, 15:2223,825+46
19 Aug 2026, 16:1223,779+8
18 Aug 2026, 14:1423,771first reading

Engagement

10 posts held, back to 21 May 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
12.4%
avg views ÷ 23,908 subscribers
Avg views / post
2,970
2 posts measured
Reaction rate
1.45%
reactions ÷ views · ER floor
Posts in window
2
of 10 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
WindowRolling 30 days · latest post in window 2 September 2026
Posts held10 (21 May 2026 – 2 September 2026)
Views total5,930
Reactions total86
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:53 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
20m 17s
Average length
10m 09s

Measured directly from 2 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

755 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 42.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍31942.3%
🔥20827.5%
💯10513.9%
custom 5321295532910475078567.42%
custom 5391148868127717336486.36%
custom 5321323798090251837192.52%

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 are Telegram’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 9 of the 10 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 755 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 21 May 2026 to 2 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.

Recent posts

2 Sept 2026, 15:55 UTC≈2,000 views17 reactionsread 3 September 2026
Forwarded from @GTO_Klin_BazaPhoto

ВНИМАНИЕ, ДРОНЫ! Бойцы, здравия желаю! Начинаем набор на курс «Дробовик-Антидрон» - 05-06 сентября 2026 г. Для тех, кто уже был на двухдневном курсе, разрешается приехать на второй день 06 сентября, сразу на стрельбище в воскресение. За два дня постараемся наработать навык ближней противодроновой обороны с использованием гладкоствольного оружия. Работа по подвижным мишеням, тактика, безопасность. 🔥 Работа на резу…

👍14🔥3

31 Aug 2026, 20:12 UTC≈3,930 views69 reactionsread 3 September 2026
Video

Защита от тепловизора - Термокамуфляж «Мимик»

👍45custom 539114886812771733622💯2

12 Aug 2026, 11:31 UTC≈23,600 views92 reactionsread 3 September 2026
Photo

Товарищи! Просьба к вам привести примеры попадания различных боеприпасов в защитную толщу (блиндажа или др. сооружения). Надо, чтобы достоверно был известен 1) тип БП (например, мина миномётная ОФ, 120 мм, заряд ВВ ... кг, или снаряд ОФ, 155/152 мм, нато/наш, СВУ 10 кг ТНТ, или ТМ-62 и т.д.); 2) размеры повреждения (глубина, диаметр воронки, разрушен только первый накат и т.п., можно своими словами); 3) конструктив з…

👍66🔥26

25 Jul 2026, 09:02 UTC≈10,500 views102 reactionsread 3 September 2026
Photo

Всем привет. Что то активизировались звонки с предложением на контракты, хуже спамеров, каждый день 2-3 звонка, говоришь им что и так служишь и хоть бы что. Крайние разы говорю да интересовался и они сбрасывают. Вам как часто поступают такие звонки? P.S. фото для красоты, это один из комплектов минирование для задачи минирования маршрута проезда техники.

custom 532129553291047507850🔥33👍19

16 Jul 2026, 07:36 UTC≈10,800 views72 reactionsread 3 September 2026
Forwarded from @GTO_Klin_BazaVideo

11 июля на Базе НВП «ГТО‑Клин» встретились 8 команд из разных округов Подмосковья и доказали, что упорные тренировки, сплочённость и настоящая командная работа творят чудеса! Члены Клинского отделения Ассоциации ветеранов СВО Московской области совместно с Клинским отделением «Союза десантников» при поддержке администрации округа провели военно-патриотическую игру «Зарница-2026». Военно-патриотические клубы МО бороли…

👍72

3 Jul 2026, 02:23 UTC≈11,800 views130 reactionsread 3 September 2026
Photo

Я просто оставлю это здесь, на память. Может быть будем вспоминать с улыбкой, стоя у самовара с сырой нефтью) P.S это Сибирь)

💯93custom 532132379809025183717🔥12custom 53212955329104750786custom 53911488681277173362

29 Jun 2026, 10:39 UTC≈35,200 views64 reactionsread 3 September 2026
Photo

💥Анонс курсов на Июль- Август- Сентябрь💥 🗓 Июль 13-19 Сапер Разведчик 🗓 Июль 20-26 ИРГ и ПОЗ 🗓 Август 1-2 Базовый курс 🗓 Сентябрь 7-13 Сапер Разведчик 🗓 Сентябрь 14-20 ИРГ и ПОЗ Недельный курс Сапер Разведчик Описание курса и как записаться по ссылке ниже ⬇️ https://telegra.ph/Sapyor-Razvedchik-09-22 Базовый Курс по Инженерной Подготовке - 2 дня. Описание курса и как записаться по ссылке ниже ⬇️ https://telegra.ph…

🔥48custom 539114886812771733610👍6

19 Jun 2026, 19:57 UTC≈13,000 views54 reactionsread 3 September 2026
Forwarded from @GTO_Klin_BazaPhoto

ВНИМАНИЕ, ДРОНЫ! Бойцы, здравия желаю! Начинаем набор на курс «Дробовик-Антидрон» - 27 - 28 июня 2026 г. Для тех, кто уже был на двухдневном курсе, разрешается приехать на второй день 28 июня, сразу на стрельбище в воскресение. За два дня постараемся наработать навык ближней противодроновой обороны с использованием гладкоствольного оружия. Работа по подвижным мишеням, тактика, безопасность. 🔥 Работа на результат.…

👍38custom 539114886812771733610🔥6

21 May 2026, 17:13 UTC≈14,000 views155 reactionsread 3 September 2026
Photo

Друзья, немного интересного для вас. На данный момент мы заняты разработкой нового концепта эшелонированного снаряжения для сапёров разведчиков и командиров ИРГ и не только. В концепции присутствует несколько вариантов снаряжения. 1- Сапёр разведчик, концепция минимизация снаряжения, размещение инструмента и расходников в быстром доступе на 1 эшелоне снаряжения, в штатных габаритах подсумков 2 ак. 2- Сапёр, данная…

🔥80👍59💯10custom 53911488681277173364custom 53213237980902518372

Showing the 10 most recent of 10 posts we hold for @ratnoe_delo. 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.

Forward network

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.

Mentions

Named by 5 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.

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.

Одна нога здесь, другая там!
@combat_engineer · 92,515
#1
Видео архив Ратное Дело
@Video_Ratnoe_Delo · 1,671
#2
«Инженеры ЧФ»
@inzheneryChF · 20,264
#3
NerV⚡️⚡️⚡️
@KaskadNerv · 28,118
#4
Fighterbomber
@bomber_fighter · 527,852
#5
Крупнокалиберный Переполох
@bolshiepushki · 325,501
#6
Старше Эдды
@vysokygovorit · 488,324
#7
Разработчик БПЛА
@UAVDEV · 123,630
#8
Говорит ТопаZ 🪖
@Love_Russia_Beauty · 115,716
#9
Белорусский силовик
@belarusian_silovik · 453,479
#10
Кирилл Фёдоров / Война История Оружие
@warhistoryalconafter · 481,589
#11
FRONT SIDE OF THE MEDAL
@rsotmvideo · 93,418
#12
Colonelcassad
@boris_rozhin · 747,495
#13
Повёрнутые на войне 🇷🇺
@voenacher · 664,441
#14
Военная библиотека 📚
@VBiblioteka · 23,305
#15
ХИЛЕР l HEALER
@HealerTacMed · 131,502
#16
Dez_informator
@dez_informator · 12,546
#17
Месть доброй воли
@Mestb_Dobroj_Voli · 101,212
#18
Лесной
@lesnoy16 · 3,635
#19
ТРОЙКА 🏴‍☠️
@rustroyka1945 · 190,364
#20
ПТСР TEAM Community
@ptsr_team · 38,159
#21
СОЛДАТ УДАЧИ
@Soldieroffortune777 · 124,825
#22
Репортер Filatov
@filatovcorr · 168,413
#23
БП (Боевая Подготовка) СпН, Разведка, ВДВ, ...
@combattraining365 · 29,098
#24
Наука побеждать
@naukapobezhdatZ · 51,682
#25
Военный Осведомитель
@milinfolive · 615,738
#26
Смертельный номер 👉👈
@smertnomr · 12,828
#27
Yujin_Mamedof Official 😶‍🌫🥵🫥☠😺🦿👣🪖🐀
@yujin_mamedov · 3,919
#28
Tynu40k Goblina (oper.ru)
@oper_goblin · 494,224
#29
Юрий Евич | "Юрич"
@russkiysoldatYurich · 35,388
#30
FPV_выZOV🇷🇺
@FPV_vyZOV · 67,842
#31
Хроника оператора БпЛА | БВС, БЛА
@xronikabpla · 55,183
#32
SimpDungeon☠️
@grpzdc · 166,370
#33
Техник БПЛА🇷🇺
@texotdelBPLA · 23,524
#34
Владлен Татарский
@vladlentatarsky · 174,452
#35
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 276,927
#36
Мёртвые головы
@Dead_heads · 33,616
#37
Lobaev Z
@lobaev_vlad · 73,177
#38
Диванный спецнаZ
@divannyi_special · 5,863
#39
Учебка ТСП
@UchebkaSpN · 8,477
#40
Опасный Бизнес
@OpasniyBiznes · 97,051
#41
WarGonzo
@wargonzo · 745,026
#42
Русский инженер
@rusengineer · 124,401
#43
АРХАНГЕЛ СПЕЦНАЗА
@arx_spn · 1,020,241
#44
Канал специального назначения
@okspn · 130,747
#45
Тактика и специальная подготовка
@tactical_z · 65,983
#46
Курс огневой подготовки
@firearms_edu · 16,195
#47
ПАРТИЗАН
@ruspartizan · 7,857
#48
W. M. P.
@warmempolit · 33,977
#49
Тринадцатый.
@Z13_Separ · 212,772
#50
Vlad_Hurrygun
@hurrygun_tacmed · 15,733
#51
ПИСАРЬ ИЗ СПЕЦНАZА
@specnaz_com · 27,567
#52
Кум вещает
@pmcum · 3,885
#53
Hard Blog
@Hard_Blog_Line · 83,635
#54
Воевода Вещает
@ZOV_Voevoda · 168,954
#55
Дневник связиста Кибы📡💤
@signalman_diary · 19,135
#56
Неофициальный Безсонов
@NeoficialniyBeZsonoV · 244,779
#57
Секретариат Двух майоров
@DvaMayoraSekretka · 45,709
#58
Д///ИХАД
@tvjihad · 123,565
#59
Milgear & Phantom group
@phantommilgeargroup · 6,379
#60
УЦТМ. Первая помощь и тактическая медицина.
@uctm_official · 32,678
#61
Белые дяди в Африке🌴
@wagner_group2022 · 122,616
#62
Arm.Taktik27
@Arm_taktik27 · 33,893
#63

Read from Telegram’s recommendation API, most recently 17 September 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.

FRONT SIDE OF THE MEDAL
@rsotmvideo · 93,418
Telegram ranks this channel #38 of 66 here — alongside 65 others — read 16 September 2026
Военная библиотека 📚
@VBiblioteka · 23,305
Telegram ranks this channel #42 of 67 here — alongside 66 others — read 18 September 2026
Рустам Ковальски и Kowalski team
@kowalski_team · 23,447
Telegram ranks this channel #45 of 53 here — alongside 52 others — read 18 September 2026
Unfair Advantage
@unfair_advantage_tg · 24,550
Telegram ranks this channel #52 of 58 here — alongside 57 others — read 16 September 2026
Технологии выживания - Тактическая медицина
@tvtacticalmed · 23,116
Telegram ranks this channel #63 of 68 here — alongside 67 others — read 19 September 2026
Институт СВО / ЦСН "БАРС-САРМАТ"
@svo_institute · 21,204
Telegram ranks this channel #70 of 72 here — alongside 71 others — read 24 September 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Ратное Дело” (@ratnoe_delo), 23,908 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ratnoe_delo.

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.