Channel
@yundsscdt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
80subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002774093738 |
|---|---|
| Type | Channel |
| Username | @yundsscdt |
| Description | Cover dance team from Russia/Yekaterinburg \\ b-day : 03.06.2025 members: 🐁 Rina - https://t.me/kivxuq167 🐿️ Bomii - https://t.me/bomiiy8 🐐 Rybi - https://t.me/r1ybi_nnn 🦛 Noa - https://t.me/noackk |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/yundsscdt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 15:00 | 80 | no change |
| 10 Aug 2026, 14:51 | 80 | first reading |
10 posts held, back to 16 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 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.
| Window | Rolling 30 days · latest post in window 15 July 2026 |
|---|---|
| Posts held | 10 (16 May 2026 – 15 July 2026) |
| Views total | 71 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 15:00 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.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
105 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 16.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249328880510055880 | 17 | 16.2% | |
| custom 5395833736849822967 | 16 | 15.2% | |
| custom 5251624974321463241 | 15 | 14.3% | |
| custom 5456547708078690113 | 13 | 12.4% | |
| custom 5251395326715111425 | 11 | 10.5% | |
| custom 5251505780389063067 | 11 | 10.5% | |
| custom 5415771975765228444 | 10 | 9.52% | |
| custom 5314609510076142889 | 7 | 6.67% | |
| custom 5249109996091751960 | 5 | 4.76% |
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 9 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 105reactions 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 16 May 2026 to 15 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.
Ждите aespa-Black Mamba на WHICH? PARTY ➫ 25.07.2026 📆 🥹второй блок и снова с Боми 😻 #EW #PERFORMANCE
custom 52493288805100558805custom 52491099960917519602custom 52513953267151114252custom 52516249743214632411
🤩 Уже завтра будем на random'NAER с номером aespa - Black Mamba совместно с Боми ! ❤️🩹 #EW #PERFORMANCE
custom 52515057803890630674
Будем на KPOP STAR WORLD с номером aespa-BLACK MAMBA ➫ 28.06.2026 📆 🥹второй командный блок совместно с Боми !! 😇 #EW #PERFORMANCE
custom 52516249743214632417custom 52513953267151114253custom 52515057803890630671
что же это ???
custom 52515057803890630675custom 52493288805100558804custom 52516249743214632414
поздравляем нашу прекрасную Рину!🪷 🥰 та самая мама нашей команды, без неё мы никуда. Рина, спасибо, что терпишь этих детей, и мы тебя любим!! #риналучшая #ринамама #ринарулит
custom 52493288805100558808custom 52513953267151114255custom 52491099960917519603custom 52516249743214632412
Channel photo updated
03.06.2025 одна из самых важных дат для нашей команды - день рождения yundss ! ! руби: за этот год мы стали маленькой семьёй, которая всегда готова поддержать и помочь в трудной ситуации или просто весело провести время вместе. давайте останемся такими же крутыми смешняфками и захватим кд ! люблю вас, мои ёнсики 🥹🥹 к сожалению с некоторыми девочками мы не нашли фото ((
custom 539583373684982296710custom 54565477080786901136custom 53146095100761428893custom 52513953267151114251custom 52515057803890630671custom 52516249743214632411
до конца подачи заявок осталась неделя ! 🏝 ⭐️ дедлайн заявок : 09.06.2026, до 23:59 по ЕКБ ⭐️ все заявки принимаются в наш бот @randss_bot
custom 54157719757652284442custom 54565477080786901132custom 53958337368498229671
help, pls мы в поиске казухи в boompala тренировки в ревде, по костюмам уже всё решено зал бесплатный, с вас только приехать 😭😭 @r1ybi_nn
custom 54157719757652284447custom 54565477080786901134custom 53958337368498229672custom 53146095100761428891
🅰🅰🅰🅰🅰❕🅰🅰🅰3⃣ ⭐️ дедлайн заявок : 09.06.2026, до 23:59 по ЕКБ ⭐️ все заявки принимаются в наш бот @randss_bot форма подачи заявок : 👋 1. название команды / дуэта / псевдоним 2. песня - исполнитель 3. сколько по времени идёт ваше выступление ( командное до 5 минут; дуэт до 4 минут; соло до 2 минут ) 4. видео заявка 🪷 ориентировочное кол-во призовых мест : соло - 3 места дуэт - 1 место командные - 1 ме
custom 53146095100761428893custom 53958337368498229673custom 54157719757652284441custom 54565477080786901131
Showing the 10 most recent of 10 posts we hold for @yundsscdt. 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 — 981,145 of 1,169,250entries 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.
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.
Named by 1 registered channel — 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“— 𝐲𝐮𝐧𝐝𝐬𝐬 𝐭𝐞𝐚𝐦” (@yundsscdt), 80 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/yundsscdt.
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.