Channel
@riri_yuji
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
177subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001991735639 |
|---|---|
| Type | Channel |
| Username | @riri_yuji |
| Created | Between 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/riri_yuji |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 21:15 | 177 | -1 |
| 9 Aug 2026, 14:13 | 178 | no change |
| 8 Aug 2026, 22:00 | 178 | first reading |
4 posts held, back to 20 April 2026 — the 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 4 posts for this entry, the most recent from 4 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
78 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 37.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 29 | 37.2% | |
| custom 5465280394498692130 | 14 | 17.9% | |
| ❤🔥 | 10 | 12.8% | |
| 💋 | 10 | 12.8% | |
| custom 5273886906508133889 | 6 | 7.69% | |
| custom 5312298418238930271 | 5 | 6.41% | |
| custom 5343919904502328315 | 1 | 1.28% | |
| custom 5384425981589090775 | 1 | 1.28% | |
| custom 5463046874065813291 | 1 | 1.28% | |
| 🕊 | 1 | 1.28% |
Custom emoji. 6 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 4 of the 4 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 78reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 20 April 2026 to 4 May 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.
давно подписана на этого парня , и мне нравится его разговорные видео не всегда я конечно с ним согласна , но это самые правильные слова , которые должна услышать и понять каждая
❤10custom 52738869065081338892💋1🕊1custom 53844259815890907751
воспоминания со вчерашнего дня 🌟💋 ну вот и стукнуло мне 21 , я решила что какого-то масштабного праздника делать не буду , а лучше соберу самых близких и спокойненько посидим . но даже с этим мой день прошёл очень ярко и был наполнен эмоциями . я так счастлива и словами не передать . спасибо большое всем за поздравления , а я побежала собираться на день рождения к другой львице тигрицы
❤9❤🔥6custom 54652803944986921306💋3
фотокарточки с дня рождения
❤7💋5custom 52738869065081338893❤🔥2custom 54652803944986921301
“ она была безупречной ..! “ теперь уже двадцати однолетняя , я продолжаю радовать вас своей красотой
custom 54652803944986921307custom 53122984182389302715❤3❤🔥2💋1custom 52738869065081338891custom 53439199045023283151custom 54630468740658132911
Showing the 4 most recent of 4 posts we hold for @riri_yuji. 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 — 509,977 of 1,548,671entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“By_Annora” (@riri_yuji), 177 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/riri_yuji.
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.