Telegram RegisterThe public register of Telegram
Telegram profile photo for Типичный программист

Channel

Типичный программист

@tproger

Verified by Telegram2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

78,305subscribers

-762 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001044298783
TypeChannel
Usernames@tproger @tproger_official
DescriptionВсё самое интересное по программированию Разместить рекламу: @tproger_sales_bot Правила общения: https://tprg.ru/rules Другие каналы: @tproger_channels Сайт: https://tprg.ru/site VK: vk.com/tproger Регистрация в перечне РКН: https://tprg.ru/mJwo
Created11 March 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live24 September 2026
Measurements held69
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/tproger

Topic

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 20 August 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

78,30579,13978,7225 August 202624 September 2026
69 measurements spanning 50 days, net -762. 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 78,180–79,264 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 69
Measured (UTC)SubscribersChange
24 Sept 2026, 20:5878,305-264
18 Sept 2026, 16:0178,569-1
18 Sept 2026, 12:2178,570-11
16 Sept 2026, 10:1778,581+2
16 Sept 2026, 07:5778,579+4
14 Sept 2026, 16:5878,575-5
13 Sept 2026, 03:1778,580no change
13 Sept 2026, 02:0178,580-15
11 Sept 2026, 07:5678,595+3
11 Sept 2026, 01:5678,592+6
8 Sept 2026, 14:5978,586+7
8 Sept 2026, 03:3578,579-50
5 Sept 2026, 10:5778,629+8
4 Sept 2026, 21:4178,621-21
3 Sept 2026, 13:2178,642-8
3 Sept 2026, 07:5578,650-37
2 Sept 2026, 04:5578,687-1
2 Sept 2026, 04:1278,688+2
1 Sept 2026, 07:1578,686+3
1 Sept 2026, 04:0478,683first reading

Engagement

179 posts held, back to 27 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 114 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.52%
avg views ÷ 78,305 subscribers
Avg views / post
6,670
109 posts measured
Reaction rate
0.538%
reactions ÷ views · ER floor
Posts in window
109
of 179 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held179 (27 July 2026 – 27 September 2026)
Views total727,499
Reactions total3,916
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 05:13 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈3,750
Videos
≈1,160
Links
≈8,390

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 42s
Average length
2m 42s

Measured directly from 1 video 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.

Reaction mix

6,912 reactions across 175 posts, in 65 distinct kinds. The most used accounts for 16.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,17116.9%
❤1,05015.2%
🔥6679.65%
😁6419.27%
👏3625.24%
🤣3505.06%
💊2723.94%
🎉2163.13%
💯1922.78%
🤔1622.34%
👎1241.79%
🤝1051.52%
✍931.35%
🤯901.30%
👌851.23%
🌚811.17%
⚡781.13%
👀590.854%
🤩570.825%
🙈550.796%
45 further kinds1,00214.5%

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

Measured over the 179 most recent posts we hold, published 27 July 2026 to 27 September 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.

Telegram Stars

Stars received
16
across the posts below
Posts paid on
13
of 179 we hold a reading for · 7%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tproger. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 179 most recent posts we hold for this entry, published 27 July 2026 to 27 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.559%
1 of 179 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
5,600
over 1 measured post
Median views · rest
7,050
over 178 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFJrVGHw124 September 202624 September 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 179 most recent posts we hold, published 27 July 2026 to 27 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

27 Sept 2026, 05:01 UTC209 views2 reactionsread 27 September 2026
Photo

Как научить небольшую языковую модель соблюдать структуру ответа Модель на 350 млн параметров дообучили всего за 100 шагов и подняли результат в IFStruct с 22,6% до 29,7%. Этот тест проверяет, выдаёт ли модель корректный JSON или YAML по заданной схеме, а не просто правдоподобный текст. Для обучения взяли около 500 примеров и метод группового сравнения ответов GRPO. Модель получала награду за три вещи: ответ можно …

👻1😴1

