Telegram RegisterThe public register of Telegram
Telegram profile photo for Калейдоскоп | 2 Сезон

Channel

Калейдоскоп | 2 Сезон

@Kaleidoscop_mc

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

192subscribers

+15 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-1003565038062
TypeChannel
Username@Kaleidoscop_mc
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/Kaleidoscop_mc

Growth

177194185.59 August 2026 — 177 subscribers9 August 2026 — 177 subscribers16 August 2026 — 184 subscribers24 August 2026 — 188 subscribers31 August 2026 — 193 subscribers9 September 2026 — 194 subscribers19 September 2026 — 192 subscribers1929 August 202619 September 2026
7 measurements spanning 41 days, net +15. 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 174–197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 09:35192-2
9 Sept 2026, 21:56194+1
31 Aug 2026, 22:08193+5
24 Aug 2026, 22:37188+4
16 Aug 2026, 21:44184+7
9 Aug 2026, 23:41177no change
9 Aug 2026, 13:03177first reading

Engagement

20 posts held, back to 25 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 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
26s
Average length
26s

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.

Reaction mix

61 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 65.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4065.6%
🔥914.8%
👎46.56%
👍23.28%
🕊23.28%
🎉11.64%
💩11.64%
🤡11.64%
🥴11.64%

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 14 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 61 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 25 June 2026 to 5 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

5 Aug 2026, 10:36 UTC431 views8 reactionsread 9 August 2026
Photo

На сервере орудует НЕИЗВЕСТНЫЙ В МАСКЕ Он произвёл ограбление на спавне, украв 47 аров и скрывшись в неизвестном направлении На данный момент главный подозреваемый - Контур🤑 Однако МАКСИВИН🤑 ВЫЗВАЛСЯ РАССКРЫТЬ ЭТО ДЕЛО клип - https://www.twitch.tv/maksivin21/clip/WrongFastVampireYouWHY-G9Hb7cwHpJIrwdDR 📱 @Kaleidoscop_mc | 📱 Discord

7👎1

4 Aug 2026, 17:59 UTC99 views2 reactionsread 9 August 2026
Forwarded from @gatastrophic

Posted without readable text

🎉1🥴1

23 Jul 2026, 18:36 UTC417 views7 reactionsread 9 August 2026
Photo

АЙ, В ГЛАЗ ЧТО-ТО ПОПАЛО! А вы замечали что людей грибами не корми, да подай зрелищ каких-нибудь? Вот именно так решили наши друзья Дикс 🤑 и Лантоик 🤑 объевшись грибов и решили оформить документы на свою организацию — ИСКРА, выпустив так же своё обращение. Так же наших друзей не устраивает коренное население Калейдоскопа в виде эндерменов, но знаете, меня тоже не устраивает их чёрная задница. Мне лишь интересно, ка

5🕊2

22 Jul 2026, 19:29 UTC563 views2 reactionsread 9 August 2026
Photo

А можно потрогать ваши глазки? Ладно-ладно, это шутка. У нас отличная новость! Игроки Калейдоскопа начали возвращать частично своё зрение, из замеченых игроков что вернули своё зрение: 🤑 Абиля 🤑 БлуБан 🤑 Грибомор 🤑 ДропВА 🤑 ДомБезКрыши 🤑 Зинга 🤑 Кириллич 🤑 ПСб 🤑 Сэмпи 🤑 Эквай 🤑 Элис Вимсвуд Занимаются же лечением глаз Сэмпи 🤑 и Кириллич 🤑 в своей уютной клинике путём пересадки их от различных существ. А ВАШИ глаза

2

10 Jul 2026, 17:26 UTC670 views3 reactionsread 9 August 2026

Адский страж, созданный обезумевшим миром для дезинтеграции путников прошедших в ад забрал следующих людей: Блубан 🤑 Руфок 🤑 Элис 🤑 Нэмурес 🤑 Абиля 🤑 Дикс🤑 Лантоик🤑 Кармичелли🤑 Балдаша👀 Ему оставалось убить одного игрока, что бы заполучить возможность войти в обычный мир Однако, восставший из пепла Руфок🤑 смог одолеть извращенную пародию на человека. Заполучив легендарную броню с первого сезона КЛИП - https://www

🔥2👎1

10 Jul 2026, 14:51 UTC407 viewsread 9 August 2026

Стримы: Кибер🤑 Блубан🤑 Дикс🤑 Кармичлени🤑 Зиннга🤑 Балдаша👀 📱 @Kaleidoscop_mc | 📱 Discord

10 Jul 2026, 14:03 UTC304 views1 reactionsread 9 August 2026
Photo

Готовы ли вы к НАСТОЯЩЕМУ АДУ?😡 Надеюсь, вы понимаете, что так легко ничего не будет. Как и в Верхнем мире мы не одни... В аду за вами будет охотиться настоящее дитя нашего МИРА, облаченное в легендарную броню прямо из прошлого сезона¹. Которую вы можете получить, убив его. Чтобы попасть на основной сервер, мофагу нужно убить 10 разных игроков за 1 час. Помогать или нет - решать уже вам). Удачи! 1. Легендарная бр

1

10 Jul 2026, 10:45 UTC346 views2 reactionsread 9 August 2026
Photo

Сегодня ОТКРЫТИЕ АДА🔥 Момент достаточно знаменательный и долгожданный Из интересного: Игрокам в лс писали люди с зашифрованными никами, с просьбой вытащить их из ада В журнале призмлаунчера они были подписаны как грешники😨 За людьми начали наблюдать огромные человеческие глаза👀 Люди начали лечить дальтонизм хирургическим путём😳 У меня закончились смайлики для оформления постов🖕 📱 @Kaleidoscop_mc | 📱 Discord

2

5 Jul 2026, 20:19 UTC351 viewsread 9 August 2026
Photo

Калейдоскоп триггеры🥳 Неофициальный ТГК где зрители|игроки могут анонимно делится негативном по отношению к нашему серверу🤓 С каждого МИНИМУМ по одному оскорблению блубана (ЭТО Я) !!! https://t.me/kaleidoscopetriggers 📱 @Kaleidoscop_mc | 📱 Discord

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Калейдоскоп | 2 Сезон” (@Kaleidoscop_mc), 192 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Kaleidoscop_mc.

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.