Telegram RegisterThe public register of Telegram
Telegram profile photo for ЗАКРЫТО. ➪ 𝑺𝓹𝓲𝓷 𝓸𝓯 𝑭𝓪𝓽𝓮..

Channel

ЗАКРЫТО. ➪ 𝑺𝓹𝓲𝓷 𝓸𝓯 𝑭𝓪𝓽𝓮..

@SpinofFate_life

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

21subscribers

-3 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003907605273
TypeChannel
Username@SpinofFate_life
CreatedBetween 1 April 2026 and 14 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/SpinofFate_life

Growth

212422.513 August 2026 — 24 subscribers13 August 2026 — 24 subscribers20 August 2026 — 23 subscribers3 September 2026 — 22 subscribers11 September 2026 — 21 subscribers13 August 202611 September 2026
5 measurements spanning 29 days, net -3. 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 21–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 23:3621-1
3 Sept 2026, 09:0522-1
20 Aug 2026, 12:2223-1
13 Aug 2026, 13:3124no change
13 Aug 2026, 13:1724first reading

Engagement

20 posts held, back to 14 June 2026the 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 20 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

29 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 27.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5429494331851441877827.6%
🍓724.1%
custom 5429369421317586929517.2%
🔥517.2%
🎉413.8%

Custom emoji. 2 of the rows above are 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 20 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 14 June 2026 to 5 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

5 Jul 2026, 18:29 UTCviews —

Channel name was changed to «ЗАКРЫТО. ➪ 𝑺𝓹𝓲𝓷 𝓸𝓯 𝑭𝓪𝓽𝓮..»

5 Jul 2026, 18:29 UTC84 views1 reactionsread 13 August 2026

Итак, принято решение закрыть флуд. У меня больше нет желания заниматься проектом, да и вообще посещать флуды. Спасибо тем, кто был с нами вездк и всегда, со всеми разрыв.

🍓1

28 Jun 2026, 23:32 UTC86 views5 reactionsread 13 August 2026

𝓦𝓪𝓷𝓭𝓮𝓻𝓮𝓻 ─ Спасибо за результат. Я теперь хочу себе такую кружку

🍓2🎉2🔥1

28 Jun 2026, 17:24 UTC89 viewsread 13 August 2026

разрыв с 𝘕𝘖𝘙𝘒𝘌𝘞𝘘 𝘍𝘓𝘖𝘖𝘋 причина: неактив очень долгое время #𝓫𝓻𝓮𝓪𝓴_𝓢𝓞𝓕

24 Jun 2026, 18:10 UTC76 viewsread 13 August 2026

𝓦𝓪𝓷𝓭𝓮𝓻𝓮𝓻 ─ репост тайм переноситься на завтра так как у меня проблемы с интарнетом

21 Jun 2026, 19:12 UTC50 views1 reactionsread 13 August 2026
Photo

🐾 𝑭𝒂𝒎𝒊𝒍𝒚 𝑼𝒏𝒊𝒐𝒏 “𝓤𝓷𝓽𝓲𝓵 𝓽𝓱𝓮 𝓭𝓮𝓪𝓽𝓱 𝓭𝓸𝓽𝓱 𝓹𝓪𝓻𝓽 𝓾𝓼, 𝓭𝓸 𝔂𝓸𝓾 𝔀𝓪𝓷𝓽 𝓶𝓮 𝓽𝓸 𝓫𝓮 𝓽𝓻𝓾𝓮?” ʍы ᴨᴇᴩᴇзᴀᴋᴧючᴀᴇʍ ᴄоюз нᴀ ᴄᴇʍᴇйный ᴄ Nᴀ Gyᴇʍ nᴇ ʙᴀluysyᴀ nyᴀ~🪭, ᴛᴇᴨᴇᴩь он нᴀɯ ᴄын ᴀ ʍы ᴇᴦо оᴛᴇц 🪄 ɪɴꜰᴏ | ʟɪꜰᴇ . ᴛʀᴀᴄᴋɪɴɢ:@MadaraY 𝓔𝓿𝓮𝓻𝔂 𝓽𝓲𝓶𝓮 𝓘 𝓽𝓱𝓲𝓷𝓴 𝓸𝓯 𝔂𝓸𝓾, 𝓶𝔂 𝓱𝓮𝓪𝓻𝓽 𝓼𝓽𝓪𝓻𝓽𝓼 𝓫𝓮𝓪𝓽𝓲𝓷𝓰 𝓯𝓪𝓼𝓽𝓮𝓻. 𝓓𝓸 𝔂𝓸𝓾 𝓯𝓮𝓮𝓵 𝓽𝓱𝓮 𝓼𝓪𝓶𝓮 𝔀𝓪𝔂 ────────────── #𝓯𝓪𝓶𝓲𝓵𝔂𝓾𝓷𝓲𝓸𝓷_𝓢𝓞𝓕 #𝓾𝓷𝓲𝓸𝓷_𝓢𝓞𝓕

