❌ 🤩 ❌🔠𝙚𝙨𝙪𝙡𝙩𝙨 𝙛𝙤𝙧... 🗯 ❌ @yuhichann 🤩

Channel
ПЕРЕЕЗД || юх𝓾 - 𝓜яу
@yuhichann
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
27subscribers
-28 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003845021322 |
|---|---|
| Type | Channel |
| Username | @yuhichann |
| Created | Between 1 February 2026 and 30 July 2026 — 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 | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/yuhichann |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 20:40 | 27 | -1 |
| 10 Sept 2026, 00:40 | 28 | -5 |
| 25 Aug 2026, 04:25 | 33 | -8 |
| 17 Aug 2026, 16:48 | 41 | -15 |
| 10 Aug 2026, 07:46 | 56 | no change |
| 10 Aug 2026, 05:31 | 56 | +1 |
| 9 Aug 2026, 10:30 | 55 | first reading |
Engagement
14 posts held, back to 30 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 14 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 7s
- Average length
- 7s
Measured directly from 1 video 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
173 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 23.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5309875567057728490 | 40 | 23.1% | |
| custom 5309928781702528075 | 31 | 17.9% | |
| custom 5429451167430123002 | 25 | 14.5% | |
| custom 5190540978775157455 | 24 | 13.9% | |
| custom 5307707974372847209 | 20 | 11.6% | |
| custom 5309835280264491140 | 19 | 11.0% | |
| custom 5309983220413001854 | 9 | 5.20% | |
| custom 5307536149911204740 | 5 | 2.89% |
Custom emoji. Every 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 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 6 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 173 reactions 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 30 July 2026 to 9 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.
Recent posts
Sticker, posted without a caption
☁🤩🤩🤩 N🤩W🤩o🤩t ͡ 🤩 ☁🗒🎀 #Gregor🗒 #Radion 🗒🎀 ☁☁☁🤩рк / рт / мнение🎀.
custom 53077079743728472099custom 51905409787751574557custom 53098352802644911407custom 54294511674301230023custom 53098755670577284902custom 53099287817025280752custom 53099832204130018542
Sticker, posted without a caption
☁𖹭͟𝐫𝐞𝐬𝐮𝐥𝐭𝐬 :3
custom 53098755670577284908custom 54294511674301230025custom 51905409787751574554custom 53077079743728472093
Sticker, posted without a caption
𝟏 - б𝐮н𝐨ш𝐤а 𝟐 - м𝐚ф𝐤р𝐮 𝟑 - м𝐞о 𝟒 - 𝐚р𝐤аш𝐚 𝟓 - л𝐨ття 𝟔 - д𝐚н𝐜с𝐲 𝟕 - в𝐚н𝐨р𝐚 𝟖 - м𝐚р𝐮я 𝟗 - к𝐨з𝐮н𝐚к з𝐚к𝐩ыт𝐨
custom 54294511674301230028custom 51905409787751574555custom 53099287817025280754
Sticker, posted without a caption
☁ 𐔌 𓏵 ׄ 𝐦𝐞 𝐚𝐧𝐝 ? ? ೀ 🤩 ࣪для 𝐲ч𝐚ст𝐮я н𝐮жн𝐨 : п𝐨ст𝐚в𝐮ть 𝐩к , 𝐮 н𝐚п𝐮с𝐚ть в𝐚ш п𝐨в𝐜𝐞дн𝐮м н𝐚 𝐩у𝐜𝐜к𝐨м , 𝐲ч𝐚ств𝐨в𝐚ть 𝐦ог𝐲т в𝐜𝐞 ! ☁︶ ͝ ⏝ ִ 🤩 𐄬 🤩 ׄ ⏝ ͝ ︶
custom 53099287817025280759custom 53098755670577284908custom 51905409787751574556custom 54294511674301230024
Sticker, posted without a caption
Sticker, posted without a caption
☁🤩🤩🤩 N🤩W🤩o🤩t ͡ 🤩 ☁🗒🎀 #saparata 🗒 #fluixon 🗒🎀 ☁☁☁🤩рк / рт / мнение🎀
custom 530987556705772849013custom 530992878170252807510custom 53098352802644911409custom 54294511674301230025custom 53075361499112047403custom 51905409787751574552custom 53099832204130018542custom 53077079743728472091
Showing the 12 most recent of 14 posts we hold for @yuhichann. 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.
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 3 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ПЕРЕЕЗД || юх𝓾 - 𝓜яу” (@yuhichann), 27 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yuhichann.
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.