в сочи летим !!!
custom 52264507966100793825

Channel
@yohjisuwant
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
991subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001653308211 |
|---|---|
| Type | Channel |
| Username | @yohjisuwant |
| Created | 27 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/yohjisuwant |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 04:18 | 991 | -8 |
| 30 Aug 2026, 00:27 | 999 | +4 |
| 22 Aug 2026, 23:18 | 995 | -1 |
| 15 Aug 2026, 17:35 | 996 | +11 |
| 8 Aug 2026, 00:35 | 985 | no change |
| 7 Aug 2026, 20:03 | 985 | first reading |
10 posts held, back to 24 June 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 10 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
138 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 29.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226507069271593332 | 40 | 29.0% | |
| custom 5226626770010132648 | 19 | 13.8% | |
| custom 5332721026386117717 | 17 | 12.3% | |
| custom 5400098050964211841 | 16 | 11.6% | |
| custom 5226450796610079382 | 13 | 9.42% | |
| custom 5226596726713896821 | 10 | 7.25% | |
| custom 5188647563917543487 | 9 | 6.52% | |
| custom 5274149595297889863 | 6 | 4.35% | |
| custom 5400199553926318856 | 4 | 2.90% | |
| custom 5404388676048273675 | 4 | 2.90% |
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 10 of the 10 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 138 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 24 June 2026 to 5 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 52264507966100793825
Video message, posted without a caption
custom 540009805096421184116custom 52741495952978898635custom 54001995539263188564
2202208311839998 - карта сбер принимаю донаты на новое белье ! 🤍 🌟🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟
custom 52264507966100793827
Posted without readable text
custom 52265967267138968215
щечки мои милые
custom 522650706927159333224custom 522662677001013264811custom 52265967267138968215custom 54043886760482736754custom 53327210263861177172custom 52264507966100793821custom 52741495952978898631
Photo, posted without a caption
custom 533272102638611771715
Photo, posted without a caption
custom 52266267700101326488
Photo, posted without a caption
custom 51886475639175434879
Photo, posted without a caption
custom 52265070692715933328
Video message, posted without a caption
custom 52265070692715933328
Showing the 10 most recent of 10 posts we hold for @yohjisuwant. 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“be my sugar mommy when u are ill get u all the yohjis u want” (@yohjisuwant), 991 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/yohjisuwant.
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.