Telegram RegisterThe public register of Telegram

Channel

Змей Горыныч

@russdragon

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

3,034subscribers

+11 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001973700975
TypeChannel
Username@russdragon
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/russdragon

Growth

3,0233,0343,028.56 August 2026 — 3,023 subscribers7 August 2026 — 3,028 subscribers10 August 2026 — 3,032 subscribers12 August 2026 — 3,034 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net +11. 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 3,021–3,036 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:383,034+2
10 Aug 2026, 02:023,032+4
7 Aug 2026, 11:213,028+5
6 Aug 2026, 16:403,023first reading

Engagement

18 posts held, back to 28 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 18 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
54s
Average length
14s

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

423 reactions across 18 posts, in 29 distinct kinds. The most used accounts for 21.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9121.5%
6615.6%
😁5011.8%
custom 5370961671432979613307.09%
custom 5307909000317121664296.86%
266.15%
🫡266.15%
👍235.44%
🤬122.84%
❤‍🔥102.36%
👏102.36%
custom 537068716718819027992.13%
🤝51.18%
🤯51.18%
custom 538183795455559385440.946%
🏆40.946%
custom 538225157708606701130.709%
😱30.709%
🙈30.709%
custom 537103372809930297620.473%
9 further kinds122.84%

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

Measured over the 18 most recent posts we hold, published 28 April 2026 to 10 July 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.

Telegram Stars

Stars received
76
across the posts below
Posts paid on
5
of 18 we hold a reading for · 28%
Most on one post
70
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @russdragon. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 28 April 2026 to 10 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

10 Jul 2026, 16:15 UTC886 views27 reactionsread 8 August 2026
Photo

Были на DRONE EXPO Российская китайскся выставка производителей БПЛА и комплектующих.

14custom 53079090003171216645🫡3custom 53706871671881902792custom 53709616714329796132😁1

1 Jul 2026, 14:28 UTC≈1,100 views25 reactionsread 8 August 2026
Forwarded from @ptsd_againVideo

и эт заберем люблю такое

😁18🔥3🫡3🤩1

26 Jun 2026, 20:38 UTC≈1,440 views9 reactionsread 8 August 2026
Forwarded from @soratnikgroupPhoto

❗️Важная информация от военных, друзья: "В местах остановки военных машин или гражданским с военными, ждуны начали прикреплять к машинам такие маячки. После установки - 100% прилет в машину. Необходимо предупредить всех наших водителей, чтоб во время остановок не выпускали автомобиль из вида. Крепят и здесь, и в Ростове, в Ростовской области."

🤝5🔥31

22 Jun 2026, 19:47 UTC≈1,700 views10 reactionsread 8 August 2026
Forwarded from @rosich_russia

В Брянске прилеты, отключение интернета не помогает, почему так? "Росич" в MAX | TG | VK

🏆4🙈3🍾2🔥1

19 Jun 2026, 08:15 UTC≈1,840 views31 reactions1 Starread 8 August 2026
Photo

К прогулке готовы🤘🏻😈 Арс😁 Змей Горыныч. Подписаться.

16🔥9custom 53706871671881902795custom 53818379545555938541

17 Jun 2026, 05:59 UTC≈1,660 views33 reactionsread 8 August 2026
Photo

В ожидании талончиков на бензин, VTOL на ДВС сам себя заправит...

😁15custom 537096167143297961386custom 53079090003171216644

11 May 2026, 11:38 UTC≈2,860 views36 reactionsread 8 August 2026
Photo

Змей Горыныч. Подписаться.

14🔥6custom 53709616714329796136custom 53818379545555938543🫡2custom 53079090003171216642custom 538225157708606701121

11 May 2026, 08:02 UTC≈2,470 views27 reactionsread 8 August 2026
Photo

Туда его... Змей Горыныч. Подписаться.

🔥12👏7custom 5307909000317121664411🤣1🥰1

8 May 2026, 10:27 UTC≈19,400 views36 reactions1 Starread 8 August 2026
Video

Video, posted without a caption

👍17😁114custom 53079090003171216642custom 53709616714329796132

5 May 2026, 07:19 UTC≈2,460 views17 reactionsread 8 August 2026
Video

Атака на Чебоксары продолжается, фиксируются случаи применения беспилотных летательных аппаратов по жилым домам и гражданскому населению.

🤬12😱31🙏1

4 May 2026, 18:37 UTC≈1,850 views16 reactions3 Starsread 8 August 2026
Photo

Змей Горыныч. Подписаться.

🔥94👏3

3 May 2026, 05:49 UTC≈1,870 views11 reactionsread 8 August 2026
Forwarded from @UAVDEVVideo

К вопросу об эффективности ёлки без бч. В данном случае Аллах помог сбить хвостовое оперение и вражеский дрон, в конце концов, упал. Пуск ёлки стоит 600 тыр, по слухам. А на втором видео самопальный квадрик с небольшой бч сносит крыло с первого удара. Вопросы есть? 😒 Ёлка может снабжаться бч, конструкцией это предусмотрено. Но не снабжается тому що не положено.

6🤯5

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 812,938 of 1,151,006entries 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.

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

“Змей Горыныч” (@russdragon), 3,034 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/russdragon.

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.