Telegram RegisterThe public register of Telegram
Telegram profile photo for Колычевский ДК МБУК "КТЦ" г. о. Ступино

Channel

Колычевский ДК МБУК "КТЦ" г. о. Ступино

@kolychevo

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

38subscribers

+0 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-1001780321039
TypeChannel
Username@kolychevo
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged3 times, most recently 8 October 2026
On Telegramt.me/kolychevo

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

383938.57 August 2026 — 38 subscribers10 August 2026 — 38 subscribers5 September 2026 — 39 subscribers13 September 2026 — 38 subscribers7 August 202613 September 2026
4 measurements spanning 37 days. 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 38–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 22:2038-1
5 Sept 2026, 08:5639+1
10 Aug 2026, 21:0038no change
7 Aug 2026, 17:4838first reading

Engagement

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

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.0%

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

Measured over the 17 most recent posts we hold, published 30 January 2025 to 18 February 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

22 Dec 2025, 13:56 UTC91 viewsread 10 August 2026
Photo

🎄Викторина «Путешествие в историю: Твой билет на Кремлёвскую ёлку!» Жителей городского округа Ступино приглашают принять участие в увлекательной викторине, которая позволит не только проверить свои знания истории родного края, но и получить шанс выиграть билеты на одно из самых масштабных и ярких новогодних событий страны — Кремлёвскую ёлку. Для участия необходимо: 1. Навести камеру смартфона на QR-код и перейти в …

9 Oct 2025, 05:19 UTC97 viewsread 10 August 2026
Forwarded from @volontermoPhoto

❤️‍🔥 Стань «Амбассадором добра»! В Московской области объявлен конкурс амбассадоров регионального движения «Волонтёры Подмосковья». До 19 октября в каждом муниципалитете области пройдёт внутренний отбор среди представителей волонтёрских организаций. В рамках него каждому кандидату предстоит выполнить конкурсное задание. По окончании этого этапа будет сформирована группа из 200 ребят, которые примут участие в регион…

12 Apr 2025, 08:33 UTC170 viewsread 10 August 2026
Forwarded from @MuzhalskihPhoto

🚀Дорогие друзья, поздравляю с Днём космонавтики! 12 апреля 1961 года Юрий Гагарин стал первым человеком, вышедшим в космическое пространство. 64 года назад наш летчик-космонавт совершил орбитальный полёт вокруг Земли на корабле «Восток». Открытие космической эры стало поворотным событием для всего человечества, а легендарный полёт - триумфом нашей страны. Ступино внес большой вклад в развитие авиационно-космическо…

8 Apr 2025, 16:45 UTC130 viewsread 10 August 2026
Forwarded from @Stupino_goPhoto

✨Фестиваль «Город танцует в парках» объявляет старт приема заявок со всей России Фестиваль современного танца пройдет в парках Подмосковья под художественным руководством заслуженного артиста РФ и хореографа Егора Дружинина. Откроется фестиваль 17 мая концертом с участием танцоров со всей России. 🏆Участники из Подмосковья поборются за звание лучшего коллектива с 18 мая по 28 июня. ❓Кто может оставить заявку? К уч…

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

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

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

“Колычевский ДК МБУК "КТЦ" г. о. Ступино” (@kolychevo), 38 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/kolychevo.

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.