Telegram RegisterThe public register of Telegram

Channel

Котатограм

@kotatogram_ru

On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry

962subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001327745789
TypeChannel
Username@kotatogram_ru
DescriptionЭкспериментальный форк Telegram Desktop от @EricKotato. GitHub: https://github.com/kotatogram/kotatogram-desktop Блоги разработки: @kotatogram_dev_ru On English: @kotatogram Билды: #WindowsInstaller #Windows #Linux64 #AppImage #macOS
Created21 September 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/kotatogram_ru

Growth

9626 Aug 2026, 21:19 — 962 subscribers6 Aug 2026, 21:30 — 962 subscribers6 Aug 2026, 21:196 Aug 2026, 21:30
2 measurements taken within a single day. 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 961–963 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 21:30962no change
6 Aug 2026, 21:19962first reading

Engagement

10 posts held, back to 31 December 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 2 January 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
9
Links
38

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

2 Jan 2024, 11:00 UTC≈13,800 viewsread 6 August 2026

Новый тестовый билд и новый канал для блогов разработки Я немного обдумал, как лучше сделать, и решил, что здесь я буду делать краткие сводки по прогрессу обновления, а сами посты по разработке будут в отдельном канале. Итак, для начала, новый канал: https://t.me/kotatogram_dev_ru Начал я с того, что решил обновить ветку patches-track-4.8.4 до 4.14. На удивление, это заняло меньше времени, чем я ожидал, поэтому я

31 Oct 2023, 02:55 UTC≈12,000 viewsread 6 August 2026
Poll

Как лучше поступить с блогами разработки?

  1. Постить их сюда78%
  2. Сделать отдельный канал для них8%
  3. Постить их на сайте, а ссылки постить здесь8%
  4. Постить их на сайте, а ссылки на канале с тестовыми версиями4%
  5. Другой вариант (добро пожаловать в комментарии!)2%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

31 Oct 2023, 02:13 UTC≈8,570 viewsread 6 August 2026

Про состояние Котатограма Молчание затянулось, и всё больше людей приходит спрашивать в комментарии, почему, или же вовсе хоронить клиент. Итак, разъясню ещё раз: Котатограм не мёртв. Сейчас у меня нет времени полноценно им заняться. Однако прогресс есть. Устав от многочисленных конфликтов слияния, я сделал ветку patches-track. Это вспомогательная ветка, где каждое изменение в отдельном коммите вместо хронологичес

19 Aug 2022, 15:23 UTC≈16,300 viewsread 6 August 2026

Так как Telegram повально отзывает юзернеймы каналов, которые он считает неактивными, то уточню: Котатограм не мёртв, апдейт скоро будет.

8 Mar 2022, 21:18 UTC≈19,000 viewsread 6 August 2026

Вышла новая версия! 1.4.9 (TD 3.5.2) Изменения • Внутренняя переработка настроек Kotatogram. • Перезапуск для сохранения настроек Kotatogram теперь можно отложить. • Выбор времени при переходе к дате в чате. • Экспериментальные настройки Telegram Desktop теперь отображаются всегда. • Цвета иконки рядом с именем сообщения теперь те же, что и у самих имён. • Исправлена обрезка аватарки в системных уведомлениях Windows

31 Dec 2021, 17:11 UTC≈9,520 viewsread 6 August 2026

Вышла новая версия! 1.4.8 (TD 3.3) Этот релиз весьма неожиданный, но важный, из-за критичного вылета в «Избранном» (Saved Messages). Если вы на него не наткнулись, вам повезло, но всё же лучше обновиться. Изменения • Улучшенные настройки шрифтов. Благодаря стараниям @Shlyupa, теперь в настройках шрифта есть их полный список для каждого поля, а также есть слайдер для изменения размера шрифта. Ранее размер шрифта мож

31 Dec 2021, 11:12 UTC≈4,770 viewsread 6 August 2026

Вышла новая версия! 1.4.7 (TD 3.3) Последний релиз в этом году, необходимый, потому что кто знает, что будет, если стабильная ветка не получит обновление до 1 января. К счастью, «успеть до 1 января» не единственная суть релиза: новые функции тоже имеются в наличии. Изменения с прошлой бета-версии • Вместо снятия ограничения на размер окна теперь изменены минимальные размеры самого окна. Это выполняет ту же задачу,

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

31 Oct 2023, 02:55 UTCFinal Results362 voters

Как лучше поступить с блогами разработки?

  1. Постить их сюда78%
  2. Сделать отдельный канал для них8%
  3. Постить их на сайте, а ссылки постить здесь8%
  4. Постить их на сайте, а ссылки на канале с тестовыми версиями4%
  5. Другой вариант (добро пожаловать в комментарии!)2%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 10 most recent posts we hold, published 31 December 2021 to 2 January 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 479,960 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Котатограм” (@kotatogram_ru), 962 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/kotatogram_ru.

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.