Channel photo updated

Channel
YumiYuki Official
@YukiYumiOfficial
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
45subscribers
-1 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 | -1001769240934 |
|---|---|
| Type | Channel |
| Username | @YukiYumiOfficial |
| Created | Between 1 December 2021 and 20 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 19 September 2026 |
| On Telegram | t.me/YukiYumiOfficial |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 00:25 | 45 | -1 |
| 10 Aug 2026, 14:16 | 46 | no change |
| 7 Aug 2026, 08:56 | 46 | first reading |
Engagement
20 posts held, back to 20 March 2023 — 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 20 posts for this entry, the most recent from 11 January 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 08s
- Average length
- 8s
Measured directly from 16 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
34 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 73.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 25 | 73.5% | |
| ⚡ | 2 | 5.88% | |
| 💩 | 2 | 5.88% | |
| 😡 | 2 | 5.88% | |
| 🎄 | 1 | 2.94% | |
| 👍 | 1 | 2.94% | |
| 🤯 | 1 | 2.94% |
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 15 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 34 reactions 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 20 March 2023 to 11 January 2024, 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
YumiYuki Buy! 🟢🟢🟢 Spent: $20.66 (0.01 WETH) Got: 981,843,166 YIYI 0xD3A7..c5D7: ⬆️224.59%! Price: 0.00000002104 (0.000000000008148 WETH) MCap: $10,518 TX | Chart Sushiswap Ad: $DGNX/ETH LAUNCH 11th JAN
🔥2
YumiYuki Official pinned «🐉Website has been updated🐉 https://yumiyuki.xyz/»
YumiYuki Buy! 🟢 Spent: $5.55 (0.0 WETH) Got: 284,723,432 YIYI 0xC60d..ed1f: New! Price: 0.00000001951 (0.000000000008078 WETH) MCap: $9,754 TX | Chart Sushiswap Ad: $DGNX/ETH LAUNCH 11th JAN
YumiYuki Buy! 🟢🟢 Spent: $15.41 (0.01 WETH) Got: 810,594,687 YIYI 0xDFE6..Bf84: ⬆️13.69%! Price: 0.00000001901 (0.000000000008019 WETH) MCap: $9,507 TX | Chart Sushiswap Ad: $DGNX/ETH LAUNCH 11th JAN
🐉Website has been updated🐉 https://yumiyuki.xyz/
👍1
YumiYuki Buy! 🟢🟢🟢🟢🟢 Spent: $45.70 (0.02 WETH) Got: 2,615,570,125 YIYI 0xD3A7..c5D7: ⬆️544.41%! Price: 0.00000001747 (0.000000000007838 WETH) MCap: $8,736 TX | Chart Sushiswap Ad: SolPay Presale Upcoming
YumiYuki Buy! 🟢🟢🟢🟢🟢🟢 Spent: $50.03 (0.02 WETH) Got: 2,956,136,591 YIYI 0x1111..0582: New! Price: 0.00000001692 (0.000000000007554 WETH) MCap: $8,461 TX | Chart Sushiswap Ad: SolPay Presale Upcoming
🔥1
YumiYuki Buy! 🟢🟢 Spent: $11.19 (0.01 WETH) Got: 677,800,891 YIYI 0xD3A7..c5D7: New! Price: 0.00000001652 (0.000000000007377 WETH) MCap: $8,257 TX | Chart Sushiswap Ad: SolPay Presale Upcoming
🔥1
YumiYuki Buy! 🟢🟢🟢🟢🟢🟢 Spent: $57.01 (0.03 WETH) Got: 3,837,352,912 YIYI 0x8fE7..B0A3: ⬆️378.26%! Price: 0.00000001486 (0.000000000007818 WETH) MCap: $7,428 TX | Chart Sushiswap Ad: $BTCR Bitcoin Rewards
⚡1
YumiYuki Buy! 🟢🟢 Spent: $19.00 (0.01 WETH) Got: 1,323,744,375 YIYI 0x8fE7..B0A3: New! Price: 0.00000001436 (0.000000000007554 WETH) MCap: $7,177 TX | Chart Sushiswap Ad: $BTCR Bitcoin Rewards
⚡1
YumiYuki Buy! 🟢🟢 Spent: $18.13 (0.01 WETH) Got: 353,439,915 YIYI Buyer Position: New! Price: 0.00000005130 (0.00000000002829 WETH) MCap: $25,650 TX | Chart | Buyer | Sushiswap Ad: ZKP Proxy Swap LIVE
💩2🔥2
Showing the 12 most recent of 20 posts we hold for @YukiYumiOfficial. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@YukiYumiOfficial named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 11 August 2026 – 11 August 2026
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“YumiYuki Official” (@YukiYumiOfficial), 45 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/YukiYumiOfficial.
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.