Telegram RegisterThe public register of Telegram
Telegram profile photo for Ural Dance Camp & Champ

Channel

Ural Dance Camp & Champ

@ural_dance_camp

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,102subscribers

-6 since we began measuring on 31 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001503679801
TypeChannel
Username@ural_dance_camp
CreatedBetween 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/ural_dance_camp

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 55% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2,1022,1082,10531 August 2026 — 2,108 subscribers31 August 2026 — 2,108 subscribers3 September 2026 — 2,104 subscribers9 September 2026 — 2,107 subscribers13 September 2026 — 2,105 subscribers17 September 2026 — 2,102 subscribers31 August 202617 September 2026
6 measurements spanning 17 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,101–2,109 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 10:222,102-3
13 Sept 2026, 05:582,105-2
9 Sept 2026, 00:192,107+3
3 Sept 2026, 08:482,104-4
31 Aug 2026, 05:152,108no change
31 Aug 2026, 05:002,108first reading

Engagement

11 posts held, back to 23 August 2026the 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.

ERR · 30 days
33.0%
avg views ÷ 2,102 subscribers
Avg views / post
693
11 posts measured
Reaction rate
4.41%
reactions ÷ views · ER floor
Posts in window
11
of 11 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 August 2026
Posts held11 (23 August 202630 August 2026)
Views total7,619
Reactions total336
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 05:15 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.

What this channel posts

Video runtime
1m 11s
Average length
24s

Measured directly from 3 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.

Reaction mix

336 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14743.8%
💘9428.0%
❤‍🔥5516.4%
🙏236.85%
🍓82.38%
🔥82.38%
😁10.298%

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 11 of the 11 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 336 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 23 August 2026 to 30 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

30 Aug 2026, 14:10 UTC348 views19 reactionsread 31 August 2026
Video

Судейский выход от Gleb SteelSteez Полное видео смотрите в нашем инстаграмме 🙏🏻

💘106🔥3

29 Aug 2026, 15:38 UTC581 views38 reactionsread 31 August 2026
Photo

Результаты UDC BATTLE vol.5 Hip-Hop Beginners ЭМВИ - Winner 🏆 Миша Малыша - Finalist Hip-Hop Pro Тот Самый Саня - Winner 🏆 Лиза Броневицкая - Finalist All Styles Kids Лиза Броневицкая - Winner 🏆 Санёк - Finalist All Styles 16+ Dark Whiphead - Winner 🏆 Sonic - Finalist Всем участникам спасибо большое. Все видео скоро можно будет забрать по ссылке 🙏🏻

22💘10🙏6

28 Aug 2026, 13:43 UTC563 views23 reactionsread 31 August 2026
Photo

——||—— ССЫЛКИ ——||—— КЭМП: - Селекты: ССЫЛКА - Фото: —//— - Треки: 1-3 дня и 4-5 дни UDC BATTLE vol.5: - Preselections: ССЫЛКА - Результаты: ССЫЛКА - Видео: —//— - Фото: —//— UDC CONTEST vol.3: - Судейские листы: ССЫЛКА - Видео: —//— - Фото: —//— Отдел Заботы: @anchous_forsage Наши соц.сети: 💙 Группа в VK 👈 💬 Телеграмм канал 👈 📷 Наша инста 👈 🎥 Наш аккаунт 👈 📺 Наш YouTube канал 👈

❤‍🔥118🔥4

28 Aug 2026, 09:39 UTC569 views15 reactionsread 31 August 2026
File

File, posted without a caption

💘8❤‍🔥7

28 Aug 2026, 09:39 UTC558 views12 reactionsread 31 August 2026

Треки 4-го и 5-го дня кэмпа👇

❤‍🔥12

27 Aug 2026, 06:10 UTC672 views34 reactionsread 31 August 2026
Video message

Video message, posted without a caption

💘2311

25 Aug 2026, 05:17 UTC866 views65 reactionsread 31 August 2026
Video

Класс Кирилла Зуба ❤️

25💘22❤‍🔥16🔥1😁1

23 Aug 2026, 13:48 UTC964 views64 reactionsread 31 August 2026

Спасибо всем за эти дни!🫶🏼❤️‍🔥

36🙏17💘11

23 Aug 2026, 13:48 UTC912 views23 reactionsread 31 August 2026
Video message

Video message, posted without a caption

16💘7

Showing the 11 most recent of 11 posts we hold for @ural_dance_camp. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Ural Dance Camp & Champ” (@ural_dance_camp), 2,102 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ural_dance_camp.

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.