Channel
@yaaaaazdesrisuyukruto
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
139subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002050752920 |
|---|---|
| Type | Channel |
| Username | @yaaaaazdesrisuyukruto |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/yaaaaazdesrisuyukruto |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 20:02 | 139 | +1 |
| 4 Sept 2026, 03:59 | 138 | -1 |
| 20 Aug 2026, 00:22 | 139 | +2 |
| 8 Aug 2026, 23:17 | 137 | no change |
| 6 Aug 2026, 17:49 | 137 | first reading |
9 posts held, back to 14 July 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 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 9 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
209 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 32.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5292114593093547956 | 68 | 32.5% | |
| custom 5368735847581508565 | 31 | 14.8% | |
| ❤ | 31 | 14.8% | |
| custom 5316703525676278822 | 24 | 11.5% | |
| 🔥 | 19 | 9.09% | |
| custom 5472362245813992916 | 16 | 7.66% | |
| custom 5348353977199128962 | 9 | 4.31% | |
| custom 5370751338294567994 | 6 | 2.87% | |
| ⚡ | 5 | 2.39% |
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 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 9 of the 9 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 209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 14 July 2026 to 4 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.
кину спойлер в аск и редрав древней картинки с шу капец, я наныла, что давно не ела бургэров, а теперь последние три дня ток ими и питаюсь 🥹🥹🥹
custom 529211459309354795612custom 53483539771991289627custom 53167035256762788223custom 53687358475815085651custom 54723622458139929161
хочу биг спэшл бургэр просто капец как небольшие асковые почеркушки, в основном пока туда рисую (помогите, я в рабстве) всем новеньким хааай ❤️❤️❤️
custom 529211459309354795614custom 53167035256762788227custom 54723622458139929163
легендарный трейд, все кто ждали Юю в этом канале, возрадуйтесь ❤️❤️ пасиба за такую возможность оч крутой художнице🌟
custom 529211459309354795614custom 54723622458139929167custom 53687358475815085655custom 53483539771991289621
трейдец с очень крутым бро 🥺🥺🥺🥺🥺 я кайфанула, спасибо большое 😊
custom 536873584758150856517custom 53167035256762788229custom 52921145930935479565custom 54723622458139929162custom 53483539771991289621
рисую с больной рукой, совсем дура я крч персы по гачиакуте💕💕
custom 529211459309354795618custom 53687358475815085654custom 53707513382945679944custom 54723622458139929161
https://t.me/boost/yaaaaazdesrisuyukruto блин, ребят, я оч хочу милые реакции, проголосуйте, кто может 🫠🫠🫠
❤9custom 52921145930935479561custom 53167035256762788221custom 53707513382945679941
ваще я так горда собой кирами еще нигде не получался так хорошо 🤩
❤10🔥3⚡2custom 52921145930935479561custom 53687358475815085651custom 53707513382945679941
некие спойлеры моей дивы в аск извините, что пропала, я жестко делала ивент ☝️☝️☝️
❤12🔥5⚡3custom 52921145930935479562custom 53167035256762788222custom 53687358475815085652custom 54723622458139929162
🥰 Влетаю в день репостов #PortfolioDay
🔥11custom 53167035256762788222custom 52921145930935479561custom 53687358475815085651
Showing the 9 most recent of 9 posts we hold for @yaaaaazdesrisuyukruto. 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.
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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“♡𝓈𝒶𝓋𝒶𝓋𝑒𝓎𝒶♡ рест” (@yaaaaazdesrisuyukruto), 139 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/yaaaaazdesrisuyukruto.
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.