Telegram RegisterThe public register of Telegram
Telegram profile photo for RUSVARG

Channel

RUSVARG

@rusvarg

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

38,502subscribers

-732 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001769400021
TypeChannel
Username@rusvarg
Created22 July 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live25 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 25 October 2026
On Telegramt.me/rusvarg

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 70% 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

38,50239,23438,8685 August 2026 — 39,234 subscribers6 August 2026 — 39,234 subscribers7 August 2026 — 39,231 subscribers7 August 2026 — 39,222 subscribers8 August 2026 — 39,213 subscribers9 August 2026 — 39,201 subscribers11 August 2026 — 39,206 subscribers12 August 2026 — 39,201 subscribers13 August 2026 — 39,094 subscribers14 August 2026 — 39,084 subscribers15 August 2026 — 39,083 subscribers17 August 2026 — 39,075 subscribers18 August 2026 — 39,063 subscribers19 August 2026 — 39,058 subscribers20 August 2026 — 39,053 subscribers21 August 2026 — 39,037 subscribers22 August 2026 — 39,066 subscribers24 August 2026 — 39,050 subscribers26 August 2026 — 39,024 subscribers27 August 2026 — 39,010 subscribers28 August 2026 — 39,039 subscribers29 August 2026 — 39,030 subscribers30 August 2026 — 39,008 subscribers31 August 2026 — 38,988 subscribers1 September 2026 — 38,975 subscribers2 September 2026 — 38,966 subscribers4 September 2026 — 38,952 subscribers6 September 2026 — 38,928 subscribers9 September 2026 — 38,898 subscribers12 September 2026 — 38,866 subscribers13 September 2026 — 38,876 subscribers15 September 2026 — 38,868 subscribers17 September 2026 — 38,843 subscribers26 September 2026 — 38,763 subscribers4 October 2026 — 38,684 subscribers8 October 2026 — 38,642 subscribers13 October 2026 — 38,611 subscribers14 October 2026 — 38,601 subscribers15 October 2026 — 38,603 subscribers16 October 2026 — 38,598 subscribers17 October 2026 — 38,584 subscribers18 October 2026 — 38,573 subscribers19 October 2026 — 38,565 subscribers20 October 2026 — 38,559 subscribers21 October 2026 — 38,542 subscribers22 October 2026 — 38,530 subscribers24 October 2026 — 38,518 subscribers25 October 2026 — 38,502 subscribers5 August 202625 October 2026
48 measurements spanning 80 days, net -732. 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 38,392–39,344 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
25 Oct 2026, 03:3738,502-16
24 Oct 2026, 00:0538,518-12
22 Oct 2026, 21:5638,530-12
21 Oct 2026, 21:1038,542-17
20 Oct 2026, 17:3838,559-6
19 Oct 2026, 17:1738,565-8
18 Oct 2026, 19:1138,573-11
17 Oct 2026, 18:0938,584-14
16 Oct 2026, 17:2038,598-5
15 Oct 2026, 15:0938,603+2
14 Oct 2026, 16:2838,601-10
13 Oct 2026, 06:0938,611-31
8 Oct 2026, 21:4038,642-42
4 Oct 2026, 14:1738,684-79
26 Sept 2026, 09:2138,763-80
17 Sept 2026, 13:5738,843-25
15 Sept 2026, 15:5538,868-8
13 Sept 2026, 22:3638,876+10
12 Sept 2026, 02:1638,866-32
9 Sept 2026, 14:3638,898first reading

Engagement

98 posts held, back to 3 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 147 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.3%
avg views ÷ 38,502 subscribers
Avg views / post
4,360
38 posts measured
Reaction rate
1.84%
reactions ÷ views · ER floor
Posts in window
39
of 98 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 21 October 2026
Posts held98 (3 August 2026 – 21 October 2026)
Views total165,500
Reactions total3,038
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Oct 2026, 19:52 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
22m 55s
Average length
57s

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

7,917 reactions across 95 posts, in 10 distinct kinds. The most used accounts for 17.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,40417.7%
🙏1,07213.5%
🔥1,04013.1%
🤬1,02412.9%
🫡95212.0%
❤94712.0%
😁91511.6%
🤔2773.50%
👎1541.95%
😢1321.67%

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 96 of the 98 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 7,986 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 98 most recent posts we hold, published 3 August 2026 to 21 October 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

21 Oct 2026, 12:27 UTC≈3,050 views123 reactionsread 24 October 2026