26 Sept 2026, 20:01 UTC≈2,640 views19 reactionsread 27 September 2026
Photo

Почему JOIN с блокировкой строки может вернуть пустоту в PostgreSQL Строка есть, внешний ключ заполнен, но INNER JOIN ничего не возвращает. Это возможно, когда две транзакции одновременно меняют связанную запись. В Read Committed PostgreSQL после снятия блокировки перепроверяет условие JOIN по новой версии строки, но связанную запись не загружает заново. Условие больше не совпадает: INNER JOIN отбрасывает строку, а…

🤯7🔥2🤔2☃1⚡1❤1🎉1👌1

26 Sept 2026, 17:04 UTC≈3,960 views25 reactionsread 27 September 2026
Photo

Как передавать Minecraft-сервер между компьютерами игроков Экзамены одного игрока выключили Minecraft-сервер для всей компании на неделю: мир работал только на его компьютере. В ответ появился Nomad, который позволяет запускать тот же мир у любого участника. Проект выбирает хоста через файл lease.json в общем хранилище. Если два игрока запускают сервер одновременно, условная запись разрешает это только одному. Хост…

❤8👍4👏4🎉2⚡1💊1🤷‍♂1🦄1

26 Sept 2026, 14:07 UTC≈3,960 views22 reactionsread 27 September 2026
Photo

Как GitHub перенёс движок Copilot на Rust силами Copilot GitHub переписал общий движок Copilot с TypeScript на Rust: вышло более 800 тысяч строк производственного кода. Большую часть написали ИИ-агенты, а 128 пул-реквестов вливали в основную ветку и выпускали постепенно. Раньше каждое приложение через SDK запускало отдельный процесс с Node.js и V8. Это означало минимум около 100 МБ памяти и обмен данными между проц…

🤔4🤗4✍2👎2🦄2😎2😴2🍾1

26 Sept 2026, 11:10 UTC≈4,050 views22 reactionsread 27 September 2026
Forwarded from @tproger_webPhoto

Как читать HTML-реликты из эпохи браузерных войн В старом head можно встретить строки, смысл которых уже не восстановить по имени. Например, X-UA-Compatible заставлял Internet Explorer выбирать самый новый доступный режим документа, а условные комментарии показывали разную разметку отдельным версиям браузера. Другие теги защищали страницу от вмешательства сторонних программ. Skype Toolbar превращал номера телефонов…

🤔5👀3🍾2👌2👍2👾2🔥2☃1

25 Sept 2026, 15:02 UTC≈4,760 views38 reactionsread 27 September 2026
Photo

Как реализовать приложения в гибриде? Гибридная инфраструктура хороша тем, что позволяет не держать всю нагрузку в одном месте. Например, часть ресурсов можно оставить on-premises, а переменную или более тяжёлую нагрузку переносить в облако — в зависимости от требований и стоимости. В Yandex Cloud для этого есть Cloud Interconnect: он соединяет разные контуры по приватному соединению без выхода в интернет. BareMeta…

❤10👍8👏5🔥3👌2👎2🤷‍♂2🫡2

24 Sept 2026, 10:04 UTC≈5,600 views30 reactionsread 27 September 2026
Advertisementerid 2W5zFJrVGHwPhoto

А вы уже забрали свой подарок ко Дню программиста? К вашему профессиональному празднику Tproger, Proglib, Столото, Центральный университет и SmartApe собрали целую коробку подарков. Переходите по ссылке, трясите коробку и забирайте свой презент: https://tprg.ru/edsw Реклама. ИП Михайлишина Гузель Фаниловна, erid: 2W5zFJrVGHw

🤔4🥰4🫡4🍓3🎉3👎3🍾2💊2

22 Sept 2026, 11:13 UTC≈7,250 views36 reactionsread 27 September 2026
Photo

