Telegram RegisterThe public register of Telegram
Telegram profile photo for орууу

Channel

орууу

@sweetcandyll

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

1subscribers

-93 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-1003875800346
TypeChannel
Username@sweetcandyll
Created4 April 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/sweetcandyll

Growth

19447.58 August 2026 — 94 subscribers9 August 2026 — 94 subscribers15 September 2026 — 1 subscribers8 August 202615 September 2026
3 measurements spanning 39 days, net -93. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:571-93
9 Aug 2026, 13:1594no change
8 Aug 2026, 03:5094first reading

Engagement

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

Reaction mix

89 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 25.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54069057931716964902325.8%
custom 52089463352727043421820.2%
custom 54069991614657453131719.1%
custom 52107134437320723401618.0%
custom 520869367523158586188.99%
custom 521118333462908953577.87%

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

Measured over the 18 most recent posts we hold, published 4 April 2026 to 2 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

2 Aug 2026, 14:06 UTC39 viewsread 9 August 2026

кицики, продаю этот канал за 70 руб, писать : @al3xisaev

19 Jul 2026, 06:54 UTC71 viewsread 9 August 2026
Forwarded from @quietbloomwy

̣ ۫ ᮫𝅼ܴ ꨭ𐇽֢۫𝓗ꨭ𐇽֢۫✿𝆬ϐׁꨭ𐇽֢۫ыйׁ֪᪾ׁ᪾ пᰮࣲꨵ࣪𑀼ۢᨡ‌࣮ׄ‌⃪⃪۟ຼк 𝐜ꨭ𐇽֢۫к⃪࡙᪾ֿؗаꨵ࣪𑀼ۢчꨭ⃪ࣰᨡ‌࣮ׄ‌⃪т⃪ۭ۫‌ь #emu ⦂ #sekai #otori

16 Jul 2026, 20:56 UTC95 viewsread 9 August 2026

привет, извините что поздно пишу у нас переезд в этот канал : @purina_sy , там публикуются символы , и скоро будут паки от меня 🥹❤️

19 Jun 2026, 13:39 UTC200 views6 reactionsread 9 August 2026

. ОГО спасибо за 100 подписчиков !! Здравствуйте милые !!. канал откроется уже в июле , скоро снова будет обычная деятельность и будут паки

custom 52089463352727043426

11 Jun 2026, 13:25 UTC243 views6 reactionsread 9 August 2026

добрый вечер мои милашки , я хотела вам предложить свой канал (кликабельно) по символам который я сделала с подругой , там я более активна !!. кто зайдет сразу получает обнимашки ~(˘▾˘~)

custom 52089463352727043424custom 52107134437320723402

3 Jun 2026, 15:48 UTC285 views7 reactionsread 9 August 2026

БЛИН , пр канал закрываеца , наверное в августе откроЮ извиниеь

custom 52107134437320723406custom 52089463352727043421

27 May 2026, 11:13 UTC363 views9 reactionsread 9 August 2026

но пак сделаю !!!!!!!

custom 52089463352727043425custom 52107134437320723404

27 May 2026, 11:13 UTC345 views13 reactionsread 9 August 2026

пр.ВЕТ ,,, я влзьму рест до конца мая , мне плохо сильно , пака

custom 52086936752315858618custom 52111833346290895355

18 May 2026, 11:10 UTC414 views9 reactionsread 9 August 2026

̣ ۫ ᮫𝅼ܴ ꨭ𐇽֢۫𝙷𐇽࣫𝆬𖹭ϐׁꨭ𐇽֢۫ыйׁ֪᪾ׁ᪾ 𐓣ׅ‌፝֟ᨡ‌࣮ׄ‌⃪ӄ᪶ ! #emoji #sekai 🤍🤍̣ ۫ ᮫𝅼ܴ𝚍𐇽࣫𝆬✿ֵ𝚠⃪᳟᳟᳟𝚗ׁ֪᪾ׁ᪾𝚕ꨭ𐇽֢۫✿ֵᨡ‌࣮ׄ‌⃪𝚍

custom 54069057931716964904custom 52107134437320723403custom 54069991614657453132

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

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

“орууу” (@sweetcandyll), 1 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/sweetcandyll.

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.