Channel
@KazanovaTalks
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
289subscribers
-13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002691503942 |
|---|---|
| Type | Channel |
| Username | @KazanovaTalks |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/KazanovaTalks |
Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 15:38 | 289 | -3 |
| 13 Sept 2026, 06:58 | 292 | -3 |
| 5 Sept 2026, 00:38 | 295 | -3 |
| 27 Aug 2026, 12:25 | 298 | +1 |
| 21 Aug 2026, 01:05 | 297 | -3 |
| 13 Aug 2026, 13:35 | 300 | -2 |
| 6 Aug 2026, 22:32 | 302 | no change |
| 6 Aug 2026, 18:49 | 302 | first reading |
6 posts held, back to 25 July 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 6 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
117 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 39.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 46 | 39.3% | |
| ❤ | 37 | 31.6% | |
| ❤🔥 | 18 | 15.4% | |
| 👏 | 8 | 6.84% | |
| custom 5303310030940952439 | 3 | 2.56% | |
| 🤩 | 3 | 2.56% | |
| 👍 | 2 | 1.71% |
Custom emoji. One 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 count beside it is 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 5 of the 6 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 117 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 25 July 2026 to 3 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.
Наша группа поддержки самая крутая была. Спасибо огромное. В такие моменты, видно большую сильную общую компанию. Казанова 69 - одна большая команда ради успеха.
🔥13❤2
Signed Aleksey Chernykh
Уральский Кофейный Фестиваль 2026 прошел, а эмоции все не утихают! В этом году все было изумительно ярко, вкусно, с пикантной добавкой афродизиаков от КОФЕ 18+ Практически 10 000 гостей посетивших мероприятие - познакомились с нашими кофейнями! И нам очень радостно, что все наши бариста достойно выступили в заявленных конкурсных дисциплинах - показав свое мастерство и фантазию (горячие фантазии🔥)! Отдельное спасибо…
🔥14❤1
Signed Aleksey Chernykh
Ребят, тут такое было! Хотим рассказать ещё раз)))
Signed Aleksey Chernykh
⚡️ Мы это сделали! Первая в России страница-гид по секс-девайсам для спинальных пациентов официально запущена: https://kazanova.su/medical/ Друзья, отличные новости. Мы финализировали работу, и страница-гид уже доступна для вас! Команда нейроурологов во главе с Артемом Бершадским лично проверили каждый раздел. Все тексты вычитаны, девайсы одобрены, а инструкции по безопасности актуализированы специалистами. Никаких…
❤🔥18👏8❤5🔥3custom 53033100309409524392
Signed Dmitrii
И снова мы здесь! ☕️ Собрались поддержать нашу команду бариста КОФЕ 18+ на Уральском кофейном фестивале! Гордимся, болеем всей командой и желаем удачи! Знаем, что всё получится 🥰❤️ // На фотографиях выступление Марины Гавриловой
❤13🔥8🤩3👍1custom 53033100309409524391
Signed Dmitrii
КОФЕ 18+ в деле! 🤭🔥 Мы участвуем в Уральском фестивале кофе! Подготовили для судей наши лучшие напитки, продумали каждую деталь подачи и, конечно, добавили немного вау-эффекта! Кажется, нам удалось удивить не только вкусом, но и интересными сюрпризами из Казанова 69 😏 Спасибо каждому, кто поддерживает нас. Для нас это очень ценно и мотивирует двигаться дальше! Завтра продолжаем фестиваль — обязательно заходите …
❤16🔥8👍1
Signed Dmitrii
Showing the 6 most recent of 6 posts we hold for @KazanovaTalks. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Kaza ⚡️Nova | live🎙️” (@KazanovaTalks), 289 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/KazanovaTalks.
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.