Кто должен решать, к данным какого клиента обращается ИИ-агент Модель может составить безупречный вызов инструмента и запросить договор из чужого аккаунта. Схема верна, аргумент подходит, но договор принадлежит другому клиенту. Более строгий промпт снизит риск, однако границей авторизации не станет. Автор собрал экспериментальную Rust-библиотеку TenantInvariant. Модель передаёт только идентификатор ресурса, сервер …

👏9❤7🤝4😢3🎃2🎅2👎2💯2

22 Sept 2026, 07:29 UTC≈7,000 views39 reactionsread 27 September 2026

Архитектор решений: чем он занимается и как войти в профессию Одна пропущенная система на схеме может обернуться сдвигом сроков и ростом бюджета: её доработку просто не заложат в проект. Архитектор решений должен заметить такой промах до реализации. Он разбирает бизнес-требования на функции, распределяет их по системам и проектирует обмен данными между ними. Результат: архитектурный вижен, то есть диаграммы систем,…

❤13🔥9⚡3🎉3👍3🤔3🌚1👎1

21 Sept 2026, 17:22 UTC≈6,730 views34 reactionsread 27 September 2026
Photo

Иногда важнее понять, как всё устроено, чем выучить очередной инструмент. Эти статьи про логику и процессы: без привязки к конкретным технологиям, зато с идеями, которые пригодятся в любой команде. Будет полезно командам и разработчикам, которые хотят больше понимания процессов на уровне концепций! Как выстроить работу с выделенной командой Как работает IT-команда: путь задачи от бэклога до релиза 7 стратегий модерн…

🔥9👍8❤‍🔥3🆒3😁2😐2🙉2🙊2

21 Sept 2026, 07:54 UTC≈6,460 views51 reactionsread 27 September 2026
Photo

Как раздать 8,8 Гбит/с видео на одном ядре Go Ошибочно отправленная ссылка уложила сервер: зрители одновременно открыли HLS-трансляцию, память закончилась, потоки оборвались. Автор собрал Ruseon Core на Go без перекодирования видео. Кадр один раз попадает в буфер, а зрители читают те же байты. Отстающему подписчику сервер пропускает кадры до следующего ключевого, поэтому не хранит отдельную очередь видео для каждог…

👍21👏13🤩3😈3😴3🐳2🙈2💋1

20 Sept 2026, 18:21 UTC≈6,800 views61 reactionsread 27 September 2026
Photo

Как повторное использование ReverseProxy ускорило прокси на Go в 3,8 раза Автор нагрузил свой обратный прокси и обнаружил хвост медленных запросов. Причина оказалась в обработчике: тот создавал новый httputil.ReverseProxy для каждого запроса. Вместе с прокси заново создавался http.Transport. Соединения с целевым сервером не переиспользовались, поэтому каждый запрос платил за новое подключение. Исправление: хранить …

👍14👏12❤10🏆6👀6🙉4👌3🎉2

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

Named by 9 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

