Telegram RegisterThe public register of Telegram
Telegram profile photo for CuarDDe ff

Channel

CuarDDe ff

@cuarddeff

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

705subscribers

+33 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002075354845
TypeChannel
Username@cuarddeff
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/cuarddeff

Growth

672705688.58 August 2026 — 672 subscribers9 August 2026 — 673 subscribers16 August 2026 — 684 subscribers24 August 2026 — 698 subscribers1 September 2026 — 705 subscribers8 August 20261 September 2026
5 measurements spanning 24 days, net +33. 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 667–710 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 02:46705+7
24 Aug 2026, 03:25698+14
16 Aug 2026, 08:58684+11
9 Aug 2026, 00:50673+1
8 Aug 2026, 02:49672first reading

Engagement

17 posts held, back to 30 July 2024the 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 17 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 15s
Average length
45s

Measured directly from 3 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

295 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 54.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16154.6%
💊11037.3%
🍌175.76%
💔72.37%

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

Measured over the 17 most recent posts we hold, published 30 July 2024 to 22 July 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

29 May 2026, 14:00 UTC≈1,520 views43 reactionsread 8 August 2026
Photo

ИДЕАЛ NC-17 / Завершён Фэндом: stray kids Пэйринг и персонажи: Ли Минхо/Хан Джисон, Хан Джисон/Ли Минхо, Хван Хёнджин, Со Чанбин, Ян Чонин, Бан Чан Размер: 347 страниц, 106 674 слова Метки: AU Hurt/Comfort Великобритания Дизайнеры Дружба Жаргон Италия Любовь/Ненависть Модели Модельеры Модельный бизнес Нежный секс Ненависть к себе Нецензурная лексика Отклонения от канона Повседневность Психология Ревность Рейтинг за

31💊12

29 May 2026, 13:56 UTC≈1,220 views6 reactionsread 8 August 2026
Forwarded from @msssenaiVideo

🅰️🅰️🅰️✨🅰️ @cuardde✈️

4💊2

29 May 2026, 13:55 UTC≈1,200 views8 reactionsread 8 August 2026
Video

с днем эдита для кьюрди, на который я убила 5 дней...))))) всем счастливого 2к18!!!🧛

💊53

29 May 2026, 13:52 UTC≈1,080 views10 reactionsread 8 August 2026
Forwarded from @cuarddePhoto

и д е а л — info 🤩🤩🤩🌎🤩🌟💋 так как эта работа нынче живёт своей жизнью, я предлагаю немного упорядочить здесь всю информацию которая у нас есть, касаемо неё. 🌟 #визуалидеал — весь зрительный контент который не несёт в себе сюжетных спойлеров (внешность персонажей, эстетика) 🌟 #разборидеал — любая информация дополняющая сюжет, объясняющая и раскрывающая его 🌟 #идеал — всё вышеперечисленное в куче и ещё немного юмора

💊64

15 Aug 2024, 15:15 UTC≈2,400 views18 reactionsread 8 August 2026
File

File, posted without a caption

14💊3🍌1

15 Aug 2024, 15:15 UTC≈2,320 views17 reactionsread 8 August 2026

обложка: https://t.me/soon_doon_dory/4686

13🍌4

15 Aug 2024, 15:14 UTC≈2,040 views19 reactionsread 8 August 2026
Photo

что-то между тараканом и феей фб: https://ficbook.net/readfic/019150fb-4de2-7264-892f-97b4159427de Stray Kids G Завершён Пэйринг и персонажи: Ли Минхо/Хан Джисон, Бан Чан, Ким Сынмин, Ли Феликс, Со Чанбин, Хван Хёнджин, Ян Чонин, ОЖП, ОМП Размер: 11 страниц, 1 часть Метки: AU; Hurt/Comfort; Вымышленные существа; Люди; Повседневность; Стёб; Флафф; Фэнтези; Экшн; Юмор Описание: Минхо увидел другую, более ма

19

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

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

“CuarDDe ff” (@cuarddeff), 705 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/cuarddeff.

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.