Channel
@TorXazan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6subscribers
+0 since we began measuring on 1 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003977046910 |
|---|---|
| Type | Channel |
| Username | @TorXazan |
| Created | 24 June 2026 — measured — dated from the channel’s first post |
| First recorded | 1 October 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TorXazan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 16:22 | 6 | no change |
| 1 Oct 2026, 15:47 | 6 | first reading |
4 posts held, back to 24 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 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 4 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 1 October 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.
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.
46 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5465370691891131082 | 11 | 23.9% | |
| custom 5467838846387386923 | 8 | 17.4% | |
| custom 5197556859392780542 | 6 | 13.0% | |
| custom 5467446252016795276 | 6 | 13.0% | |
| custom 5197306063367473204 | 4 | 8.70% | |
| custom 5447130025914566473 | 4 | 8.70% | |
| custom 5359681287722397690 | 2 | 4.35% | |
| custom 5465427084811732269 | 2 | 4.35% | |
| custom 5359816351558955197 | 1 | 2.17% | |
| custom 5449635671180348326 | 1 | 2.17% | |
| custom 5465326311994065221 | 1 | 2.17% |
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 3 of the 4 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 24 June 2026 to 20 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.
Photo, posted without a caption
custom 54678388463873869235custom 53596812877223976902custom 51975568593927805421custom 54496356711803483261custom 54653706918911310821custom 54674462520167952761
▫️▫️▫️▫️▫️▫️▫️▫️
custom 54674462520167952765custom 51973060633674732043custom 54653706918911310823custom 54678388463873869232custom 53598163515589551971custom 54471300259145664731
anon ; tt ; boost ; archive
custom 54653706918911310827custom 51975568593927805425custom 54471300259145664733custom 54654270848117322692custom 51973060633674732041custom 54653263119940652211custom 54678388463873869231
Channel created
Showing the 4 most recent of 4 posts we hold for @TorXazan. 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 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.
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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Дегарб” (@TorXazan), 6 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/TorXazan.
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.