Channel
@yushkoch_v_kleyu
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
57subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002553692220 |
|---|---|
| Type | Channel |
| Username | @yushkoch_v_kleyu |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 18 September 2026 |
| On Telegram | t.me/yushkoch_v_kleyu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 22:57 | 57 | -1 |
| 19 Aug 2026, 06:54 | 58 | +1 |
| 11 Aug 2026, 19:01 | 57 | no change |
| 11 Aug 2026, 18:46 | 57 | first reading |
17 posts held, back to 8 May 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 17 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 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.
254 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5285114685459302792 | 79 | 31.1% | |
| custom 5253985453987634841 | 42 | 16.5% | |
| custom 5352751766012193062 | 36 | 14.2% | |
| ❤ | 17 | 6.69% | |
| custom 5381854954036156218 | 16 | 6.30% | |
| custom 5382332833572344632 | 15 | 5.91% | |
| custom 5456530584044059790 | 15 | 5.91% | |
| custom 5199897981641310670 | 9 | 3.54% | |
| custom 5233315859451115604 | 7 | 2.76% | |
| custom 5208650880177424366 | 4 | 1.57% | |
| custom 5222450279386991813 | 3 | 1.18% | |
| custom 5271546531583902428 | 3 | 1.18% | |
| 🐳 | 3 | 1.18% | |
| 💊 | 3 | 1.18% | |
| 🍌 | 1 | 0.394% | |
| 💘 | 1 | 0.394% |
Custom emoji. 11 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 17 of the 17 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 254 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 8 May 2026 to 19 July 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.
▫️✨▫️ 🥹「art cr」: htshanquan7; Subisabin_; 02_neta_; Qj4Kn37 (x) 🥹「song」: buck-tick - my funny valentine #edit #ooe #大穢 #shizuma #oosaki
custom 52539854539876348415custom 52851146854593027923custom 53527517660121930623
Signed ёша ⊹₊☾⋆˚𖦹
▫️✨ещё шзм #art #ooe #大穢 #daibashizuma
custom 52539854539876348416custom 52851146854593027922custom 53527517660121930622custom 52086508801774243661custom 52333158594511156041custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
▫️🎀64bitの分解 🥹「art cr」: k1sh3e #edit #shimbashi #ooe #大穢 #adelta
custom 53527517660121930627custom 52851146854593027923custom 52539854539876348412custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
🤩✨шзм #art #ooe #大穢 #daibashizuma
custom 52539854539876348417custom 52851146854593027923custom 53823328335723446322custom 52086508801774243661custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
🤩✨с д/р шиона ураа #art #shiontatsunami #saihatestation
custom 528511468545930279212custom 52539854539876348413custom 53527517660121930623❤2custom 53823328335723446321custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
больше оошз под пластик три 🥹「art cr」: reyjALBCG229144 (x); 142389666; 134092288 (pixiv); htshanquan7 (x); p7fp7; ?? 🥹「song」: plastic tree - 13th,Friday #edit #ooe #大穢 #shizuma #oosaki
custom 52851146854593027925custom 52539854539876348413custom 52086508801774243662custom 53823328335723446322❤1custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
🫐✨с д/р кокичее 🥹「art cr」: kuzirapyonka 🥹「song」: 鮮血A子ち ゃん 3年5組の特異点 #edit #kokichiouma #danganronpa
custom 52851146854593027928custom 53527517660121930625custom 54565305840440597905❤3custom 53823328335723446321
Signed ёша ⊹₊☾⋆˚𖦹
🤩✨скрап 🥹「art cr」: yokujitudesu; shiki_fanart; zp_f1k; gochugae📱 🥹「song」: ?? #edit #ooe #大穢 #shizuma #daibashizuma
custom 52851146854593027926custom 52333158594511156043custom 52539854539876348413custom 53527517660121930622❤1custom 52224502793869918131custom 53823328335723446321custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
🕸️✨🕸️ 🥹「art cr」: kjou_000, 21g_yaseru, mayonakahino, Rrrrrrice0303, angandago📱 🥹ib: kc270947📱 🥹♫ : crxw - unpledged alliance #edit #tatsumikazehaya #himeru #ensemblestars #enstars
custom 52851146854593027924💊3custom 53527517660121930623custom 52539854539876348412❤1custom 54565305840440597901
Signed ёша ⊹₊☾⋆˚𖦹
🙂✨мне кста это приснилось 🎵?? :( #edit #minakami #tamamori #hashihimeoftheoldbooktown
custom 52539854539876348416custom 52851146854593027923custom 53823328335723446323custom 52333158594511156042❤1
Signed ёша ⊹₊☾⋆˚𖦹
похвастуюсь😜
custom 53818549540361562188custom 52851146854593027923❤2custom 53823328335723446322custom 52224502793869918131custom 52333158594511156041custom 52539854539876348411custom 53527517660121930621
Signed ёша ⊹₊☾⋆˚𖦹
👾💜
custom 52539854539876348412custom 52851146854593027922custom 53527517660121930622❤1
Signed ёша ⊹₊☾⋆˚𖦹
Showing the 12 most recent of 17 posts we hold for @yushkoch_v_kleyu. 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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“юшкоч в клею” (@yushkoch_v_kleyu), 57 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/yushkoch_v_kleyu.
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.