🍓1

20 Jun 2026, 17:19 UTC44 views5 reactionsread 13 August 2026
Photo

──────⊏𝓛𝓲𝓷𝓲 ⊐────── Только заметил, спасибо за подарок. Ну левв наш 😘 ─────────────────

🎉2🔥2🍓1

20 Jun 2026, 17:09 UTC55 views2 reactionsread 13 August 2026
Photo

🎪 𝑵𝒆𝒘 𝑼𝒏𝒊𝒐𝒏 “𝓨𝓸𝓾 𝓳𝓾𝓼𝓽 𝓬𝓪𝓵𝓵 𝓸𝓾𝓽 𝓶𝔂 𝓷𝓪𝓶𝓮, 𝓪𝓷𝓭 𝔂𝓸𝓾 𝓴𝓷𝓸𝔀 𝔀𝓱𝓮𝓻𝓮𝓿𝓮𝓻 𝓘 𝓪𝓶, 𝓘'𝓵𝓵 𝓬𝓸𝓶𝓮 𝓻𝓾𝓷𝓷𝓲𝓷𝓰 𝓽𝓸 𝓼𝓮𝓮 𝔂𝓸𝓾 𝓪𝓰𝓪𝓲𝓷.„ 𝐿𝒾𝓃𝒾'𝓈 𝒩𝑒𝓌 𝒰𝓃𝒾𝑜𝓃 ⇩ ᅠ‎⃟‎ ‎⃟💽⫶𝗘𝗩𝕴𝗟 𝗖𝕬𝗧 𓈒𝆹𝅥𝆺ִ𝅥۪ ɪɴꜰᴏ | ʟɪꜰᴇ ᴛʀᴀᴄᴋɪɴɢ:@Lohen_evlbot 𝓜𝓪𝔂 𝓸𝓾𝓻 𝓾𝓷𝓲𝓸𝓷 𝓫𝓮 𝓪𝓼 𝓼𝓸𝓵𝓲𝓭 𝓪𝓼 𝓪𝓷 𝓪𝓮𝓻𝓲𝓪𝓵𝓲𝓼𝓽'𝓼 𝓼𝓽𝓾𝓷𝓽 𝔀𝓲𝓽𝓱 𝓷𝓸 𝓼𝓪𝓯𝓮𝓽𝔂 𝓵𝓲𝓷𝓮... 🎈 #𝓾𝓷𝓲𝓸𝓷_𝓢𝓞𝓕

🔥2

19 Jun 2026, 20:54 UTC44 viewsread 13 August 2026
Photo

🎪 𝑵𝒆𝒘 𝑼𝒏𝒊𝒐𝒏 “𝓨𝓸𝓾 𝓳𝓾𝓼𝓽 𝓬𝓪𝓵𝓵 𝓸𝓾𝓽 𝓶𝔂 𝓷𝓪𝓶𝓮, 𝓪𝓷𝓭 𝔂𝓸𝓾 𝓴𝓷𝓸𝔀 𝔀𝓱𝓮𝓻𝓮𝓿𝓮𝓻 𝓘 𝓪𝓶, 𝓘'𝓵𝓵 𝓬𝓸𝓶𝓮 𝓻𝓾𝓷𝓷𝓲𝓷𝓰 𝓽𝓸 𝓼𝓮𝓮 𝔂𝓸𝓾 𝓪𝓰𝓪𝓲𝓷.„ 𝐿𝒾𝓃𝒾'𝓈 𝒩𝑒𝓌 𝒰𝓃𝒾𝑜𝓃 ⇩ ⲇⲟυⲙⲁ ⲙⲉⲇⲏⲟυⲋⲉ ɪɴꜰᴏ | ʟɪꜰᴇ ᴛʀᴀᴄᴋɪɴɢ:@vlddoma 𝓜𝓪𝔂 𝓸𝓾𝓻 𝓾𝓷𝓲𝓸𝓷 𝓫𝓮 𝓪𝓼 𝓼𝓸𝓵𝓲𝓭 𝓪𝓼 𝓪𝓷 𝓪𝓮𝓻𝓲𝓪𝓵𝓲𝓼𝓽'𝓼 𝓼𝓽𝓾𝓷𝓽 𝔀𝓲𝓽𝓱 𝓷𝓸 𝓼𝓪𝓯𝓮𝓽𝔂 𝓵𝓲𝓷𝓮... 🎈 #𝓾𝓷𝓲𝓸𝓷_𝓢𝓞𝓕

Showing the 12 most recent of 20 posts we hold for @SpinofFate_life. 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.

Mentions

Named by 4 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.

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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“ЗАКРЫТО. ➪ 𝑺𝓹𝓲𝓷 𝓸𝓯 𝑭𝓪𝓽𝓮..” (@SpinofFate_life), 21 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/SpinofFate_life.

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.