Channel
@fate535
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002036442805 |
|---|---|
| Type | Channel |
| Username | @fate535 |
| Created | 17 May 2024 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/fate535 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 09:23 | 2 | +1 |
| 15 Aug 2026, 03:32 | 1 | no change |
| 7 Aug 2026, 12:33 | 1 | first reading |
3 posts held, back to 17 May 2024 — 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 3 posts for this entry, the most recent from 17 May 2024. An engagement rate over an empty window would be a number about nothing.
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.
226 reactions across 2 posts, in 12 distinct kinds. The most used accounts for 17.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5213275280054957755 | 40 | 17.7% | |
| custom 5307667335392276248 | 32 | 14.2% | |
| custom 5303450351817470625 | 24 | 10.6% | |
| custom 5416037984564687399 | 22 | 9.73% | |
| custom 5188516009069266578 | 18 | 7.96% | |
| custom 5190700738673656271 | 18 | 7.96% | |
| custom 5202220291933096756 | 17 | 7.52% | |
| custom 5305595017966924752 | 15 | 6.64% | |
| custom 5415842834135658938 | 14 | 6.19% | |
| custom 5210938890860377524 | 13 | 5.75% | |
| custom 5192944386639413581 | 9 | 3.98% | |
| custom 5305387669830775592 | 4 | 1.77% |
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 2 of the 3 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 226 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 17 May 2024 to 17 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
BenzX 🎀 sex money fellings die🔇 инициал строго в ник: BZX ✅
custom 521327528005495775531custom 530766733539227624819custom 530345035181747062518custom 541603798456468739918custom 519070073867365627113custom 518851600906926657812custom 520222029193309675610custom 530559501796692475210
🔗🔗🔗🔗🔗🔗 ☠ 🔤🔤🔤🔤🔤 From today we declare that the name “. "belongs to us. Even if there is even the slightest similarity in the name, we will ask you to change the name without conflicts.Not only the name and even the design also the initial. If we notice that there is a similarity in the design or in the initial, then we also have the right to ask to change 👕 12.12.23
custom 530766733539227624813custom 52132752800549577559custom 52022202919330967567custom 51885160090692665786custom 53034503518174706256custom 51907007386736562715custom 53055950179669247525custom 52109388908603775244
Channel created
Showing the 3 most recent of 3 posts we hold for @fate535. 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 3 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“BenzX.” (@fate535), 2 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/fate535.
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.