IT Юмор
@ithumor · 60,568
#1
Хабр
@habr_com · 132,465
#2
Библиотека программиста
@proglibrary · 78,288
#3
Веб-страница
@tproger_web · 22,429
#4
Rozetked
@rozetked · 656,361
#5
Код.ру
@d_code · 406,147
#6
Представляешь,
@your_tech · 8,748
#7
Programmer & IT Memes
@itmemes · 123,290
#8
Zen of Python
@zen_of_python · 18,830
#9
CodeCamp
@codecamp · 181,043
#10
Инструменты программиста
@prog_tools · 12,940
#11
Мобильная разработка
@mobi_dev · 13,170
#12
Журнал «Код»
@thecodemedia · 49,232
#13
addmeto
@addmeto · 71,835
#14
Точка входа в программирование
@prog_point · 18,040
#15
r/ретранслятор
@retra · 165,571
#16
vc.ru
@vcnews · 112,033
#17
Denis Sexy IT 🤖
@denissexy · 137,325
#18
Programmer memes
@programmer_memes · 51,307
#19
FrontEndDev
@front_end_dev · 25,875
#20
Clean Code
@codeclean · 12,039
#21
The After Times
@theaftertimes · 16,799
#22
Библиотека Go-разработчика | Golang
@goproglib · 24,076
#23
Не баг, а фича
@bugfeature · 571,363
#24
Код найма
@soft_skillz · 5,312
#25
Нейроканал
@neuro_channel · 11,778
#26
Сохранёнки программиста
@prog_stuff · 6,533
#27
Библиотека питониста | Python, Django, Flask
@pyproglib · 37,384
#28
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,930
#29
Технотренды
@techno_media · 790,765
#30
BZD • Книги для программистов
@bzd_channel · 36,402
#31
Библиотека шарписта | C#, F#, .NET, ASP.NET
@csharpproglib · 21,700
#32
Frontender's notes [ru]
@frontendnoteschannel_ru · 31,430
#33
эйай ньюз
@ai_newz · 96,889
#34
Рестарт
@remedia · 698,207
#35
WebDEV
@webb_dev · 8,299
#36
Яндекс
@yandex · 606,530
#37
Метод утёнка
@devs_books · 6,691
#38
hahacker_news
@hahacker_news · 25,571
#39
Machinelearning
@ai_machinelearning_big_data · 279,417
#40
Хабр Новости
@habr_com_news · 12,441
#41
Neural Shit
@NeuralShit · 53,680
#42
ЗаТелеком 🌐
@zatelecom · 64,498
#43
ТЕХНО: Яндекс про технологии
@techno_yandex · 224,759
#44
XOR
@xor_journal · 182,317
#45
Yandex for Developers
@Yandex4Developers · 28,545
#46
Рабы галерные
@rabynagalerah · 8,733
#47
Двач
@dvachannel · 938,773
#48
Эксплойт
@exploitex · 2,048,279
#49
Говнокод
@g_code · 14,872
#50
Mash
@mash · 3,110,586
#51
Раньше всех. Ну почти.
@bbbreaking · 1,974,402
#52
Ньюсач/Двач
@ru2ch · 676,175
#53
Бэкдор
@whackdoor · 1,603,481
#54
NOP::Nuances of Programming
@nuancesprog · 56,542
#55
Медуза — LIVE
@meduzalive · 1,122,482
#56
Varlamov News
@varlamov_news · 1,061,005
#57
Лентач
@lentachold · 392,921
#58
Пекарня
@pekagame · 1,089,162
#59
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,108,884
#60
THINGS PROGRAMMERS DO
@thingsprogrammersdo · 16,037
#61
Пикабу
@pikabu · 255,824
#62
Лентач
@oldlentach · 261,008
#63
GitHub Community
@github · 155,991
#64
Артемий Лебедев
@temalebedev · 970,618
#65
Reddit
@Reddit · 162,484
#66
Программист
@progeri · 15,108
#67
NN
@naebnet · 2,178,705
#68
Банкста
@banksta · 438,371
#69
Минцифры России
@mintsifry · 234,926
#70
Дудь
@yurydud · 862,341
#71
твиттота
@twitt_ota · 331,915
#72
Лепра
@Lepragram · 341,971
#73
Big Geek
@biggeekru · 581,535
#74
Physics.Math.Code
@physics_lib · 146,712
#75
GameDev: разработка игр
@make_game · 7,629
#76
Yaplakal.com
@yaplakal · 421,771
#77
Go in Action
@go_in_action · 4,110
#78
VG/Двач
@ru2chvg · 181,977
#79
MDK
@mudak · 533,284
#80
Golang
@Golang_google · 40,461
#81
Т-Инвестиции
@tb_invest_official · 528,596
#82
[BadComedian]
@TheBadComedian · 605,674
#83
СТАС БОМБИТ
@ikakprosto · 326,616
#84
Типичный Сисадмин
@sysodmins · 38,088
#85
Библиотека IT-мемов
@itmemlib · 9,576
#86
.NET / C#
@dot_net_c_sharp · 3,835
#87
4chan
@ru4chan · 180,454
#88
Чашечка Java
@a_cup_of_java · 8,400
#89
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 22,022
#90
Не баг, а фича
@bugnotfeature · 1,065,433
#91
Metanit
@metanit · 8,052
#92
DTF
@dtfbest · 57,722
#93
Утечки информации
@dataleak · 119,401
#94
Кинопоиск | Фильмы и сериалы
@kinopoisk · 804,634
#95

