Telegram RegisterThe public register of Telegram
Telegram profile photo for Ruin_Cherub

Channel

Ruin_Cherub

@Ruined_Cherub_Channel

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

111subscribers

+15 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003604267409
TypeChannel
Username@Ruined_Cherub_Channel
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/Ruined_Cherub_Channel

Growth

96111103.59 August 2026 — 96 subscribers9 August 2026 — 96 subscribers16 August 2026 — 98 subscribers1 September 2026 — 109 subscribers10 September 2026 — 111 subscribers9 August 202610 September 2026
5 measurements spanning 32 days, net +15. 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 94–113 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 17:02111+2
1 Sept 2026, 00:16109+11
16 Aug 2026, 14:3698+2
9 Aug 2026, 12:0296no change
9 Aug 2026, 07:4696first reading

Engagement

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

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52175147134238385627827.1%
custom 52199742736905328656522.6%
custom 54292377247353690745920.5%
custom 54138625020248998873913.5%
custom 54655697077907247773512.2%
custom 521994359044416936182.78%
custom 546332925098565640341.39%

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

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

7 Aug 2026, 19:44 UTC31 views9 reactionsread 9 August 2026
Forwarded from @MichaelcucumberPhoto

Photo, posted without a caption

custom 54138625020248998875custom 52175147134238385624

7 Aug 2026, 19:40 UTC36 views7 reactionsread 9 August 2026
File

File, posted without a caption

custom 52175147134238385625custom 54138625020248998872

5 Aug 2026, 19:03 UTC50 views14 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 54138625020248998878custom 52199742736905328653custom 54292377247353690742custom 52175147134238385621

2 Aug 2026, 05:25 UTC100 views17 reactionsread 9 August 2026
File

File, posted without a caption

custom 54138625020248998878custom 54292377247353690744custom 52199435904441693613custom 52175147134238385622

31 Jul 2026, 21:03 UTC114 views36 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 521997427369053286518custom 52175147134238385629custom 54292377247353690747custom 52199435904441693611custom 54655697077907247771

25 Jul 2026, 08:54 UTC137 views14 reactionsread 9 August 2026
File

File, posted without a caption

custom 52175147134238385627custom 52199742736905328655custom 54292377247353690742

24 Jul 2026, 09:32 UTC188 views22 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 521997427369053286514custom 52175147134238385624custom 54292377247353690744

22 Jul 2026, 19:14 UTC165 views9 reactionsread 9 August 2026

You know, I can't forget your movements, how you touch me from below and tear away the last virgin pieces from me. I will be exhausted, but will wait bitterly for your further actions, something condescending..🪽

custom 52175147134238385629

22 Jul 2026, 16:31 UTC163 views10 reactionsread 9 August 2026
File

File, posted without a caption

custom 54633292509856564034custom 52175147134238385622custom 54138625020248998872custom 54292377247353690742

20 Jul 2026, 19:27 UTC187 views25 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 546556970779072477712custom 52175147134238385626custom 54292377247353690744custom 52199742736905328653

19 Jul 2026, 04:40 UTC157 views12 reactionsread 9 August 2026

I regret trying to offer help, but then I suffer myself.

custom 54655697077907247776custom 52199742736905328653custom 54138625020248998872custom 52175147134238385621

18 Jul 2026, 18:40 UTC167 views11 reactionsread 9 August 2026
File

File, posted without a caption

custom 52199742736905328655custom 52199435904441693612custom 54292377247353690742custom 52175147134238385621custom 54138625020248998871

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

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

“Ruin_Cherub” (@Ruined_Cherub_Channel), 111 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Ruined_Cherub_Channel.

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.