Sticker, posted without a caption

Channel
𝐓𝐇𝐄 𝐃𝐑𝐔𝐆𝐆𝐄𝐃
@DRUGGERSKY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
394subscribers
-101 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003902990491 |
|---|---|
| Type | Channel |
| Username | @DRUGGERSKY |
| Created | 8 June 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/DRUGGERSKY |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 17:36 | 394 | -100 |
| 9 Aug 2026, 21:11 | 494 | -1 |
| 9 Aug 2026, 17:45 | 495 | first reading |
Engagement
19 posts held, back to 8 June 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 143.1%
- avg views ÷ 394 subscribers
- Avg views / post
- 564
- 2 posts measured
- Reaction rate
- 2.66%
- reactions ÷ views · ER floor
- Posts in window
- 2
- of 19 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.
| Window | Rolling 30 days · latest post in window 22 July 2026 |
|---|---|
| Posts held | 19 (8 June 2026 – 22 July 2026) |
| Views total | 1,128 |
| Reactions total | 30 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 17:45 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
- 16s
- Average length
- 16s
Measured directly from 1 video 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
259 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 19.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5395764802624722269 | 51 | 19.7% | |
| custom 5341550787656981875 | 50 | 19.3% | |
| custom 5429577237605151150 | 39 | 15.1% | |
| custom 5289662102343023004 | 33 | 12.7% | |
| custom 5312072863736432219 | 33 | 12.7% | |
| custom 5395511378079421812 | 28 | 10.8% | |
| custom 5312134681200723266 | 25 | 9.65% |
Custom emoji. Every row above is a 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 11 of the 19 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 259reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 8 June 2026 to 22 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.
Recent posts
#DRGVIDEO ✔️| Наши красивые.
custom 53957648026247222698custom 53120728637364322196custom 54295772376051511506custom 53415507876569818755custom 52896621023430230042custom 53121346812007232662custom 53955113780794218121
Sticker, posted without a caption
⚡️Инициалы не являются обязательным условием для вступления, но мы всегда положительно относимся к их использованию. 🎁Вариации инициалов: [Ник, инфо] — DRG / ᴰᴿᴳ [Премиум] — 🤩 / 🤩 ⚡️Инициалы можно скопировать нажатием. 🕸
custom 534155078765698187510custom 52896621023430230045custom 54295772376051511505custom 53120728637364322194custom 53955113780794218123custom 53957648026247222693custom 53121346812007232662
Sticker, posted without a caption
𝐑𝐄𝐂𝐊𝐋𝐄𝐒𝐒 🤩 𝑶𝑾𝑵𝑬𝑹 — Dragao Ravenscoft. ➿➿➿➿➿➿➿➿➿➿➿➿➿ ✔️𝑨𝑫𝑴 𝑺𝑵𝑹 — Bagheera Winterhalter. ✔️𝑨𝑫𝑴 𝑱𝑼𝑵𝑰𝑶𝑹 — Kaoru Mine. ✔️𝑨𝑫𝑴 𝑪𝑯𝑨𝑻 — Latte Blackwood. ✔️𝑨𝑫𝑴 𝑽𝑰𝑫𝑬𝑶 — Talita Weiss. ➿➿➿➿➿➿➿➿➿➿➿➿➿ 🤩 Подать заявку. 🕸
custom 53957648026247222694custom 52896621023430230043custom 54295772376051511503custom 53415507876569818752custom 53955113780794218122custom 53120728637364322191
Sticker, posted without a caption
𝐈𝐍𝐒𝐀𝐍𝐄 🤩 𝑶𝑾𝑵𝑬𝑹 — Dragao Ravenscoft. ➿➿➿➿➿➿➿➿➿➿➿➿➿ ✔️𝑨𝑫𝑴 𝑺𝑬𝑵𝑰𝑶𝑹 — Kaoru Mine. ✔️𝑨𝑫𝑴 𝑱𝑼𝑵𝑰𝑶𝑹 — Tamelian Sein ✔️𝑨𝑫𝑴 𝑪𝑯𝑨𝑻 — Serafim Winterhalter. ✔️𝑨𝑫𝑴 𝑨𝑪𝑻𝑰𝑽𝑬 — TerrorBlade. ✔️𝑨𝑫𝑴 𝑽𝑰𝑫𝑬𝑶 — Talita Astralova. ➿➿➿➿➿➿➿➿➿➿➿➿➿ 🤩 Подать заявку. 🕸
custom 53955113780794218125custom 52896621023430230044custom 53415507876569818753custom 54295772376051511503custom 53957648026247222692
Sticker, posted without a caption
⚡️Выбирай свою клетку⚡️ ⭐Подать заявку INSANE. ⭐️Подать заявку RECKLESS. 🕸
custom 53955113780794218128custom 54295772376051511507custom 53957648026247222696custom 53415507876569818753custom 52896621023430230042custom 53120728637364322191custom 53121346812007232661
Sticker, posted without a caption
⚡️ Перед вступлением внимательно прочитайте правила конференции. ⚡️ Незнание правил не освобождает вас от ответственности. Каждое противоречие списку правил карается предупреждением.
custom 53415507876569818759custom 52896621023430230046custom 53957648026247222695custom 53121346812007232664custom 54295772376051511502custom 53120728637364322191custom 53955113780794218121
Showing the 12 most recent of 19 posts we hold for @DRUGGERSKY. 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 — 1,016,539 of 1,565,402entries 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.
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.
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@DRUGGERSKY named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐓𝐇𝐄 𝐃𝐑𝐔𝐆𝐆𝐄𝐃” (@DRUGGERSKY), 394 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/DRUGGERSKY.
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.