Read from Telegram’s recommendation API, most recently 19 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

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.

Веб-страница
@tproger_web · 22,429
Telegram ranks this channel #1 of 96 here — alongside 95 others — read 20 September 2026
IT Юмор
@ithumor · 60,568
Telegram ranks this channel #1 of 94 here — alongside 93 others — read 22 August 2026
Библиотека программиста
@proglibrary · 78,288
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 19 August 2026
Уголок программиста
@conhum · 20,678
Telegram ranks this channel #3 of 89 here — alongside 88 others — read 26 September 2026
Журнал «Код»
@thecodemedia · 49,232
Telegram ranks this channel #3 of 97 here — alongside 96 others — read 25 August 2026
Хабр
@habr_com · 132,465
Telegram ranks this channel #7 of 92 here — alongside 91 others — read 13 August 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,930
Telegram ranks this channel #10 of 93 here — alongside 92 others — read 25 September 2026
TechNews
@techlucker · 43,532
Telegram ranks this channel #10 of 79 here — alongside 78 others — read 28 August 2026
[404] — программирование
@procode404 · 40,506
Telegram ranks this channel #11 of 83 here — alongside 82 others — read 30 August 2026
BZD • Книги для программистов
@bzd_channel · 36,402
Telegram ranks this channel #12 of 57 here — alongside 56 others — read 1 September 2026
Библиотека питониста | Python, Django, Flask
@pyproglib · 37,384
Telegram ranks this channel #12 of 84 here — alongside 83 others — read 1 September 2026
Английский для программиста | EnglishScript
@EnglishScript · 45,107
Telegram ranks this channel #13 of 82 here — alongside 81 others — read 27 August 2026
FrontEndDev
@front_end_dev · 25,875
Telegram ranks this channel #16 of 95 here — alongside 94 others — read 13 September 2026
hahacker_news
@hahacker_news · 25,571
Telegram ranks this channel #20 of 59 here — alongside 58 others — read 14 September 2026
медиатрендс
@mediatrends · 584,160
Telegram ranks this channel #23 of 90 here — alongside 89 others — read 13 September 2026
Physics.Math.Code
@physics_lib · 146,712
Telegram ranks this channel #23 of 72 here — alongside 71 others — read 13 August 2026
Programmer memes
@programmer_memes · 51,307
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 24 August 2026
Хабр Карьера
@habr_career · 33,171
Telegram ranks this channel #26 of 97 here — alongside 96 others — read 4 September 2026
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 78,781
Telegram ranks this channel #26 of 90 here — alongside 89 others — read 18 August 2026
The ExtremeCode Times
@extremecode · 35,596
Telegram ranks this channel #27 of 93 here — alongside 92 others — read 2 September 2026
Python Academy
@python_academy · 44,284
Telegram ranks this channel #27 of 87 here — alongside 86 others — read 28 August 2026
Programmer & IT Memes
@itmemes · 123,290
Telegram ranks this channel #27 of 95 here — alongside 94 others — read 13 August 2026
Простой Python | Программирование
@python_piton_javascript · 126,249
Telegram ranks this channel #29 of 84 here — alongside 83 others — read 13 August 2026
Двоичный кот
@binarcat · 30,827
Telegram ranks this channel #30 of 93 here — alongside 92 others — read 9 September 2026

This channel appears in 68 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Типичный программист” (@tproger), 78,305 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/tproger.

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.