Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐂𝐀𝐍𝐃𝐘

Channel

𝐂𝐀𝐍𝐃𝐘

@candyyuo

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

6subscribers

+0 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002100199739
TypeChannel
Username@candyyuo
Created21 February 2024measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live14 September 2026
Measurements held2
Confirmed unchanged5 times, most recently 14 September 2026
On Telegramt.me/candyyuo

Growth

615 Aug 2026, 08:31 — 6 subscribers16 Aug 2026, 04:58 — 6 subscribers15 Aug 2026, 08:3116 Aug 2026, 04:58
2 measurements taken within a single day. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 04:586no change
15 Aug 2026, 08:316first reading

Engagement

8 posts held, back to 21 February 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 8 posts for this entry, the most recent from 14 March 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

48 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 27.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52492140287895939291327.1%
custom 53437750395504103561327.1%
custom 53975723267263191181225.0%
custom 54201415552330713411020.8%

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

Measured over the 8 most recent posts we hold, published 21 February 2024 to 14 March 2025, 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

14 Mar 2025, 12:56 UTC42 views7 reactionsread 15 August 2026

🔫🔫🔫🔫🔫 🎀 press the button 🎀

custom 52492140287895939292custom 53437750395504103562custom 53975723267263191182custom 54201415552330713411

Signed вор в законе

14 Mar 2025, 12:41 UTC43 views7 reactionsread 15 August 2026

🔫🔫🔫🔫🔫 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤍𝐜𝐫𝐮𝐬𝐡 𝐥𝐢𝐬𝐭 🖤𝐛𝐥𝐚𝐜𝐤𝐥𝐢𝐬𝐭 ❤️ 𝐫𝐞𝐝 𝐥𝐢𝐬𝐭 ᥰ᧐ρяд᧐κ нᥱ ᥙʍᥱᥱᴛ ɜнᥲчᥱнᥙя!

custom 52492140287895939292custom 53437750395504103562custom 54201415552330713412custom 53975723267263191181

Signed вор в законе

14 Mar 2025, 12:41 UTC39 views7 reactionsread 15 August 2026
Photo

🔫🔫🔫🔫🔫🔫 👑 𝐨𝐰𝐧𝐞𝐫— @silsilia 👑 𝐜𝐨𝐨𝐰𝐧𝐞𝐫— @s1mplenv 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🎀 𝐧𝐞𝐰— 🎀 𝐜𝐡𝐚𝐭— 🎀 𝐯𝐢𝐝𝐞𝐨— @bmwe39arm 🎀 𝐚𝐜𝐭𝐢𝐯𝐞— 🎀 𝐮𝐧𝐢𝐨𝐧— 🌟𝐚𝐛𝐨𝐮𝐭 𝐚𝐝𝐦𝐢𝐧𝐢𝐬𝐭𝐫𝐚𝐭𝐢𝐨𝐧🌟

custom 52492140287895939292custom 53437750395504103562custom 53975723267263191182custom 54201415552330713411

Signed вор в законе

14 Mar 2025, 12:41 UTC40 views7 reactionsread 15 August 2026

🔫🔫🔫🔫🔫🔫🔫🔫 🌟 🌟 🌟 🌟 🌟 🌟 на русском: кэндивская/кэндивский кнд кэнди на английском: candy cnd cd если нет возможности вставить инициалы в ник/био буквами, то можно использовать эмодзи с конфетой

custom 53437750395504103562custom 53975723267263191182custom 54201415552330713412custom 52492140287895939291

Signed вор в законе

14 Mar 2025, 12:41 UTC33 views6 reactionsread 15 August 2026
Photo

🔫🔫🔫🔫🔫 🎀𝐜𝐡𝐚𝐭 𝐫𝐮𝐥𝐞𝐬🌟🎀𝐮𝐧𝐢𝐨𝐧 𝐫𝐮𝐥𝐞𝐬

custom 52492140287895939292custom 53975723267263191182custom 53437750395504103561custom 54201415552330713411

Signed вор в законе

14 Mar 2025, 12:41 UTC30 views6 reactionsread 15 August 2026
Photo

🔫🔫🔫🔫🔫🔫🔫🔫🔫🔫 🤩𝙥𝙖𝙩𝙚𝙣𝙩 🤩𝙧𝙪𝙡𝙚𝙨 🤩𝙖𝙙𝙢𝙞𝙣𝙞𝙨𝙩𝙧𝙖𝙩𝙞𝙤𝙣 🤩𝙖𝙧𝙘𝙝𝙞𝙫𝙚 🤩𝙘𝙝𝙖𝙩 𝙡𝙞𝙣𝙠 🤩𝙞𝙣𝙞𝙩𝙞𝙖𝙡𝙨 🤩𝙗𝙤𝙤𝙨𝙩 🤩𝙡𝙞𝙨𝙩𝙨 !ᥰᥱρᥱд ʙᥴᴛуᥰ᧘ᥱнᥙᥱʍ, ᥰ᧐дᥰᥙᥴᥲᴛьᥴя нᥲ κᥲнᥲ᧘ , ᥰ᧐ᥴᴛᥲʙᥙᴛь ᥙнᥙцᥙᥲ᧘ы ᥙ ᧐ɜнᥲκ᧐ʍᥙᴛьᥴя ᥴ ᥰρᥲʙᥙ᧘ᥲʍᥙ!

custom 53437750395504103562custom 54201415552330713412custom 52492140287895939291custom 53975723267263191181

Signed вор в законе

14 Mar 2025, 12:41 UTC27 views8 reactionsread 15 August 2026
Photo

🔫🔫🔫🔫🔫🔫 💖💖💖💖💖💖💖💖💖💖 нᥲɜʙᥲнᥙᥱ "CANDY" нᥲ ʙᥴᥱх яɜыκᥲх, ʙ᧐ ʙᥴᥱх ʙᥲρᥙᥲцᥙях ᥙ ᴛ.ᥰ. ᥰρᥙнᥲд᧘ᥱжᥙᴛ нᥲʍ ᥴ 02.01.24. 💖💖💖💖💖💖💖💖💖💖 ʙᥴᥱ κ᧘ᥲны, κɸ, ρ᧐᧘κᥙ ᥙ ᴛᥲκ дᥲ᧘ᥱᥱ ʍы ʙᥱж᧘ᥙʙ᧐ ᥰ᧐ᥰρ᧐ᥴᥙʍ ᥙɜʍᥱнᥙᴛь нᥲɜʙᥲнᥙᥱ, н᧐ ᥰρᥙʍᥱʍ нᥱ᧐δх᧐дᥙʍыᥱ ʍᥱρы, ᥱᥴ᧘ᥙ нᥲᥴ нᥱ уᥴ᧘ыɯᥲᴛ

custom 52492140287895939293custom 53437750395504103562custom 53975723267263191182custom 54201415552330713411

Signed вор в законе

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

Mentions

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.

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

“𝐂𝐀𝐍𝐃𝐘” (@candyyuo), 6 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/candyyuo.

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.