Channel
@code_on_tg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
8,914subscribers
-134 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001641747805 |
|---|---|
| Type | Channel |
| Username | @code_on_tg |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/code_on_tg |
Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 12 Oct 2026, 14:41 | 8,914 | -16 |
| 5 Oct 2026, 19:59 | 8,930 | -14 |
| 28 Sept 2026, 11:41 | 8,944 | -20 |
| 18 Sept 2026, 15:40 | 8,964 | -9 |
| 14 Sept 2026, 11:57 | 8,973 | -7 |
| 11 Sept 2026, 00:21 | 8,980 | -10 |
| 5 Sept 2026, 16:41 | 8,990 | -6 |
| 1 Sept 2026, 19:36 | 8,996 | -9 |
| 29 Aug 2026, 16:44 | 9,005 | -6 |
| 26 Aug 2026, 06:18 | 9,011 | -5 |
| 23 Aug 2026, 14:58 | 9,016 | -3 |
| 20 Aug 2026, 03:06 | 9,019 | -10 |
| 17 Aug 2026, 12:05 | 9,029 | -9 |
| 14 Aug 2026, 10:34 | 9,038 | -5 |
| 10 Aug 2026, 19:15 | 9,043 | -3 |
| 7 Aug 2026, 16:54 | 9,046 | -2 |
| 7 Aug 2026, 03:17 | 9,048 | first reading |
73 posts held, back to 29 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 35 pages 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 73 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
14 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 28.6% | |
| 😁 | 4 | 28.6% | |
| ❤ | 3 | 21.4% | |
| 🔥 | 2 | 14.3% | |
| 👏 | 1 | 7.14% |
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 9 of the 73 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 73 most recent posts we hold, published 29 July 2026 to 28 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.
Делаем нейросеть с нуля Как бы вас не запугивали, нейросети писать не сложно и можно сделать это даже в 90 строк кода. Достаточно просто хорошо разбираться в математике. Автор рассказывает про принципы работы нейронных сетей и создаёт проекты на их основе. Например, определение числа на основе пикселей. Подробнее: 👉 тут #видео #ai ⬇️ Скачать видео Кодим на Коленке
📣Универсальный держатель Цена: ~1300₽ Рейтинг: 5😀 Отзывы: 119 💬 🖱 Заказать Универсальный регулируемый держатель для планшета или телефона, поможет удобно разместить устройство на кровати или столе, освобождая руки для просмотра видео, чтения, работы и учёбы. #держатель #девайс Больше товаров — Находки Программиста
#meme Кодим на Коленке
Уроки #Android Studio для начинающих Видеоуроки: 1. Создание Андроид приложения (E-Commerce) 2. Дизайн основного окна 3. Категории товаров 4. Основные товары приложения 5. Страница с товаром 6. Переход между страницами с анимацией 7. Сортировка товаров по категориям 8. Добавление в корзину 9. Заключительный урок 🗝 Смотреть курс Кодим на Коленке & Скачать видео
Что такое Kubernetes? Контейнеризация проектов — это то, что отлично упрощает перенос проектов на разные устройства, а также позволяет контролировать использование ресурсов. Для работы с контейнерами был придуман Kubernetes. Автор видео подробно рассказал о контейнерах и в общих чертах описал, как ими пользоваться. Подробнее: 👉 тут #видео #devops ⬇️ Скачать видео Кодим на Коленке
#Вопрос_с_собеседования За что отвечает команда git stash? Ответ: Команда git stash позволяет на время «сдать в архив» (или отложить) изменения, сделанные в рабочей копии, чтобы вы могли применить их позже Кодим на Коленке
Нашел 10 репозиториев на GitHub для изучения ИИ-агентов 1. ИИ-агенты для начинающих (Microsoft) — github.com/microsoft/ai-a 2. Бесплатные ресурсы по ИИ-агентам — github.com/avinash201199/ 3. Потрясающие приложения на основе больших языковых моделей — github.com/Shubhamsaboo/a 4. Курс Hugging Face Agents — github.com/huggingface/ag 5. GenAl Agents (учебные материалы + реализации) — github.com/NirDiamant/Gen 6. Потряс…
#meme Кодим на Коленке
#Вопрос_с_собеседования Чем отличается энумератор map от each в Ruby? Ответ: each возвращает исходный массив, а . map - новый массив Кодим на Коленке
Хватайте 7 репозиториев на GitHub для изучения больших языковых моделей Вам не нужно читать десятки случайных руководств, чтобы разобраться в больших языковых моделях. Эти 7 проектов на GitHub помогут вам пройти путь от основ трансформеров до самостоятельного создания и обучения языковых моделей. 1. Создание больших языковых моделей с нуля — Себастьян Рашка → Пошаговое создание большой языковой модели с помощью Py…
Учебный курс «Язык SQL» В этом курсе вы без предварительной подготовки сможете разобраться, что представляет собой система баз данных PostgreSQL, и научиться с ней работать. Начиная с разработки простых запросов на языке SQL вы постепенно осваиваете более сложные конструкции (такие как общие табличные выражения), знакомитесь с концепцией транзакций и вопросами оптимизации производительности. Учебные примеры использу…
#meme Кодим на Коленке
Showing the 12 most recent of 73 posts we hold for @code_on_tg. 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.
@code_on_tg edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Кодим на Коленке | Уроки по программированию” (@code_on_tg), 8,914 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/code_on_tg.
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.