🌟🌟🤍!

Channel
ㅤ𝁑愛𝐬𝗁𝗂𝐡𝗈;𝐨𝗄𝐞?
@fckingsx5
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
12subscribers
-305 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003548132174 |
|---|---|
| Type | Channel |
| Username | @fckingsx5 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/fckingsx5 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 04:56 | 12 | -297 |
| 1 Sept 2026, 16:08 | 309 | -27 |
| 25 Aug 2026, 04:04 | 336 | -26 |
| 17 Aug 2026, 15:26 | 362 | +38 |
| 10 Aug 2026, 03:31 | 324 | +7 |
| 9 Aug 2026, 13:47 | 317 | first reading |
Engagement
20 posts held, back to 3 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
52 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 23.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5440901249593546049 | 12 | 23.1% | |
| custom 5458506814461081897 | 11 | 21.2% | |
| custom 5470081373366689165 | 9 | 17.3% | |
| custom 5470127990941713935 | 8 | 15.4% | |
| custom 5436257268960101457 | 4 | 7.69% | |
| custom 5217562331726259944 | 3 | 5.77% | |
| custom 5470169802448342536 | 3 | 5.77% | |
| custom 5474233026193948885 | 2 | 3.85% |
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 5 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 52 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 3 July 2026 to 9 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.
Recent posts
какой-то список.. хах, все наши.. здесь даже я есть
🌟🌟
Sticker, posted without a caption
резы интерактива! 🤩я замучилась тк приходилось лезть не только в обычный крк, чтобы найти подходящего персонажа.. всем спасибо за участие! опять вопрос : с кем из крк я у вас ассоциируюсь?
Sticker, posted without a caption
🤩🩶,, 𝐢𝗇𝗍𝖾𝗋𝖺𝖼𝗍𝗂𝗏𝖾 𝐟𝗋𝗈𝗆.. 𝐬𝗁𝗂𝐡𝗈??🤩🤩 . 🤩🤩𝐝𝗈𝖼𝗍𝗈𝐫, 𝐝𝗈𝖼𝗍𝗈𝐫, 𝐟𝖾𝗅𝗅 𝐠𝗈𝗈𝖽.. 𝐜𝗈𝗆𝖾 𝐦𝖺𝗄𝖾 𝐦𝖾 𝐟𝖾𝖾𝗅 𝐫𝖾𝖺𝗅 𝐠𝗈𝗈𝐝! 🔤 😀😀🤩🤩😀😀😀😀😀🤩 🎀 : 𝐤а𝐤ая вы п𝐞ч𝐞нь𝐤а из cookie run kingdom ? 🌟 🤩 подпишитесь на блядское инфо шихоро🤩@fckingsx5 🤩 ртшните в активный кн 🤩 скиньте доквы в комм под постом и юз 😀😀🖤😀 😀𝟏𝟐/𝟏𝟎 😀😀😀𝐨ткрыт𝐨 / з𝐚крыт𝐨
custom 54700813733666891653
Sticker, posted without a caption
. 🤩🤩𝐠𝗂𝗏𝖾𝐚𝗐𝖺𝐲 𝐟𝗋𝗈𝐦 𝐬𝗁𝗂𝐡𝗈𝐫𝗈! 🤩🎁 🎁🤩 𝐇а физ a𝐤𝐤аунт сш𝐚 !🤩🤩 😀😀🤩🎀что т𝐚𝐤ое физ ?? 🤩 🤩это номер имеющий физическую основу. и в отличие от виртуальных, меньше шанса слета. + иногда вас нельзя пробить через всяких ботов . 😀🎁🤩𝐇р𝐚вится? т𝐨гд𝐚 слуш𝐚й 😀😀😀 𝐲сл𝐨вия уч𝐚стия!🤩🤩🤩 😀🤩 подписка на шихоро ! но без дальнейшей отписки 🤩 рт в свой активный канал 😀🤩 доки под пост и номерок участника. 😀😀😀😀Ит𝐨ги 𝟏𝟎.𝟎𝟖
custom 54701279909417139353
Sticker, posted without a caption
Sticker, posted without a caption
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @fckingsx5. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 11 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.
@anon69mango · 47 postsེ ֺ ⃟░⃟۫🍬𝗳𝐮𝐲𝐮𝗸𝗼 𝗮𝗿𝗰𝗵𝗶𝘃𝗲 ୧ ♡゙
@fuyukosilly · 62 posts𓆇 𝕚ꬻ𝙛𝕠݃ Эթֺυᥴ̼𐐫ֺꪒִֺь 𓆪 𓂃
@arisinf · 3281 postрест ѡɛɼƒⅈℵ ОН/ЕГО
@cmepmhocmi · 761 postдобрый инт
@dafachha · 11 postfilth's info ‼️
@errorberry · 51 post︎ ︎ ִ𓈒 ︎ ︎ ݁ ︎ ︎ ︎ ݂𝑝𝑎𝑟𝑎𝒅𝒊𝒔 ݁
@forgottenwarmth · 71 post🐳 Бегу бегу – Сок любимый ❤️
@Okutopus · 2471 post♡゙̼ ᷼︵𐔌резы интерактов рафи && архивᶻz ৎ
@rapfises_rezz_archive · 71 post𝓈𝒽𝒾𝓃' 𝓈 𝒾𝓃𝒻ℴ
@sqrrwr · 2971 post@ trishskisser
@Trishskisser · 21 post
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“ㅤ𝁑愛𝐬𝗁𝗂𝐡𝗈;𝐨𝗄𝐞?” (@fckingsx5), 12 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/fckingsx5.
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.