Telegram RegisterThe public register of Telegram
Telegram profile photo for Король говорит…

Channel

Король говорит…

@Korol_Konstantinov

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

110subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002192914865
TypeChannel
Username@Korol_Konstantinov
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 October 2026
Measurements held6
Confirmed unchanged3 times, most recently 13 October 2026
On Telegramt.me/Korol_Konstantinov

Topic

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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

1081101097 August 2026 — 108 subscribers8 August 2026 — 109 subscribers9 August 2026 — 109 subscribers30 August 2026 — 110 subscribers8 September 2026 — 109 subscribers16 September 2026 — 110 subscribers7 August 202616 September 2026
6 measurements spanning 40 days, net +2. 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 108–110 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:59110+1
8 Sept 2026, 08:58109-1
30 Aug 2026, 06:46110+1
9 Aug 2026, 07:31109no change
8 Aug 2026, 01:54109+1
7 Aug 2026, 18:18108first reading

Engagement

8 posts held, back to 20 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 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 8 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 30s
Average length
23s

Measured directly from 4 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

33 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 45.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1545.5%
🔥1133.3%
🥰515.2%
👍13.03%
🤩13.03%

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

Measured over the 8 most recent posts we hold, published 20 June 2026 to 18 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.

Recent posts

18 Jul 2026, 16:26 UTC59 views3 reactionsread 9 August 2026

Вот о таком завтраке идет речь. Если кто не в курсе😁

❤2🥰1

18 Jul 2026, 12:31 UTC70 views7 reactionsread 9 August 2026
Video

Скоро понедельник!!! 20.07 Завтрак на Волге. В прошлый раз было мощно и вкусно. У многих раскрылось тело, начало дышать без блоков в груди, шее и плечах. Приходи, кайфуй в компании своих людей с практикой и вкусной едой. В этот раз у нас круассаны, с двумя видами начинок, сладкая и нет.

❤3🔥2🤩1🥰1

13 Jul 2026, 15:49 UTC79 views3 reactionsread 9 August 2026
Photo

Возымел желание поделиться одним из своих плейлистов. Для практик, тантры/секса, медитаций, наполнения. Меня эти треки трогают за душу, проникают прямо в нутро. Каждый по своему, они все великолепны. Заходите, слушайте, наслаждайтесь, исцеляйтесь. (Ссылка на плейлист☝️) И прикреплю три скриншота моих фаворитов, хотя… это все зависит от состояния.

🔥3

8 Jul 2026, 15:06 UTC84 views3 reactionsread 9 August 2026
Photo

Приглашаю на завтрак 13 июля. Собираемся в 10:00 на Волге Дикий пляж в черте города, сильное место, доехать легко. Энгельс, район старого моста (дикий, малоизвестный людям пляж, будем в тишине, одни) Завтрак, а перед ним — короткая практика, чтобы прийти к столу собранным: — встреча, знакомство — дыхание по методу Вима Хофа — заряд без кофеина, тишина в голове — шавасана — медитация - тело отпускает лишнее — с…

❤1👍1🥰1

28 Jun 2026, 08:48 UTC90 views2 reactionsread 9 August 2026
Video

Если готов принять быстрое спонтанное решение, то пиши в личку! Сегодня есть ветер и возможность пройтись на яхте под парусом. Есть 4 места По 2500 с человека Присоединяйся.

🔥2

22 Jun 2026, 13:39 UTC132 views4 reactionsread 9 August 2026
Photo

🌿🌿🌿🌿 🥳😞.😣😟 В четверг 25.06 в 19:00 Собираю баньку для своих. Приглашаю всех желающих! Кто желает хорошего пара в шикарной компании Открытых и любящих жизнь людей, пишите мне в личку или тут под постом. Даже если мы пока не знакомы лично))) Паримся, общаемся, практикуем. Баня это целый процесс и ритуал. Очищение и перезагрузка по полной. С нами классные пар мастера. Травы для парной и профессиональные веники. Алк…

❤3🔥1

20 Jun 2026, 11:39 UTC93 views4 reactionsread 9 August 2026
Video

Кто сейчас на Преме. Пишите в комменты. Встретимся Рад видеть всех!

❤4

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

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

“Король говорит…” (@Korol_Konstantinov), 110 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Korol_Konstantinov.

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.