Music — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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
31 measurements spanning 49 days, net +237. 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 21,863–22,172 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)
Subscribers
Change
24 Sept 2026, 22:39
22,136
+26
18 Sept 2026, 19:02
22,110
+18
16 Sept 2026, 09:02
22,092
+14
14 Sept 2026, 17:20
22,078
+8
13 Sept 2026, 00:56
22,070
+19
11 Sept 2026, 03:16
22,051
-8
8 Sept 2026, 05:56
22,059
+3
5 Sept 2026, 00:18
22,056
+9
3 Sept 2026, 08:37
22,047
+11
1 Sept 2026, 23:07
22,036
+5
1 Sept 2026, 02:27
22,031
+10
31 Aug 2026, 01:04
22,021
+2
30 Aug 2026, 03:05
22,019
-2
29 Aug 2026, 04:43
22,021
+2
28 Aug 2026, 02:44
22,019
-1
27 Aug 2026, 01:32
22,020
-2
26 Aug 2026, 04:56
22,022
-1
25 Aug 2026, 01:48
22,023
+17
23 Aug 2026, 15:47
22,006
+8
22 Aug 2026, 04:34
21,998
first reading
Engagement
140 posts held, back to 1 August 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 59 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.19%
avg views ÷ 22,136 subscribers
Avg views / post
1,150
35 posts measured
Reaction rate
3.95%
reactions ÷ views · ER floor
Posts in window
36
of 140 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. It is computed over the 34 of 35 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 September 2026
Posts held
140 (1 August 2026 – 3 September 2026)
Views total
40,177
Reactions total
1,539
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 12:51 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
35m 20s
Average length
1m 13s
Measured directly from 29 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
7,487 reactions across 134 posts, in 10 distinct kinds. The most used accounts for 57.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
4,296
57.4%
🔥
1,242
16.6%
👍
829
11.1%
👏
466
6.22%
🎉
390
5.21%
😁
96
1.28%
🥰
93
1.24%
🤩
37
0.494%
🤔
21
0.28%
😢
17
0.227%
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 134 of the 140 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 7,487 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 140 most recent posts we hold, published 1 August 2026 to 3 September 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.
Считаете Ивана Грозного исключительно суровым и жестоким царём? А что, если я скажу, что он… писал музыку? И мы даже можем её послушать!
Да, первый русский правитель, оставивший после себя музыкальные сочинения, — именно он. Пока в Европе бушевало Возрождение, в России царь лично сочинял стихиры.
Это суровые, глубокие и завораживающие распевы, которые совершенно меняют наше представление о музыкальной культуре XVI …
18 лет Бородин писал «Князя Игоря». Но всё равно не успел закончить🫣
В 53 года Александр Бородин, полный сил и планов, внезапно ушёл из жизни — у него случился сердечный приступ прямо во время праздника.
И «Князь Игорь» остался незаконченным. Тогда за дело взялись друзья Бородина — Николай Римский-Корсаков и Александр Глазунов. Они разобрали рукописи и черновики, дописали недостающее и оркестровали значительную час…
Кто в Москве?
Традиционная рубрика
Папа приглашает на концерты-лекции в библиотеке искусств им. Боголюбова
🎻 2 сентября, среда, 17:00
🎟 По билетам
«Пленительные звуки виолончели»
Концерт-беседа
Музыка И. С. Баха, Ф. Мендельсона, С. Рахманинова.
Исполняют лауреаты международных конкурсов:
Михаил Калиничев — виолончель
Полина Генералова — фортепиано
Рассказывает Михаил Калиничев.
📚 3 сентября, четверг, 15:00
✨ …
У Мишки хорошо получается взгляд вселенской печали по утрам👌
Картина называется «Шел второй день школы …»
(На самом деле, все нравится и все хорошо, это Мишун в образе)
Ромео и Джульетта поженились и жили долго и счастливо? 😁
Именно так первоначально должен был закончиться знаменитый балет Сергея Прокофьева!
В первой версии 1935 года Джульетта просыпалась вовремя — и трагедия Шекспира превращалась в историю со счастливым финалом.
Но удивительным был не только финал.
Когда музыку впервые показали в театре, её не приняли: слишком непривычной она казалась для балета.
🎵 Прокофьев н…
Всех причастных - с праздником!
А праздник, я считаю, у всех: не важно, идет кто-то в семье в школу или нет. 📚
Когда еще не родился Мишка, а консерватория уже закончилась, я помню, как радовалась 1го сентября - что никуда идти не надо🔥
Так что празднуем, друзья мои, в любом случае!!! Надо идти или не надо идти!
P.S. Мишка пошел в 5 класс. Новая школа (в смысле новое здание), новые порядки, новые учителя. Так что …
Сентябрь предлагаю начать с праздничной встречи!
Приглашаю вас на новый бесплатный вебинар🥰👇
🎼 «История русской классической музыки за 1,5 часа»
Можно ли понять 300 лет русской музыки за полтора часа?
С чего начинается русская классика?
Кто написал первую русскую симфонию?
А кто создал первую русскую оперу? Подсказка: это не Глинка😉
И кто совершил главные музыкальные революции ХХ века?
📍9 сентября в 19:00 по Мск…
Showing the 12 most recent of 140 posts we hold for @Yuliakazantsevamusic. 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.
Posts edited after publishing
@Yuliakazantsevamusic edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
24 August 2026
Most recent edit
24 August 2026
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.
Mentions
Named by 4 registered channels — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 24 September 2026 — this
entry's latest reading, not the date you are reading this.
“Музыка для всех | Юлия Казанцева” (@Yuliakazantsevamusic), 22,136 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/Yuliakazantsevamusic.
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.