Channel
@kod_ru
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
404,820subscribers
+404,230 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001196534191 |
|---|---|
| Type | Channel |
| Username | @kod_ru |
| Created | 15 March 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/kod_ru |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 14 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 18 Sept 2026, 05:20 | 404,820 | +1,360 |
| 15 Sept 2026, 20:58 | 403,460 | +1,997 |
| 14 Sept 2026, 02:39 | 401,463 | +8,466 |
| 12 Sept 2026, 07:41 | 392,997 | +1,087 |
| 10 Sept 2026, 03:39 | 391,910 | +1,537 |
| 6 Sept 2026, 18:40 | 390,373 | +230 |
| 4 Sept 2026, 06:16 | 390,143 | +1,079 |
| 2 Sept 2026, 20:27 | 389,064 | +238 |
| 1 Sept 2026, 18:44 | 388,826 | +218 |
| 31 Aug 2026, 18:34 | 388,608 | +296 |
| 30 Aug 2026, 16:24 | 388,312 | +471 |
| 29 Aug 2026, 15:07 | 387,841 | +315 |
| 28 Aug 2026, 12:36 | 387,526 | +299 |
| 27 Aug 2026, 14:17 | 387,227 | +337 |
| 26 Aug 2026, 14:53 | 386,890 | +294 |
| 25 Aug 2026, 11:28 | 386,596 | +467 |
| 24 Aug 2026, 12:57 | 386,129 | -76 |
| 22 Aug 2026, 21:44 | 386,205 | +963 |
| 21 Aug 2026, 10:15 | 385,242 | +240 |
| 20 Aug 2026, 10:53 | 385,002 | first reading |
20 posts held, back to 18 October 2020 — 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 20 posts for this entry, the most recent from 12 September 2024. An engagement rate over an empty window would be a number about nothing.
🤗 Новый Код, новая жизнь // Больше года я вместе с командой SKAM и нашей редакцией работал над новым видением издания. Нужно сказать, что за это время мы пересмотрели сотни дизайнов интернет-изданий и перекроили десятки идей насчёт подхода к IT-медиа и наших продуктов. Новый Код Дурова — это не просто новый дизайн ради нового дизайна. Это новый этап развития, в котором мы не только обновляем айдентику, но и вносим …
Signed Gaik Dallakyan
[KOD V5.0 UPDATE] Installation: ███[][][][][][][] 30% Time to end: 12.09.2024
Signed Gaik Dallakyan
👹 Мем смешной, ситуация страшная //
Signed Aik Dallakyan 🐝
😎
Signed Vlad Voitenko
🧑🏻💻 Код Дурова объявляет конкурс для веб-разработчиков // Призовой фонд: 200 000 рублей. Срок сдачи работ: 25 февраля 23:59 по Московскому времени (UTC+3). Объявление итогов: 3 марта. Задача: Взяв за основу Ghost 4.28.0 и точно следуя предложенному дизайну, написать тему для сайта kod.ru. Приём работ: Мы предлагаем конкурсантам запустить собственный тестовый сервер и присылать нам URL-адрес с уже готовыми работам…
Signed Aik Dallakyan
🤷🏻♂️ Ладно, уговорили //
Signed Aik Dallakyan
🦥 Мы активно работаем над обновлением нашего сайта: kod.ru На данный момент прорабатываем дизайн и готовим обновление к релизу на тестовом сервере. Сейчас активно думаем на тему подключения к сайту — синтеза речи. Как вы считаете нужна ли такая функция? Чего вам не хватает у нас на сайте?
Signed Aik Dallakyan
🦾 «Код Дурова» ищет редактора-новостника Наша небольшая команда скоро станет чуть-чуть больше, поэтому мы ищем ответственного человека, который в курсе последних новостей из мира IT и умеет рассказывать о них быстро, ёмко, грамотно и с огоньком! Пиши нам, если: - знаешь, где и как быстрее всех найти интересные и свежие IT-инфоповоды; - знакомо слово фактчекинг; - умеешь быстро и грамотно писать тексты на русском я…
Signed Aik Dallakyan
🔒Privacy v1.1 Наша команда щепетильно относится к приватности данных наших читателей. В феврале мы отказались от всех трекеров на kod.ru, которые продавали ваши данные третьим лицам, таргетировали рекламу на сайте и давали нам «бесплатную» аналитику. Заменив их на более приватные решения и полностью отказавшись от таргетинга, мы сделали сайт более «чистым». Однако внимательные читатели могли заметить, что на некото…
Signed Aik Dallakyan
Marreti 🚩 : Создать полноценный Android-клиент для Clubhouse можно примерно за 3-4 месяца. Гриша (ex-разработчик Android-клиента Telegram): Парень, подержи-ка мое пиво 🍺 https://kod.ru/clubhouse-android-non-official/
Signed Aik Dallakyan
🤣 Ты, когда вакцинировался от коронавируса! Прислал подписчик Dmitry Shleymovich.
Signed Kirill Sergeew
😍 18+ Мы достали уникальные кадры с шикарной виллы Павла Дурова в Дубае, на которых запечатлен основатель Telegram в момент переговоров с инвесторами, которые хотят конвертировать свои вложения в долю в ходе обязательного IPO. Видео от читателя с именем Oleg Polihronidi
Signed Kirill Sergeew
Showing the 12 most recent of 20 posts we hold for @kod_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.
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.
Named by 19 registered channels — 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Код.ру” (@kod_ru), 404,820 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kod_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.