Telegram RegisterThe public register of Telegram

Channel

(РЕСТ у влд)☁️˖࣪ Rⲓⲋⲏⲉⲛⲕⲁ.Ⲥⳑⲟυⲇ Ⲣⲟʀⲧ𖥔 ࣪ ᥫ᭡

@CloudRi

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

17subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002948238299
TypeChannel
Username@CloudRi
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/CloudRi

Growth

1712 Aug 2026, 06:01 — 17 subscribers12 Aug 2026, 19:33 — 17 subscribers12 Aug 2026, 06:0112 Aug 2026, 19:33
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 16–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:3317no change
12 Aug 2026, 06:0117first reading

Engagement

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

Reaction mix

70 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 24.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53686618925396515571724.3%
custom 53706643995665724651724.3%
💘1217.1%
🕊811.4%
❤‍🔥57.14%
🐳34.29%
😢34.29%
22.86%
🆒22.86%
🍓11.43%

Custom emoji. 2 of the rows above are 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 areTelegram’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 14 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 70reactions 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 28 April 2026 to 6 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @CloudRi. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 28 April 2026 to 6 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Jul 2026, 15:02 UTC15 views1 reactionsread 12 August 2026

Пока была в ресте, очень много кто закрылся 😭 #разрыв

😢1

Signed 𝑅𝑖𝑠ℎ𝑎𐙚♡[𝐸𝑆𝐹𝑃] #𐙚Ⲩⲙ

23 May 2026, 14:10 UTC63 views3 reactionsread 12 August 2026

#союзники_репост (По желанию)

custom 53706643995665724652custom 53686618925396515571

Signed 𝑅𝑖𝑠ℎ𝑎𐙚♡[𝐸𝑆𝐹𝑃] #𐙚Ⲩⲙ

23 May 2026, 14:09 UTC82 views1 reactionsread 12 August 2026
Poll

Будет…

  1. Нью эра 😋22%
  2. Интерактив ⚡️17%
  3. Все сразу 🔥61%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

custom 53686618925396515571

Signed 𝑅𝑖𝑠ℎ𝑎𐙚♡[𝐸𝑆𝐹𝑃] #𐙚Ⲩⲙ

23 May 2026, 14:06 UTC54 views3 reactionsread 12 August 2026

[☁️] - Кстати, вот вам на раздумье пока я в ресте. Лучше сделать нью эру или какой нибудь интерактив?? Или может сразу все?? В нью эре я вообще планирую даже псевдоним поменять 💥 Как то так :)) А еще лучше все так оставить ахах

2custom 53706643995665724651

Signed 𝑅𝑖𝑠ℎ𝑎𐙚♡[𝐸𝑆𝐹𝑃] #𐙚Ⲩⲙ

23 May 2026, 07:35 UTCviews —

(РЕСТ у влд)☁️˖࣪ Rⲓⲋⲏⲉⲛⲕⲁ.Ⲥⳑⲟυⲇ Ⲣⲟʀⲧ𖥔 ࣪ ᥫ᭡ pinned «ВАЖНАЯ ИНФОРМАЦИЯ!! союзники, у меня тг очень плохо работает!! Я еле как сейчас пишу, не знаю когда еще смогу так написать!! Поэтому я возьму рест, не смогу репостить соо, очень прошу прощения!! Постараюсь вернутся скорее!! #важно #союзники_репост»

23 May 2026, 07:35 UTC58 views4 reactionsread 12 August 2026

ВАЖНАЯ ИНФОРМАЦИЯ!! союзники, у меня тг очень плохо работает!! Я еле как сейчас пишу, не знаю когда еще смогу так написать!! Поэтому я возьму рест, не смогу репостить соо, очень прошу прощения!! Постараюсь вернутся скорее!! #важно #союзники_репост

🕊2😢2

Signed 𝑅𝑖𝑠ℎ𝑎𐙚♡[𝐸𝑆𝐹𝑃] #𐙚Ⲩⲙ

19 May 2026, 09:18 UTC59 views10 reactionsread 12 August 2026
Photo

🤩 🤩ew 🤩ost | 🎁 🤩 • 🅰️rder / 🅰️ractice ❤️🥹🥹🌸🥹🥹🥹🕯 ➿➿➿➿➿➿➿➿➿➿➿ 🌫🌫 🌫🌫🌫🌫🌫🌫🌫 🎁 - баннер для моего порта :Р

custom 53706643995665724654custom 53686618925396515572❤‍🔥1🍓1💘1🕊1

Signed ㄍ 🪽 — 𝔐𝔯. 𝔖𝔰𝔢𝔣𝔦𝔯

19 May 2026, 09:17 UTC43 viewsread 12 August 2026
Sticker

Sticker, posted without a caption

Signed ㄍ 🪽 — 𝔐𝔯. 𝔖𝔰𝔢𝔣𝔦𝔯

13 May 2026, 18:34 UTC39 views5 reactionsread 12 August 2026
Photo

🤩 🤩ew 🤩ost | 🎁 🤩 • 🅰️rder / 🅰️ractice ❤️🥹🥹🌸🥹🥹🥹🕯 ➿➿➿➿➿➿➿➿➿➿➿ 🌫🌫 🌫🌫🌫🌫🌫🌫🌫 🎁 - мне с ней помогали ..

💘2custom 53686618925396515572🆒1

Signed ㄍ 🪽 — 𝔖𝔖𝔈𝔉𝔗ℜ“ 𝔖 #TSUSSEF #kD

13 May 2026, 18:33 UTC30 viewsread 12 August 2026
Sticker

Sticker, posted without a caption

Signed ㄍ 🪽 — 𝔖𝔖𝔈𝔉𝔗ℜ“ 𝔖 #TSUSSEF #kD

10 May 2026, 12:59 UTC48 views9 reactionsread 12 August 2026
Photo

🤩🤩🤩 🌟🌟ew 🤩 🌟ost 🌟 #баннер 🌩🌩🌩🌩🌩🌩 ➿🐈‍⬛ ➿🥹🔤🥹 🌸🥹🍭 🦷🦷🦷он мнение 🤩- мне на канал баннкр, горжусь 🤩🤩🤩🤩 ☺️любовью

custom 53686618925396515574🐳2🕊2custom 53706643995665724651

Signed ㄍ 🪽 — 𝔖𝔖𝔈𝔉𝔗ℜ“ 𝔖 #TSUSSEF

10 May 2026, 12:56 UTC45 viewsread 12 August 2026
Sticker

Sticker, posted without a caption

Signed ㄍ 🪽 — 𝔖𝔖𝔈𝔉𝔗ℜ“ 𝔖 #TSUSSEF

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

23 May 2026, 14:09 UTCAnonymous Poll18 voters

Будет…

  1. Нью эра 😋22%
  2. Интерактив ⚡️17%
  3. Все сразу 🔥61%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 28 April 2026 to 6 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 1,211,185 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 registered channels — 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“(РЕСТ у влд)☁️˖࣪ Rⲓⲋⲏⲉⲛⲕⲁ.Ⲥⳑⲟυⲇ Ⲣⲟʀⲧ𖥔 ࣪ ᥫ᭡” (@CloudRi), 17 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/CloudRi.

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.