Telegram RegisterThe public register of Telegram

Channel

death

@sx4death

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

9subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003706702935
TypeChannel
Username@sx4death
Created17 March 2026 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/sx4death

Growth

98 August 2026 — 9 subscribers12 August 2026 — 9 subscribers8 August 202612 August 2026
2 measurements spanning 4 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:469no change
8 Aug 2026, 10:479first reading

Engagement

10 posts held, back to 17 March 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 11 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
2

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

281 reactions across 3 posts, in 8 distinct kinds. The most used accounts for 16.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54632386271757227274716.7%
custom 52063406988733009944516.0%
custom 52289315181806580764014.2%
custom 54656125543844722784014.2%
custom 54652250280752916013311.7%
custom 54677609915152144943111.0%
custom 5465322476588272328238.19%
custom 5447334462062889078227.83%

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

Measured over the 10 most recent posts we hold, published 17 March 2026 to 11 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

11 Jul 2026, 09:51 UTC111 viewsread 12 August 2026
Forwarded from @tupaiusPhoto

⸝⸝ ТУПА Я — МИСА АМАНЕ ( #deathnote )

17 Mar 2026, 10:41 UTC930 views99 reactionsread 12 August 2026
Photo

🎁🤩ur opinion abt mee 🤩 🤩😀нег принимается, без флуда pls

custom 546561255438447227825custom 520634069887330099423custom 546522502807529160117custom 52289315181806580768custom 54473344620628890787custom 54653224765882723287custom 54632386271757227276custom 54677609915152144946

17 Mar 2026, 10:41 UTC906 views94 reactionsread 12 August 2026
Photo

❤️🤩my luvv 🤩 🤩😀 fp teru asya kirva foleur sivi hibi satoshi killy

custom 546323862717572272721custom 522893151818065807617custom 546776099151521449417custom 52063406988733009948custom 54652250280752916018custom 54653224765882723288custom 54656125543844722788custom 54473344620628890787

17 Mar 2026, 10:41 UTC853 views88 reactionsread 12 August 2026
Photo

🎶🤩карма🥹sheher🥹7teen 😀shp tell me smth tltp

custom 546323862717572272720custom 522893151818065807615custom 520634069887330099414custom 54473344620628890788custom 54652250280752916018custom 54653224765882723288custom 54677609915152144948custom 54656125543844722787

Showing the 10 most recent of 10 posts we hold for @sx4death. 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 — 884,186 of 1,345,403entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

тупа ( я / мы )
@tupaius · 24,1501 post

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

adapter
@ANAperehod · 1691 postinfo confession
@infoconfe · 6211 post

Names

Channels on the register whose handles appear in this channel's posts.

тупа ( я / мы )
@tupaius · 24,1501 post

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.

“death” (@sx4death), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sx4death.

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.