❗️Самолёт Су-30 упал в Калининградской области при выполнении учебно-тренировочного полёта — Минобороны РФ Экипаж катапультировался, угрозы жизни лётчиков нет. Самолёт упал в безлюдном районе, полёт выполнялся без боекомплекта. @rusvarg

🙏100🤬10🔥5😢5😁3

19 Oct 2026, 19:41 UTC≈3,830 views72 reactionsread 24 October 2026

❗️Мы дали Украине многое. Они не дали нам ничего. Запомните это — Трамп @rusvarg

👍41😁22🫡5🔥4

19 Oct 2026, 19:34 UTC≈3,830 views62 reactionsread 24 October 2026

⚡️Настало время кому-то другому вести переговоры от имени Украины — Трамп @rusvarg

😁53🔥9

19 Oct 2026, 19:34 UTC≈3,620 views42 reactionsread 24 October 2026

⚡️Трамп анонсировал трёхстороннюю встречу с Путиным и Си Цзиньпином @rusvarg

🔥23🤔12😁7

19 Oct 2026, 16:00 UTC≈5,020 views106 reactionsread 24 October 2026
Photo

Военнослужащие различных подразделений в зоне СВО @rusvarg

❤46🔥26🙏20🫡14

19 Oct 2026, 14:50 UTC≈3,030 views53 reactionsread 24 October 2026
Forwarded from @SCSFB1Video

☀️Работа сводной РГ 417 ОРБ и группы Киллы в составе 1-й ОКэжБрСпН по зачистке ОП и ликвидации л/с противника в направлении Орехова. В ходе разведки боем выявлен ОП противника. Стремительным и слаженным передвижением группа максимально сблизилась с оппонентом и очень быстро стрелковым огнем и гранатами разведчики ликвидировали 2 ВСУшников на месте. Остальные силы противника оставили свои позиции и обратились в бегст…

👍29🫡20🔥3❤1

19 Oct 2026, 11:48 UTC≈3,060 views165 reactionsread 24 October 2026
Forwarded from @militaristrussian67Photo

В Пхеньяне открыли музей, посвящённый участию корейских военнослужащих в боях на Курском направлении. В центре экспозиции — стела с 2288 звёздами: столько бойцов погибли из 10-тысячного контингента КНДР. 271 военнослужащему присвоили звание Героя КНДР, а рядом создали мемориальное кладбище. В залах представлены фотографии, личные вещи, оружие и диорамы боёв, а в парке трофеев — бронетехника и вооружение ВСУ и стран…

🫡98❤43🔥18👍4🙏2

17 Oct 2026, 16:58 UTC≈3,840 views106 reactionsread 24 October 2026

⚡️В России предложили разрешить перенос дата-центров за границу на фоне атак беспилотников, — СМИ. Ассоциация компаний интернет-торговли направила премьер-министру Мишустину предложение о поддержке бизнеса, пострадавшего от атак БПЛА. Инициатива предусматривает введение специального правового режима, который позволит компаниям временно размещать критически важные системы в зарубежных резервных дата-центрах, если во…

😁56🤔26👎21❤2🔥1

17 Oct 2026, 12:40 UTC≈3,920 views45 reactionsread 24 October 2026

Вашингтон пытается организовать встречу Путина, Трампа и Зеленского в ОАЭ, Саудовской Аравии или США — Зеленский @rusvarg

👎33🤔10😁2

16 Oct 2026, 05:57 UTC≈4,780 views58 reactionsread 24 October 2026

Снова воздушные заявления? Трамп: — Договариваться с Путиным легче. Завершение войны произойдёт без участия президента Украины. Зеленский — не тот человек, с которым стоит иметь дело; — Зеленский говорит, что хочет договориться, но на самом деле не хочет. @rusvarg

😁47👍9❤2

14 Oct 2026, 18:51 UTC≈5,130 views48 reactionsread 24 October 2026
Forwarded from @infomil_liveVideo

Тем временем, по поступающей информации неопознанным лицом были ликвидированы 5 военнослужащих из 72-й ОМБр ВСУ в н.п. Кутузовка Харьковской области. Неизвестный, сперва расстрелял одного военнослужащего на улице у входа в дом, а затем продолжил стрельбу уже непосредственно в доме. После, неизвестный скрылся с места событий и до сих пор разыскивается. Украинские ресурсы уже запустили в эфир историю про сбежавшего …

👍27🔥10❤7🤔2🫡2

