Telegram RegisterThe public register of Telegram
Telegram profile photo for cutieskie

Channel

cutieskie

@cutieskie

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

4subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001855500817
TypeChannel
Username@cutieskie
DescriptionНачало 11.02.2023
Created11 February 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded13 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/cutieskie

Growth

47 August 2026 — 4 subscribers13 August 2026 — 4 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:164no change
7 Aug 2026, 19:494first reading

Engagement

13 posts held, back to 8 May 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 posts for this entry, the most recent from 10 June 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
343
Videos
72
Links
76

Lifetime counters from Telegram’s own channel header, read 13 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.

Video runtime
4s
Average length
2s

Measured directly from 2 videos 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

25 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 28.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘728.0%
🍓624.0%
520.0%
❤‍🔥416.0%
28.00%
🆒14.00%

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 11 of the 13 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 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 8 May 2023 to 10 June 2023, 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

10 Jun 2023, 14:15 UTC152 views1 reactionsread 13 August 2026

Мы уходим на другой канал,юз: @YomiTsuchi Если есть желание заключить союз,пишите мне в лс @Restwith Максимальная подписка 6х6 #cutierp

🍓1

Signed 리미연

5 Jun 2023, 09:22 UTC191 views1 reactionsread 13 August 2026
Video

Ровно через месяц мы выходим из реста. В честь этого мы решили провести полную перезагрузку. Что будет изменено(?) ВСЁ -Оформление -Навигация -Оформление анкет -Юз -Оформление поста И другие мелочи. Мы благодарны всем,кто остался и дождался нас,рады сотрудничеству и поздравляем с началом нашей новой Эры #cutierp

1

Signed .

27 May 2023, 14:48 UTC308 views7 reactionsread 13 August 2026

Здравствуйте,наш доп сменил юз Был @Kolouiu Стал @Molopipilop #cutierp

2🍓21❤‍🔥1💘1

Signed .

27 May 2023, 14:19 UTC131 views1 reactionsread 13 August 2026
Forwarded from @akbozatovyPhoto

миледи акбозатова манчестер увидела @Restwith и они сдружились во время съемок @akbozatovy -> @cutieskie

1

Signed .

27 May 2023, 10:08 UTC80 views2 reactionsread 13 August 2026
Forwarded from @anderovyVideo

@anderovy 𝒏𝒆𝒘 𝒖𝒏𝒊𝒐𝒏 @cutieskie #Anderovy — #goha🤍— #5×5

1💘1

Signed .

25 May 2023, 15:52 UTC93 viewsread 13 August 2026

@Comfort_fm заключили союз с @cutieskie

Signed .

24 May 2023, 12:11 UTC117 views1 reactionsread 13 August 2026

Разрыв: @LEBRONSFML Причина: закрытие #cutierp

💘1

Signed .

24 May 2023, 12:09 UTC355 views2 reactionsread 13 August 2026

Ищем союзы,4х4 подписка,папка вз Писать: @Restwith #cutierp

❤‍🔥1💘1

Signed .

24 May 2023, 12:08 UTC352 views3 reactionsread 13 August 2026

Нам срочно нужны админы,которые будут идти допами к подписке,обращаться к @Restwith либо в наш бот #cutierp

❤‍🔥1🍓1💘1

Signed .

9 May 2023, 18:15 UTC157 views2 reactionsread 13 August 2026
Forwarded from @shutovskieePhoto

‼️‼️СРОЧНО‼️‼️ дорогие союзники Виена ( @chbvien) прошу проверить, есть ли в этих списках. если нет, то прошу отметиться в комментариях и написать юз клана и папку, в которой вы находитесь у нас. проблема в том, что в моем союз-листе где то союзов 60 с чем-то, а в папках суммарное количество ≈57. я не могу понять, чьи кланы я не добавил в папки. #𝙎𝙃𝙐𝙏𝙊𝙑𝙎𝙆𝙄𝙀ᴿᴾ / ЭТО МЕГА ВАЖНО, ИБО У МЕНЯ ГОЛОВА УЖЕ БОЛИТ ИЗ ЗА СВОЕЙ

🍓1💘1

Signed .

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

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

“cutieskie” (@cutieskie), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cutieskie.

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.