Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐂𝘩𝖾𝖾ɾі𝐨𝘴 ৎ୭ 𝐂𝐯ɠ 🧀

Channel

𝐂𝘩𝖾𝖾ɾі𝐨𝘴 ৎ୭ 𝐂𝐯ɠ 🧀

@cheeriosoi

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

48subscribers

-3 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-1004482328987
TypeChannel
Username@cheeriosoi
CreatedBetween 1 June 2026 and 23 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live29 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/cheeriosoi

Growth

485149.57 August 2026 — 51 subscribers10 August 2026 — 51 subscribers22 August 2026 — 50 subscribers29 August 2026 — 48 subscribers7 August 202629 August 2026
4 measurements spanning 22 days, net -3. 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 48–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 11:1448-2
22 Aug 2026, 08:5750-1
10 Aug 2026, 11:0151no change
7 Aug 2026, 19:4051first reading

Engagement

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

Reaction mix

67 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 49923656687047155711420.9%
custom 50915081683248094021319.4%
custom 53328130890100978891319.4%
custom 52695918704926635351217.9%
custom 5474617941163008084913.4%
custom 529440655514640827034.48%
custom 532795329056501743822.99%
custom 519062679651669372411.49%

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

Measured over the 20 most recent posts we hold, published 23 July 2026 to 6 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

6 Aug 2026, 07:48 UTC28 viewsread 10 August 2026
Forwarded from @feyra_proddPhoto

🎀𝖥𝖤𝗬𝖱𝗔𝗔 ( 𝗉𝗋ꪮ𝖽 )) *🦊🦊 best prodd 🔥 🤩zZz . 𝖼𝗈𝕞𝗉𝖾𝘁𝗂𝗍𝗂𝗈𝗇 🎃 ✷ 🍃 ➖ с сегодняшне𝗀о д𝗇я 🎀🎀 з͟апускается конку𝗉с телеграмм 🔥🎀🎀🎀премиу𝗆а на 3 меся͟ца 🔥 для участ͟ия в кон𝗄𝗒рсе от в𝖺с 🔥🔥🔥🔥треб𝗒𝖾тся 🤩🎀🎀 подп𝗎𝖼𝗄а на данный тгк (@feyra_prodd) реп𝗈𝖼т в свой 𝗄𝖺нал/три пиар чат𝖺 ꪆ୧ . 🎃 나는 ° 🤩 ︵ ࿐ 𝓐 𝗎𝗍𝗎𝗆𝗇 𝗏𝗂𝖻𝖾? 𝖸𝖾𝖺𝗁 --- 🍁 !! 𝘁𝗵𝗲 producer 🤩 Ho𝐦e | 快適

5 Aug 2026, 17:50 UTC37 viewsread 10 August 2026

Давате, оформлять тупо не смогу ❤️❤️ @cheeriosoi_bot

5 Aug 2026, 17:30 UTC40 viewsread 10 August 2026

я разочарованна, меня никто из участниц не поздравил

4 Aug 2026, 19:26 UTC45 views12 reactionsread 10 August 2026

Happy Birthday to me! 🎂 (жду пока участницы что то сделают)

custom 52695918704926635355custom 52944065551464082703custom 53328130890100978893custom 50915081683248094021

31 Jul 2026, 06:19 UTC84 views11 reactionsread 10 August 2026
Photo

Сегодня 31 июля, это значит что у нашей энойи сегодня день рождения! 🎂 Мы всей командой очень любим энойю, она принесла нам много радости и счастья! Поздравляем тебя наша сладкая девочка, ты стала на год больше, желаем успехов в твоих начинаниях. Пусть каждый день приносит тебе новые возможности и радостные моменты. Желаем здоровья, успехов в работе и, конечно, много приятных сюрпризов в жизни! Мы очень хотим что б

custom 49923656687047155715custom 50915081683248094023custom 52695918704926635353

24 Jul 2026, 09:33 UTC145 views29 reactionsread 10 August 2026

к сожалению тримиллия не отвечает нам. мы выберем одну кандидатку на её место

custom 49923656687047155719custom 53328130890100978899custom 50915081683248094027custom 54746179411630080844

23 Jul 2026, 16:16 UTC156 views1 reactionsread 10 August 2026

может реально уйти

custom 53328130890100978891

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

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

“𝐂𝘩𝖾𝖾ɾі𝐨𝘴 ৎ୭ 𝐂𝐯ɠ 🧀” (@cheeriosoi), 48 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/cheeriosoi.

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.