Telegram RegisterThe public register of Telegram
Telegram profile photo for cheese nyang

Channel

cheese nyang

@rickymybeloved

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

968subscribers

-2 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-1001830877733
TypeChannel
Username@rickymybeloved
Created5 January 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/rickymybeloved

Growth

9689709697 Aug 2026, 19:58 — 970 subscribers8 Aug 2026, 00:46 — 970 subscribers8 Aug 2026, 19:08 — 968 subscribers7 Aug 2026, 19:588 Aug 2026, 19:08
3 measurements taken within a single day, net -2. 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 968–970 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:08968-2
8 Aug 2026, 00:46970no change
7 Aug 2026, 19:58970first reading

Engagement

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

What this channel posts

Video runtime
1m 08s
Average length
23s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1,063 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 98.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,04598.3%
custom 5258088882922078340181.69%

Custom emoji. One 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 count beside it isTelegram’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 14 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 1,063reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 24 April 2026 to 14 June 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

14 Jun 2026, 19:24 UTC835 views87 reactionsread 8 August 2026

мягких облачков ымппаппе ((

84custom 52580888829220783403

14 Jun 2026, 19:24 UTC676 views99 reactionsread 8 August 2026
Forwarded from @dear_gyuvinVideo

кажется, ппаппа умерла во вторник. первым человеком, которому кюбин рассказал об этом, был рики. кю знал, что именно он сможет понять его и посочувствовать. так и случилось: рики сразу же обнял и утешил его, что стало огромной поддержкой для кюби в тот тяжелый день :( даже не представляю, насколько ему было сложно справляться с таким плотным графиком, получить травмы и одновременно переживать потерю любимой ымппаппы

97custom 52580888829220783402

5 Jun 2026, 06:01 UTC886 views79 reactionsread 8 August 2026
Photo

🫧 # bubble update « удачи сегодня ! » « на этот раз это селка в зеркале » « 🙂‍↕️ »

78custom 52580888829220783401

28 May 2026, 07:34 UTC962 views81 reactionsread 8 August 2026
Photo

🫧 # bubble update « доброе утро ~ »

79custom 52580888829220783402

26 May 2026, 09:31 UTC756 views42 reactionsread 8 August 2026

https://youtu.be/m6kmpiOsLVk?si=yzyMDOTuArKgAqYM

41custom 52580888829220783401

20 May 2026, 09:31 UTC742 views81 reactionsread 8 August 2026
Video

чжан хао сказал, что в последнее время рики действительно стал более разговорчивым и легче делится своими мыслями, так что, хотя они знакомы уже давно, создается ощущение, что теперь они стали ближе друг к другу :(

80custom 52580888829220783401

19 May 2026, 16:20 UTC644 views63 reactionsread 8 August 2026
Photo

🎂🤍 # wevers update kr « сегодня наш день, хе хе. спасибо большое за поздравления 🥰 спасибо за то, что вы всегда рядом в этот день. я так рад, что мой день рождения и дата дебюта так близко друг к другу. давайте обязательно увидимся ! проведем этот прекрасный 520 день вместе весело 😘 » cn « мы вместе провели уже несколько дней рождений и каждый раз я чувствую к вам всё большую привязанность. спасибо за ваши поздравл

62custom 52580888829220783401

8 May 2026, 09:25 UTC730 views67 reactionsread 8 August 2026
Forwarded from @dear_gyuvinPhoto

sequence 01: curiosity - group & unit concept photo 'UNnatural' 🪨

66custom 52580888829220783401

7 May 2026, 09:20 UTC807 views78 reactionsread 8 August 2026
Photo

sequence 01: curiosity - ' unnatural '

77custom 52580888829220783401

29 Apr 2026, 20:17 UTC991 views89 reactionsread 8 August 2026
Video

boy why you so cat

88custom 52580888829220783401

29 Apr 2026, 20:15 UTC860 views81 reactionsread 8 August 2026
Photo

Photo, posted without a caption

80custom 52580888829220783401

25 Apr 2026, 10:19 UTC833 views74 reactionsread 8 August 2026
Photo

💬 # wevers update « покажу вам, потому что думаю, что всем было интересно ~ »

73custom 52580888829220783401

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

Citation-graph rank

Citation-graph rank — 1,067,344 of 1,481,217entries 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.

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.

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

“cheese nyang” (@rickymybeloved), 968 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/rickymybeloved.

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.