Channel
@SHOU_TAO_Yumi
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
394subscribers
-11 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002147770464 |
|---|---|
| Type | Channel |
| Username | @SHOU_TAO_Yumi |
| Created | Between 1 April 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/SHOU_TAO_Yumi |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 42% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 23:41 | 394 | -1 |
| 9 Sept 2026, 13:56 | 395 | -3 |
| 31 Aug 2026, 21:48 | 398 | -8 |
| 17 Aug 2026, 18:14 | 406 | +1 |
| 11 Aug 2026, 14:16 | 405 | no change |
| 10 Aug 2026, 20:17 | 405 | first reading |
9 posts held, back to 16 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
233 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 42.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 98 | 42.1% | |
| 💘 | 54 | 23.2% | |
| ❤🔥 | 44 | 18.9% | |
| 🍓 | 21 | 9.01% | |
| 🔥 | 4 | 1.72% | |
| 💋 | 3 | 1.29% | |
| 🤩 | 3 | 1.29% | |
| 🥰 | 3 | 1.29% | |
| 🍌 | 1 | 0.429% | |
| 😇 | 1 | 0.429% | |
| 😍 | 1 | 0.429% |
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 233 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 16 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.
Я только с концерта группы КняZz! (☆▽☆) Это было таааак круто! ✨ Я услышала свои любимые песни!٩(♡ε♡)۶ А ещё я сегодня первый раз слэмилась, давно мечтала об этом, мне так понравилось!( ◕▿◕ ) Это офигенно! ヽ(>∀<☆)ノ Правда мне порвали платье, я в чужом поту и потом мне стало плохо, но это того стоило! (๑>◡<๑) Панки хой 🤘 А ещё у меня теперь есть Совунья 🦉💜 σ(≧ε≦σ) ♡
❤12🤩3🍓2🔥2
Signed Юми
1 старый дизайн - 2 новый дизайн ▼•ᴥ•▼🐾 Я буду менять Юми волосы и юбку, а также добавлю пару эмоций! ヽ(>∀<☆)ノ Если честно мне никогда не нравились её волосы и юбка, но я не могла понять, что не так и как сделать их лучше ｡ﾟ( ﾟ^∀^ﾟ)ﾟ｡ Сейчас я просто их упростила и дизайн как по мне стал выглядеть лучше ( ◕▿◕ ) Мне придётся возвращаться в риг,а я уже надеялась, что открестилась от него раз и навсегда, я забыл как та…
❤🔥13❤7🥰3🍓1💘1
Signed Юми
Гифочка (≧◡≦) Будет каланиться во время стримов каждому новому подписчику на твич! (//▽//) А сейчас кланяется вам!^^ Спасибо, что остаётесь со мной, вы самые лучшие ⸜(*ˊᗜˋ*)⸝ 💕
❤11💘5❤🔥4🍓2💋1😍1
Signed Юми
Последние две плашечки для твича (≧▽≦) 🐾
💘11❤🔥9❤5💋2🍓1
Signed Юми
Сейчас делаю вот такие вот плашечки для твича (o^▽^o) 🎀 Осталось ещё две ^^ Параллельно создаю брелочки в зин, но пока не знаю разрешено их спойлерить или нет ¯\_(ツ)_/¯
❤17💘8🍓4
Signed Юми
Начальная заставка для стримов (*´▽*) 🐾 Захотелось чего то такого доброго, милого, наивного, простого , как рисунок из детской книжки (ﾉ´ヮ)ﾉ*: ･ﾟ В будущем сделаю тут ещё небольшую анимацию ∪ÒᗜÓ∪
❤11💘6🍓3😇1
Signed Юми
Вот такой вот баннер в итоге получился (≧▽≦) 🩷 А теперь я продолжу рисовать другие штучки ^^ А ещё у меня офигенная новость! Меня приняли в зин по Мильграм !!!! ヽ(>∀<☆)ノ Это первый раз когда я буду участвовать в чем то подобном, немного волнуюсь но постараюсь выложиться на полную (๑˃ᴗ˂)ﻭ
💘15❤8❤🔥6🍌1🍓1
Signed Юми
Баннер для ютуба, вк и твич ∪≧ᗜ≦∪ 🌸 Чтобы все элементы читались в маленьком формате, мне пришлось немножко упростить стиль ( ◕▿◕ ) Это ещё не конечный результат, в ближайшие дни я его доработаю (>ᴗ•)
❤🔥12❤8💘3🍓2🔥2
Signed Юми
Сейчас делаю активный ребрендинг соцсетей! U^ｪ^U Вот такой теперь логотип (>ᴗ•) Слева финал, а справа первоначальный набросок самой идеи (≧▽≦)
❤19🍓5💘5
Signed Юми
Showing the 9 most recent of 9 posts we hold for @SHOU_TAO_Yumi. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“БУДКА SHOU TAO18+ 🍑” (@SHOU_TAO_Yumi), 394 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/SHOU_TAO_Yumi.
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.