Channel
@iyoose
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
183subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001788392887 |
|---|---|
| Type | Channel |
| Username | @iyoose |
| Created | 13 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/iyoose |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 14:08 | 183 | +1 |
| 8 Aug 2026, 12:46 | 182 | no change |
| 7 Aug 2026, 14:22 | 182 | first reading |
9 posts held, back to 7 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 August 2026 |
|---|---|
| Posts held | 9 (7 June 2026 – 2 August 2026) |
| Views total | 184 |
| Reactions total | 26 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:46 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 2 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.
167 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 35.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5395321712323610401 | 60 | 35.9% | |
| custom 4924829008782164656 | 42 | 25.1% | |
| custom 5213416051903051726 | 32 | 19.2% | |
| custom 5318967291268833477 | 25 | 15.0% | |
| custom 5395490633387359457 | 6 | 3.59% | |
| custom 5471962813855444397 | 2 | 1.20% |
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 areTelegram’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 8 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 167reactions 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 7 June 2026 to 2 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.
возвращаюсь в нормал лайф после отпуска и собираю людей для проекта &TEAM - MISMATCH 🖤 свободная партия: фума тренировки будут по выходным и в будние дни вечером 🐶 от вас требуется: танцевальный опыт, оплачивать тренировки и не пропускать их, также покупка/кастом костюма пишите в лс @jjunshn 🥵
Video message, posted without a caption
custom 521341605190305172613custom 53953217123236104016custom 49248290087821646565custom 53189672912688334771custom 53954906333873594571
😕😕😕😕😕😕😕 💃💞💗🤕DANCE IN PUBLIC 😟🙆♂️🫥😕😕😕 👉👨🦱🤷🤕30.06 / 20:00 / арбат 👳♀️ 😕😕😕 p.s. i'm about to TNT 😎
custom 49248290087821646567custom 53953217123236104017custom 53954906333873594575custom 54719628138554443972
сегодня день рождения у нашей супер крейзи Лазизы 💌 поздравляем тебя с красивым юбилеем — 20 лет 😎 пусть жизнь радует приятными событиями, мечты становятся целями, а цели — достижениями счастья, а еще любви, удачи и ярких моментов каждый день 🥹 мы тебя любим и очень очень скучаем 😭 можете поздравить лазизу в комментариях 💐
custom 521341605190305172615custom 49248290087821646567custom 53953217123236104017custom 53189672912688334772
🤩🤩🌟 СРОЧНО В ПРОЕКТ 🌟 ищем человека на партию в cortis - tnt ( мартин ) 🌟тренировки будут по выходным и в будние дни вечером 🌟 от вас требуется: танцевальный опыт, оплачивать тренировки и не пропускать их, также покупка/кастом костюма если вы хотите потанцевать с нами, то пишите в лс @jjunshn 💌
custom 53189672912688334775
сегодня празднует свой день рождения наш министр нишевых дел или просто Ксюша 🌿 мы очень рады твоему появлению в нашей команде ! желаем исполнения всех твоих желаний (особенно хотелок из вишлиста!) и больше денег в праймовом портмоне 😝 оставайся такой же вайбовой, веселой и, конечно же, нишшшшшшевой ❤️ we love uuuuuu 🎂 пс… можете поздравить ксюшу в комментариях🙂
custom 492482900878216465615custom 53189672912688334776custom 53953217123236104016
🐾
custom 539532171232361040111custom 53189672912688334776custom 49248290087821646562
you could have anyone else you wanted to 🤍🤍
custom 539532171232361040112custom 52134160519030517264custom 53189672912688334773custom 49248290087821646562
Signed пальма
🌟
custom 539532171232361040111custom 49248290087821646564custom 53189672912688334772
Showing the 9 most recent of 9 posts we hold for @iyoose. 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.
Citation-graph rank — 974,103 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“IYOOSE COVER DANCE TEAM” (@iyoose), 183 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/iyoose.
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.