14 Oct 2026, 16:18 UTC≈4,300 views50 reactionsread 24 October 2026

❗️Директор ФБР прибыл в Россию на переговоры — СМИ @rusvarg

🤔40👎9😁1

Showing the 12 most recent of 98 posts we hold for @rusvarg. 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

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 30 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.

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.

Два майора
@dva_majors · 1,164,701
#1
АРХАНГЕЛ СПЕЦНАЗА
@arx_spn · 1,021,390
#2
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 274,697
#3
ТРОЙКА 🏴‍☠️
@rustroyka1945 · 189,166
#4
Повёрнутые на войне 🇷🇺
@voenacher · 660,408
#5
Ловец Человеков | Елена Залесская
@iamhumancatcher · 120,969
#6
Colonelcassad
@boris_rozhin · 754,676
#7
Кирилл Фёдоров / Война История Оружие
@warhistoryalconafter · 480,201
#8
Говорит ТопаZ 🪖
@Love_Russia_Beauty · 115,200
#9
Неофициальный Безсонов
@NeoficialniyBeZsonoV · 242,839
#10
Месть доброй воли
@Mestb_Dobroj_Voli · 100,413
#11
Операция Z: Военкоры Русской Весны
@rvvoenkor · 1,462,509
#12
Военный Осведомитель
@milinfolive · 615,815
#13
Крупнокалиберный Переполох
@bolshiepushki · 323,799
#14
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,673,006
#15
🇷🇺 DONTSTOPWAR
@dontstopwar · 252,546
#16
Сладков+
@sladkov_plus · 697,427
#17
Раньше всех. Ну почти.
@bbbreaking · 1,976,428
#18
CREW RUSSIA
@crewruss1a · 61,081
#19
ЖИВОВЪ
@zhivoff · 131,247
#20
МИГ России
@mig41 · 479,656
#21
Воин DV
@voin_dv · 145,414
#22
WarGonzo
@wargonzo · 740,596
#23
НгП раZVедка
@NgP_raZVedka · 94,638
#24
Осведомитель
@infomil_live · 95,269
#25
🇷🇺Южный Фронт🇷🇺
@RuFront · 24,252
#26
Дневник Десантника🇷🇺
@DnevnikDesantnika · 75,657
#27
⚔️ СВАРЩИКИ
@svarschiki · 124,322
#28
Фронтовая птичка
@frontbird · 116,519
#29
Оперативные сводки
@opersvodki · 404,425
#30
Роман Алехин
@Alekhin_Telega · 116,751
#31
Поддубный |Z|О|V| edition
@epoddubny · 570,563
#32
Резидент
@rezident_ua · 954,322
#33
СИЛОВИКИ 🇷🇺
@SIL0VIKI · 182,496
#34
Шепот Фронта
@Tatarinov_Rus · 107,087
#35
Портфель Генштаба
@genshtab24 · 83,372
#36
Роман Сапоньков
@RSaponkov · 100,416
#37
Рамзай
@ramzayiegokomanda · 151,531
#38
ЗАПОРОЖСКИЙ ФРОНТ
@ZA_FROHT · 83,410
#39
Синяя Z Борода
@beard_tim · 108,611
#40
Адмэн
@adman_life · 10,362
#41
Репортёр Руденко V
@RtrDonetsk · 153,850
#42
Бладсикер 2.0
@bIoodsiker · 211,656
#43
Минобороны России
@mod_russia · 652,178
#44
ANNA NEWS
@anna_news · 230,693
#45
Позывной Брюс
@brussinf · 107,400
#46
Северный Ветер
@warriorofnorth · 118,804
#47
Русский меч
@Rrussiansword · 166,435
#48
Open Ukraine| Открытая Украина
@OpenUkraine · 180,075
#49
Мёртвые головы
@Dead_heads · 33,455
#50
Работайте, братья!
@btr80 · 149,149
#51
Белорусский силовик
@belarusian_silovik · 450,172
#52
Тринадцатый.
@Z13_Separ · 209,906
#53
Старше Эдды
@vysokygovorit · 488,650
#54
Fighterbomber
@bomber_fighter · 526,919
#55
Воевода Вещает
@ZOV_Voevoda · 167,485
#56
Kotsnews
@sashakots · 470,851
#57
ХИЛЕР l HEALER
@HealerTacMed · 130,708
#58
ZERGULIO
@SergeyKolyasnikov · 448,795
#59
Канал специального назначения
@okspn · 130,533
#60
Военкор Котенок
@voenkorKotenok · 310,285
#61
Aviahub
@Aviahub34 · 94,344
#62
Readovka
@readovkanews · 2,012,285
#63
Mash
@mash · 3,150,586
#64
Alex Parker Returns
@apwagner · 315,867
#65
Анатолий Шарий
@asupersharij · 1,730,742
#66
RAG&E - Razvedos Advanced Gear & Equipment
@razvedosaa · 137,885
#67
Позывной《OSETIN》
@osetin21 · 65,675
#68
Милитарист
@infantmilitario · 276,532
#69
SimpDungeon☠️
@grpzdc · 176,573
#70
Репортер Filatov
@filatovcorr · 167,568
#71
SHOT
@shot_shot · 1,269,828
#72
СОЛОВЬЁВ
@solovievlive · 1,117,380
#73
Белые дяди в Африке🌴
@wagner_group2022 · 124,287
#74
Украина.ру
@ukr_2025_ru · 494,735
#75
ЕЖ
@ejdailyru · 671,302
#76
Осташко! Важное
@ostashkonews · 431,721
#77
Baza
@bazabazon · 1,560,372
#78

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

