😿
custom 53435227102217918404custom 53977778967460248214custom 53057371513196811793

Channel
@deadgensa
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
-9 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003976998380 |
|---|---|
| Type | Channel |
| Username | @deadgensa |
| Created | Between 1 April 2026 and 28 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/deadgensa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 05:05 | 6 | -11 |
| 25 Aug 2026, 08:01 | 17 | +1 |
| 18 Aug 2026, 11:33 | 16 | +1 |
| 12 Aug 2026, 00:01 | 15 | no change |
| 10 Aug 2026, 13:02 | 15 | first reading |
12 posts held, back to 28 July 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 page of 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 12 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
82 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 23.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5397777896746024821 | 19 | 23.2% | |
| custom 5420493935824902425 | 13 | 15.9% | |
| custom 5422750455807645007 | 10 | 12.2% | |
| custom 5461165609670703914 | 9 | 11.0% | |
| custom 5343522710221791840 | 8 | 9.76% | |
| custom 5299042487011154856 | 5 | 6.10% | |
| custom 5393180666831610201 | 5 | 6.10% | |
| custom 5397791176784901986 | 5 | 6.10% | |
| custom 5305737151319681179 | 3 | 3.66% | |
| custom 5420314071184480074 | 3 | 3.66% | |
| custom 5397633817773115413 | 2 | 2.44% |
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 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 12 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 82 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 28 July 2026 to 11 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.
😿
custom 53435227102217918404custom 53977778967460248214custom 53057371513196811793
🖤
custom 53977778967460248215custom 53435227102217918402custom 53976338177731154132
амбассадоры руслин
custom 52990424870111548565custom 53977778967460248215custom 53977911767849019863
Photo, posted without a caption
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤСтреляй,Только Потом Не Жалейㅤㅤㅤ
custom 53977778967460248211
File, posted without a caption
ㅤㅤㅤㅤ⚔️ 𝔾𝓮 ' n ̷S̷𝖆 𝕬non | Stickers | About Me
custom 53977778967460248214custom 53435227102217918402custom 53977911767849019862
я не шучу.
custom 54611656096707039144custom 54204939358249024252custom 54227504558076450072
на фудкорт
custom 54204939358249024256custom 54227504558076450073custom 54611656096707039143
мэйби бэйби такая зайка
custom 53931806668316102015custom 54203140711844800743custom 54204939358249024253
блин
custom 54227504558076450075custom 54204939358249024252custom 54611656096707039142
Showing the 12 most recent of 12 posts we hold for @deadgensa. 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.
Named by 2 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.
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.
@deadgensa 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Stickers” (@deadgensa), 6 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/deadgensa.
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.