Telegram RegisterThe public register of Telegram

Channel

РусскиЙ🇷🇺таков путь💀

@RUSVoin55

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

933subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002002876986
TypeChannel
Username@RUSVoin55
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/RUSVoin55

Growth

933934933.56 August 2026 — 933 subscribers6 August 2026 — 934 subscribers14 August 2026 — 933 subscribers6 August 202614 August 2026
3 measurements spanning 8 days. 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 933–934 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:45933-1
6 Aug 2026, 18:26934+1
6 Aug 2026, 14:22933first reading

Engagement

20 posts held, back to 6 July 2026the 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
22.5%
avg views ÷ 933 subscribers
Avg views / post
210
6 posts measured
Reaction rate
5.56%
reactions ÷ views · ER floor
Posts in window
6
of 20 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 5 August 2026
Posts held20 (6 July 20265 August 2026)
Views total1,260
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:22 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

186 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 38.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7238.7%
custom 5341824767915734320168.60%
custom 5341758049893757021158.06%
😨158.06%
custom 5287765917231490861147.53%
💯147.53%
🤝94.84%
👍84.30%
😭63.23%
custom 540695851819021960452.69%
custom 530541779043641783542.15%
custom 539091479241006333531.61%
custom 541603837970168325431.61%
🙏21.08%

Custom emoji. 7 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 20 of the 20 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 186reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 July 2026 to 5 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.

Recent posts

5 Aug 2026, 13:44 UTC104 views11 reactionsread 6 August 2026
Voice message

Voice message, posted without a caption

5custom 52877659172314908613custom 53418247679157343203

5 Aug 2026, 13:41 UTC104 views13 reactionsread 6 August 2026
Voice message

Voice message, posted without a caption

7custom 53417580498937570213custom 54160383797016832543

2 Aug 2026, 03:54 UTC183 views10 reactionsread 6 August 2026
Forwarded from @oxranahvk715Photo

Поздравляем ветеранов, военнослужащих и всех, кто связан с ВДВ, с праздником🇷🇺 В этот день мы выражаем признательность за мужество, выдержку и верность традициям. Пусть каждый дом будет наполнен радостью, уважением и добрыми вестями🫡 🇷🇺ВДВ - это мужество высшего класса, храбрость первой категории, боевая готовность номер один". В. Ф. Маргелов

6custom 53418247679157343204

Signed Рус 🇷🇺 🧌

1 Aug 2026, 05:01 UTC221 views2 reactionsread 6 August 2026

Доброе утро (ДоН , река такая ) Токмак передок (ДоН)

2

1 Aug 2026, 04:59 UTC226 views5 reactionsread 6 August 2026
Video

Работают наши операторы ! Свинки - Русский, таков путь💀 Слава ВДВ!😈🇷🇺 Канал ознакомительный, показывает жит, быт участников СВО, только правда и нечего кроме! Администрация канала имет боевой опыт и сейчас на СВО Ссылка для друга https://t.me/RUSVoin55 Вк https://vk.ru/rusvoin55

👍5

10 Jul 2026, 19:45 UTC576 views9 reactionsread 6 August 2026

Ну хули вы не стреляете то ребята? Стреляйте, или вы можете только по гераням стрелять ДОН (река такая )

💯62👍1

10 Jul 2026, 19:43 UTC554 views10 reactionsread 6 August 2026

Прямо сейчас 22:42 над нами пролетают ударные бпла противника в сторону РФ

😨73

9 Jul 2026, 10:43 UTC578 views13 reactionsread 6 August 2026

ДОБРЫЙ ДЭНЬ ,МЫ ТУТ!

5custom 53418247679157343203custom 53909147924100633353custom 54069585181902196042

8 Jul 2026, 08:06 UTC600 views5 reactionsread 6 August 2026

Запорожская область. Губернатор: На автомобильной дороге Приморского муниципального округа атаке БпЛА противника подвергся рейсовый пассажирский автобус, следовавший по маршруту Краснодар — Мелитополь. В автобусе было одиннадцать человек: девять пассажиров и два водителя. Все успели покинуть автобус, пострадавших нет. На месте работают оперативные службы. Пассажиры оперативно эвакуированы.

3😨2

7 Jul 2026, 19:55 UTC486 views12 reactionsread 6 August 2026

Украина отправила Путину реалистичное предложение о завершении войны — глава МИД Украины Сибига Что за план ? Там зеленский поцАлует лобок ? Или он запенит себя сам ? А мы посмотрим !

custom 53417580498937570216custom 53418247679157343203custom 54069585181902196043

7 Jul 2026, 10:28 UTC494 views11 reactionsread 6 August 2026
Voice message

Voice message, posted without a caption

custom 528776591723149086163👍2

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

Citation-graph rank

Citation-graph rank — 266,487 of 1,480,688entries 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.

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 1 registered channel — 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“РусскиЙ🇷🇺таков путь💀” (@RUSVoin55), 933 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/RUSVoin55.

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.