Channel
@SocialQuestionsCM_COK
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
45subscribers
+0 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003933057669 |
|---|---|
| Type | Channel |
| Username | @SocialQuestionsCM_COK |
| Description | 𝐓𝐡𝐞 𝐬𝐡𝐨𝐰 𝐛𝐞𝐠𝐢𝐧𝐬! Начало :: 01.06. 26 Конец :: . . . Предводитель этого цирка — @LazarevCOK_bot архив — @COKArchive |
| Created | 31 May 2026 — measured — dated from the channel’s first post |
| First recorded | 28 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SocialQuestionsCM_COK |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 21:45 | 45 | no change |
| 28 Aug 2026, 21:30 | 45 | first reading |
12 posts held, back to 31 May 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 12 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 28 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.
81 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 29.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5251273418363411959 | 24 | 29.6% | |
| custom 5251577184220390001 | 17 | 21.0% | |
| custom 5251252987203982958 | 11 | 13.6% | |
| custom 5251206781945813520 | 10 | 12.3% | |
| custom 5251543803734562170 | 8 | 9.88% | |
| custom 5251704491346011676 | 5 | 6.17% | |
| custom 5251502477559242613 | 4 | 4.94% | |
| custom 5251550396509360698 | 2 | 2.47% |
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 7 of the 12 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 81 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 31 May 2026 to 2 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.
🤩: Я умоляю, кто-нибудь, пойдёмте со мной в рейв смотреть Величайшего Шоумена. #щп
custom 52512067819458135203custom 52515024775592426131custom 52515438037345621701custom 52515771842203900011
🤩: Канал не дожил, но, всё-таки, у меня день рождения.🤩 Юпи ё, юпи ей. #щп
🤩: Хотите, я проведу вам угадайку с принцессами дисней, чтобы канал не пустовал перед новым соцопросом? 20+ реакций - играем #щп
custom 52512734183634119599custom 52512529872039829588custom 52515771842203900016custom 52515438037345621702custom 52515024775592426131custom 52517044913460116761
Sticker, posted without a caption
🤩: Эпично выхожу из Реста под "большие города" и мнение со мной🤩 #щп
custom 52512734183634119592custom 52512529872039829581custom 52515503965093606981
🤩: Я дико извиняюсь, но забыл предупредить, но до 21 числа нахожусь на отдыхе в Турции🤩. Сразу после этого вернусь в активную фазу, не теряйте. #щп
🤩: Всем спасибо, все расходимся. Огромное спасибо за анон тайм, надеюсь, вы смогли задать все интересующие вас вопросы! Поставьте реакцию, если вам понравился подобный формат. Чем больше реакций - тем скорее мы сможем его повторить, ведь именно вы - основа СОКа! Результаты интерактива будут утром #щп
custom 52512734183634119594custom 52517044913460116763custom 52515438037345621702custom 52512529872039829581custom 52515771842203900011
ЗАКРЫТ!! 🩸🩸🩸🩸🩸🩸🩸🩸🩸🩸🩸 🤩🤩Я не бог, но, поверь мне, все за тебя отдам. . . 🤩🤩 ➖➖➖ 「🤩 С МЕНЯ:: ݁ ֢ 𝟏.⸼۫ Какой вы странный вопрос для начала диалога ݁ ֢ 𝟐.⸼۫ Какая песня Лазарева ассоциируется с вами ݁ ֢ 𝟑.⸼۫ Какой вы вкус сока ➖➖➖ 「🤩 УСЛОВИЯ УЧАСТИЯ:: ݁ ֢ 𝟏.⸼۫ Репост этого поста к себе на канал ݁ ֢ 𝟐.⸼۫ Написать от лица канала/оставить ссылку на канал в коммен…
custom 52512734183634119592custom 52515771842203900011
Posted without readable text
🤩🤩🩸🩸🩸 🩸🩸🩸🩸🩸 🤩 Я нᴇ ʍᴏᴦу ʍᴏᴧчᴀᴛь, нᴇ ʍᴏᴦу. . . В предвкушении лета, которое наступило всего день назад, нескольким кмщикам был задан вопрос 🤩 Что вы любите больше 🤩🩸🩸🩸🩸🩸🩸🩸🩸🩸 или 🩸🩸🩸🩸🩸🩸🩸?? УЧАСТНИКИ У нас имеется 22 человека, ответивших на вопрос, присланный им в анон! Давайте поблагодарим этих людей за возможность создать данный пост. Пич ➛ @Peachtreebanners Флур…
custom 52515771842203900017custom 52512067819458135206custom 52512734183634119596custom 52515438037345621703custom 52512529872039829581custom 52515024775592426131custom 52515503965093606981custom 52517044913460116761
🩸🩸🩸🩸🩸🩸🩸🩸🩸🩸 🤩 И нᴇ ɜнᴀя чᴛᴏ ᴨᴏᴛᴏʍ, нᴇ ɜнᴀя чᴛᴏ ᴨᴏᴛᴏʍ я ᴏᴨяᴛь бᴇᴦу. . . 🤩🤩🤩🤩➖➖➖ Вас приветствует новый проект с нетипичной тематикой, но тесно связанный со всеми комьюнити. Добро пожаловать в 🩸🩸🩸- 🩸🩸🩸🩸🩸🩸 🩸🩸 Или просто СОК в сокращении ➡️ Прочитать об особенностях проекта 🤩🤩🤩🤩➖➖➖ Создатель, руководитель и предводитель данного цирка - @LazarevCOK_bot 🤩 Псевдоним и маскот …
custom 52512067819458135201custom 52512734183634119591custom 52515024775592426131custom 52515771842203900011
Channel created
Showing the 12 most recent of 12 posts we hold for @SocialQuestionsCM_COK. 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@SocialQuestionsCM_COK named 8 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“८ ୧ ʿ ᜔Ꮯᴏц-ᴏᴨᴩᴏᴄы км || #𝘾𝙊𝙆 ୨ 」” (@SocialQuestionsCM_COK), 45 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/SocialQuestionsCM_COK.
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.