Telegram RegisterThe public register of Telegram
Telegram profile photo for Каховка Молодая

Channel

Каховка Молодая

@KahovkaMolodaya

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

260subscribers

-4 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002461971315
TypeChannel
Username@KahovkaMolodaya
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live11 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 11 September 2026
On Telegramt.me/KahovkaMolodaya

Topic

Local community — 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 95% 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

2602642629 August 2026 — 264 subscribers9 August 2026 — 264 subscribers17 August 2026 — 262 subscribers1 September 2026 — 260 subscribers9 August 20261 September 2026
4 measurements spanning 23 days, net -4. 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 259–265 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 19:25260-2
17 Aug 2026, 18:15262-2
9 Aug 2026, 17:22264no change
9 Aug 2026, 15:47264first reading

Engagement

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

Reaction mix

79 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 27.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53057961641703133312227.8%
custom 53053485340887851991620.3%
custom 53054146851750823281620.3%
custom 53052559002341475231417.7%
custom 546328327765573096178.86%
custom 530560390425427364133.80%
custom 535530860728814129211.27%

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

Measured over the 7 most recent posts we hold, published 19 April 2026 to 6 May 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

6 May 2026, 18:15 UTC344 views22 reactionsread 9 August 2026
Photo

Друзья, мы будем скучать! Вместе с вами мы проделали путь в мир молодежной политики. Благодаря вам мы узнали какие замечательные ребята живут на территории Каховского округа. За время работы вместе мы смогли организовать межмуниципальный форум "Маяки Каховки", стать организаторами ряда региональных молодежных форумов в Центре созидания "Маяк", где участие каховской молодежи уже стало неотъемлемой частью всех програм…

custom 53053485340887851998custom 54632832776557309617custom 53057961641703133314custom 53054146851750823282custom 53553086072881412921

3 May 2026, 17:20 UTC171 views0 reactionsread 9 August 2026
Photo

Кстати, мы теперь есть в МАХ. Переходи по ссылке ЖМИ 👆

26 Apr 2026, 17:21 UTC198 viewsread 9 August 2026
Photo

Кстати, мы теперь есть в МАХ. Переходи по ссылке ЖМИ 👆

22 Apr 2026, 19:10 UTC173 views21 reactionsread 9 August 2026
Forwarded from @filipchukpPhoto

❤️Каховская молодежь задает темп! Наши юнармейцы вернулись с регионального форума «Задавай шаг и действуй», который проходил в Центре созидания «Маяк». И вернулись не с пустыми руками! Форум объединил самых заряженных ребят области: 🔵 Юнармейцев и волонтеров Победы; 🔵 Курсантов центра «Воин»; 🔵 Кадетов при СУ СК по Херсонской области. Чему учились? Программа была максимально насыщенной. Ребята прокачивали навыки, …

custom 53054146851750823289custom 53052559002341475236custom 53057961641703133316

20 Apr 2026, 05:08 UTC≈5,430 views15 reactionsread 9 August 2026
Photo

Лови волну волонтёрских возможностей на форуме «Юг Молодой» Центр созидания «Маяк» ведёт набор в команду волонтёров на Всероссийский молодёжный образовательный форум «Юг Молодой» 🔥 Что тебя ждёт? - Азовское море - очный формат обучения - море энергии и друзей - уникальный мерч - сертификат о прохождении курса - крутое пополнение в портфолио - место в кадровом резерве Центра «Маяк» - волонтёрские баллы Мест не так …

custom 53052559002341475235custom 53054146851750823285custom 53057961641703133315

19 Apr 2026, 17:20 UTC177 views10 reactionsread 9 August 2026
Photo

Кстати, мы теперь есть в МАХ. Переходи по ссылке ЖМИ 👆

custom 53057961641703133314custom 53053485340887851993custom 53056039042542736413

19 Apr 2026, 07:33 UTC≈3,970 views11 reactionsread 9 August 2026
Photo

«Путь к свободе: Херсон» — молодёжь Каховки проверила свои силы в исторической настольной игре В Каховке в Молодежном пространстве Молодежным центром «Таврический» была организована встреча: ребята стали участниками настольной игры, посвященной героическим страницам истории нашей области. 👆 Проект разработан Анастасией Сорокой в рамках конкурса #РосмолодёжьГранты. Это не просто «настолка», а настоящее погружение в …

custom 53053485340887851995custom 53052559002341475233custom 53057961641703133313

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

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.

Mentions

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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“Каховка Молодая” (@KahovkaMolodaya), 260 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/KahovkaMolodaya.

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.