Telegram RegisterThe public register of Telegram
Telegram profile photo for Caseplay

Channel

Caseplay

@case_play

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

53subscribers

-2 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002965785563
TypeChannel
Username@case_play
Created17 August 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live1 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 1 September 2026
On Telegramt.me/case_play

Growth

53555411 August 2026 — 55 subscribers11 August 2026 — 55 subscribers17 August 2026 — 54 subscribers25 August 2026 — 53 subscribers11 August 202625 August 2026
4 measurements spanning 14 days, net -2. 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 53–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 07:3253-1
17 Aug 2026, 20:3554-1
11 Aug 2026, 16:3055no change
11 Aug 2026, 16:1655first reading

Engagement

6 posts held, back to 17 August 2025the 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 6 posts for this entry, the most recent from 4 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
23s
Average length
23s

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.

Recent posts

4 Dec 2025, 10:55 UTC148 viewsread 11 August 2026
Forwarded from @ucancityPhoto

👚 Кто больше закинет звёзд на этот пост, получит Плюш Acetornia + 50 звёзд на свой баланс 🌹 За 2 место - розочка за 25 ☪️ 🧸 За 3 место - мишка за 15 ☪️ 👀 Каждый участник аукциона, который поставит ставку в 15 и более звёзд получит Telegram-подарок «Мишку» 🧸 😏 Параллельно Аукциону, мы решили вас обрадовать и запустили Розыгрыш 🤖 Условия: 1. Быть подписанным на Укан City 🌆 2. Быть подписанным на Acetornia 3. Постав

27 Nov 2025, 20:03 UTC92 viewsread 11 August 2026
Forwarded from @ucancityVideo

«Вещь, которая была в каких-либо событиях становится частью воспоминаний» 🤩 25 ноября, канал «ГАЧИ-МУЧИ» попросил своих подписчиков рассказать о предмете, который ассоциируется с ними, их ответом был: баскетбольный мяч, и именно поэтому.. 🏀 Кто больше закинет звёзд на этот пост, получит баскетбольный мяч с автографами Укан City и ГАЧИ-МУЧИ + 50 звёзд на свой баланс 😏 Также, каждый участник аукциона, который внесет

25 Nov 2025, 20:00 UTC59 viewsread 11 August 2026
Forwarded from @ikutes

Today, our Teamgram Caseplay Mint team signed four partnership agreements. We'll be launching auctions soon – stock up on stars!

23 Nov 2025, 20:29 UTC71 viewsread 11 August 2026
Forwarded from @ucancityPhoto

🦄 Кто больше закинет звёзд на этот пост, получит шапку единорога + 50 звёзд на свой баланс 👀 Первый аукцион - это открытие чего-то нового. Участники этого аукциона - открыватели, каждый из них получит билет на закрытый прямой эфир + станет инсайдером будущих аукционов. 😏 Также, каждый участник аукциона, который внесет 15 и более звёзд - стопроцентно получит подарок за звёзды 🧸. ☪️ Звезды можно купить здесь - @star

Showing the 6 most recent of 6 posts we hold for @case_play. 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.

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

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

“Caseplay” (@case_play), 53 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/case_play.

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.