Передовая Культура
@peredovaya_culture · 30,711
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 7 September 2026
Unfair Advantage
@unfair_advantage_tg · 24,690
Telegram ranks this channel #16 of 58 here — alongside 57 others — read 16 September 2026
CREW RUSSIA
@crewruss1a · 61,081
Telegram ranks this channel #22 of 75 here — alongside 74 others — read 22 August 2026
Никита Третьяков
@tretyakov_n · 26,410
Telegram ranks this channel #24 of 84 here — alongside 83 others — read 13 September 2026
Лыня🇷🇺
@Lunay14 · 22,476
Telegram ranks this channel #26 of 77 here — alongside 76 others — read 20 September 2026
Полковник Трифонов
@polkovnikt · 20,443
Telegram ranks this channel #28 of 86 here — alongside 85 others — read 27 September 2026
Осведомитель
@infomil_live · 95,269
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 16 August 2026
ЗАПОРОЖСКИЙ ФРОНТ
@ZA_FROHT · 83,410
Telegram ranks this channel #41 of 81 here — alongside 80 others — read 18 August 2026
Воин DV
@voin_dv · 145,414
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 13 August 2026
ВДВ Псков ZOV
@vdvpskovz · 25,250
Telegram ranks this channel #45 of 73 here — alongside 72 others — read 13 September 2026
Уголок Ситха
@Ugolok_Sitha · 49,220
Telegram ranks this channel #45 of 77 here — alongside 76 others — read 25 August 2026
ХИЛЕР l HEALER
@HealerTacMed · 130,708
Telegram ranks this channel #45 of 73 here — alongside 72 others — read 13 August 2026
VELES тихонько пишет
@veles_v_okope · 49,259
Telegram ranks this channel #51 of 78 here — alongside 77 others — read 7 September 2026
Басурин о главном
@basurin_e · 91,510
Telegram ranks this channel #54 of 87 here — alongside 86 others — read 29 August 2026
Дневник Десантника🇷🇺
@DnevnikDesantnika · 75,657
Telegram ranks this channel #54 of 82 here — alongside 81 others — read 19 August 2026
Канал специального назначения
@okspn · 130,533
Telegram ranks this channel #56 of 67 here — alongside 66 others — read 13 August 2026
Наука побеждать
@naukapobezhdatZ · 51,632
Telegram ranks this channel #57 of 74 here — alongside 73 others — read 25 August 2026
Алексей Суконкин
@A_S_Sukonkin · 40,677
Telegram ranks this channel #58 of 81 here — alongside 80 others — read 29 August 2026
СОЛДАТ УДАЧИ
@Soldieroffortune777 · 121,345
Telegram ranks this channel #60 of 80 here — alongside 79 others — read 13 August 2026
Military_Medic_V.
@Military_Medic_V · 39,811
Telegram ranks this channel #71 of 77 here — alongside 76 others — read 30 August 2026
Aviahub
@Aviahub34 · 94,344
Telegram ranks this channel #74 of 80 here — alongside 79 others — read 16 August 2026

This channel appears in 21 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 25 October 2026 — this entry's latest reading, not the date you are reading this.

“RUSVARG” (@rusvarg), 38,502 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/rusvarg.

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.