Channel
@kolychevencyclopedia
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,870subscribers
-95 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001811501396 |
|---|---|
| Type | Channel |
| Username | @kolychevencyclopedia |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/kolychevencyclopedia |
Personal blog — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 15 Sept 2026, 17:57 | 2,870 | -5 |
| 12 Sept 2026, 11:56 | 2,875 | -2 |
| 8 Sept 2026, 16:36 | 2,877 | -12 |
| 3 Sept 2026, 15:18 | 2,889 | -13 |
| 30 Aug 2026, 22:57 | 2,902 | -25 |
| 27 Aug 2026, 13:36 | 2,927 | -23 |
| 24 Aug 2026, 18:07 | 2,950 | -11 |
| 21 Aug 2026, 12:04 | 2,961 | -4 |
| 20 Aug 2026, 13:01 | 2,965 | first reading |
4 posts held, back to 23 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 4 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
60 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 41.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 41.7% | |
| ✍ | 16 | 26.7% | |
| 🤯 | 11 | 18.3% | |
| 💊 | 8 | 13.3% |
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 4 of the 4 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 60 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 23 July 2026 to 17 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.
Хроника пути. Часть 3 Это была славная неделя, что сказать. тяжелые симптомы болезни отступили, стало легче жить и работать. И даже, к моему превеликому счастью, тренироваться. • Тренировки начались с восстановления. Да, силовые просели, вес упал, но тут важнее было просто начать и возобновить. Чуть позже начнется долгая и очень плотная подготовка к соревнованиям. • Работа по проекту TSF идет. Провели около 6 про…
❤6✍4🤯4💊1
Хроника пути. Часть 2 Ну что, дорогие мои, это очередная глава жизнеописания. Да, я не такой крутой, как протопоп Аввакум, но жития свои уже не прочь оформлять... моя болезнь из прошлого поста лишь усугубилась, несколько дней я вообще чуть ли не замертво лежал, поэтому в рамках активности — гулянок, визитов и посещений — я не особо могу чем-то похвастаться. • Начнем с самого интересного... Господь благоволит и пом…
❤6✍5💊3🤯1
Хроника пути. Часть 1 Да, я чутка профукал со сроком — прошло больше недели, но себе в обеление скажу: я караул как заболел, и сил на подобную графоманию у меня просто-напросто не было. Сегодня чуть МОЩЬ вернулась — и я сразу решил направить ее в нужное русло. • Начнем с книг. Удалось наконец-то закончить уже мне сильно надоевшего "Доктора Живаго" — понял, что не моя книга. От слова "совсем". Да, прикольные идеи, …
❤7✍5🤯5💊1
Давайте немножко познакомимся. На этот канал, помимо моей целевой аудитории из маркетинговых и иных инфо-проектов, подписано еще многих прочих ребят — в большинстве своем из сферы онлайн-образования. Изначально на канале было под 5 тысяч аудитории, с течением времени и постами типа этого происходил, как говорится в оправдательной политике, "негативный рост". Лишние уходили, новые приходили, те, кому интересно, остал…
❤6💊3✍2🤯1
Showing the 4 most recent of 4 posts we hold for @kolychevencyclopedia. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Колычев о пути” (@kolychevencyclopedia), 2,870 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kolychevencyclopedia.
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.