Telegram RegisterThe public register of Telegram

Channel

Yandex for Developers

@Yandex4Developers

Verified by Telegram

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

28,550subscribers

-13 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001223541233
TypeChannel
Username@Yandex4Developers
DescriptionКанал Яндекса о технологиях и людях, которые их создают. События: https://events.yandex.ru/ Каналы Яндекса по стекам разработки: https://t.me/addlist/Hrq31w2p1vUyOGZi ________________________________________________ Номер заявления в РКН: 4962241172
Created10 January 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/Yandex4Developers

Growth

28,53528,56528,5505 August 2026 — 28,563 subscribers6 August 2026 — 28,563 subscribers6 August 2026 — 28,564 subscribers7 August 2026 — 28,565 subscribers8 August 2026 — 28,560 subscribers9 August 2026 — 28,553 subscribers10 August 2026 — 28,535 subscribers11 August 2026 — 28,550 subscribers5 August 202611 August 2026
8 measurements spanning 6 days, net -13. 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 28,531–28,570 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:2228,550+15
10 Aug 2026, 14:5128,535-18
9 Aug 2026, 14:1528,553-7
8 Aug 2026, 11:0828,560-5
7 Aug 2026, 13:1828,565+1
6 Aug 2026, 14:4528,564+1
6 Aug 2026, 02:0028,563no change
5 Aug 2026, 22:4528,563first reading

Engagement

9 posts held, back to 23 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.3%
avg views ÷ 28,550 subscribers
Avg views / post
3,520
9 posts measured
Reaction rate
0.465%
reactions ÷ views · ER floor
Posts in window
9
of 9 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 10 August 2026
Posts held9 (23 July 202610 August 2026)
Views total31,640
Reactions total147
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 21:51 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
1,200
Videos
114
Links
819

Lifetime counters from Telegram’s own channel header, read 12 August 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.

Reaction mix

147 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5638.1%
4732.0%
👍3725.2%
🦄64.08%
10.68%

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

Measured over the 9 most recent posts we hold, published 23 July 2026 to 10 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.

Recent posts

10 Aug 2026, 12:03 UTC≈1,910 views12 reactionsread 12 August 2026
Photo

🔥 Делимся первыми спикерами на deep tech night В карточках рассказываем, кто и на какие темы будет выступать на конференции 5 сентября. А чтобы получить доступ к эфиру, задать вопросы экспертам в прямом эфире и первыми посмотреть запись после события, зарегистрируйтесь на сайте. ⏩️ Подробности о докладах и форма регистрации Подписывайтесь: 💬 @Yandex4Developers

🔥82👍2

8 Aug 2026, 09:04 UTC≈3,860 views3 reactionsread 12 August 2026

📕 Разбираемся, как устроен прайсинг Яндекс Go, рассказываем про графовую foundation-модель, которая взяла Best Paper Award на воркшопе ICML, и изучаем опыт инженеров Яндекса в новом дайджесте Yandex for Developers 🚕 Куда сходить 🔴 22 августа — Welcome Times для аналитиков в Москве. На встрече вы познакомитесь с ребятами из команд Яндекс Поиска и Независимого Ecom, узнаете больше об их проектах и пройдёте диагностик

1👍1🔥1

7 Aug 2026, 11:45 UTC≈2,420 views16 reactionsread 12 August 2026
Photo

🥹 Как выжать из железа максимум: эволюция инференса в Алисе Привет, меня зовут Витя Хаймоненко, я разработчик в команде голосовой активации Алисы. Сегодня я расскажу, как мы прошли путь от инференса на чистом C корутинами до современных движков и квантизованных моделей — и какой инженерный опыт из этого вынесли. 🅰️ Железо фиксировано, а модели растут На колонке одновременно крутится несколько нейросетей: 🔴 Актива

👍7🔥54

4 Aug 2026, 12:04 UTC≈3,040 views29 reactionsread 12 August 2026
Photo

☺️ Как мы проапгрейдили робота-доставщика Привет, меня зовут Сергей Гутынин, я руководитель службы системной разработки в Автономном транспорте и роботах. У всякого бизнеса есть требование: масштабироваться. Производство роботов-доставщиков не стало исключением. Мы хотели сделать их умнее, дешевле и автономнее, а саму сборку поставить на поток. Но когда мы подошли к этой задаче, оказалось, что маленькими изменениям

15🔥9🦄5

1 Aug 2026, 09:01 UTC≈5,610 views9 reactionsread 12 August 2026

📕 Автоматизируем базу знаний с AI, строим новое облако для умных устройств Яндекса и запускаем платформу плагинов в Трекере. Об этом и не только — в новом дайджесте Yandex for Developers 🚕 Куда сходить 🔴 13 августа — ML Global Recap’H1 2026 в Москве и онлайн. Поговорим о главных инсайтах про AI и ML с мировых конференций за последние полгода. Обсудим тренды в ризонинге, челленджи в RL-инфраструктуре и многое другое

5👍2🔥2

31 Jul 2026, 13:00 UTC≈3,240 views35 reactionsread 12 August 2026
Photo

📕 Я перепоручил ведение базы знаний AI-агенту — расскажу как Привет, это Толя Панов, CTO Яндекс Карт. Я довольно давно веду базу знаний в Obsidian и, как любой уважающий себя «хомяк», накопил запас необработанных материалов. Это репосты и ссылки из любимых каналов в телеграме, ссылки в to-do-листе и рекомендации книг, которые некогда разобрать. 💡 Основная идея проста: перепоручить ведение базы знаний AI-агенту. Что

🔥15👍137

27 Jul 2026, 12:01 UTC≈4,150 views15 reactionsread 12 August 2026
Photo

⚡️ Успейте зарегистрироваться на Back to Back Уже в эту субботу, 1 августа, состоится Back to Back — новая бэкенд-конференция Яндекса. Она пройдёт сразу в трёх городах — Москве, Белграде и Ереване. Присоединиться можно как офлайн, так и онлайн. Немного о программе: 📍 Москва Савва Лебедев из Positive Technologies расскажет, как команда добавляла поддержку LuaJIT в eBPF-профилировщик Perforator. Даниил Подольский и

8🔥6👍1

25 Jul 2026, 09:03 UTC≈3,610 views5 reactionsread 10 August 2026

📕 Создаём AI-агента прямо в браузере, добавляем в умную колонку новые команды и знакомимся с работой ML-специалистов в Yandex Cloud. Об этом и не только — в новом дайджесте Yandex for Developers 🚕 Куда сходить 🔴 25 июля — Product : Fest. Главный фестиваль Яндекса для продактов уже сегодня! Подключайтесь онлайн: разберём реальные кейсы, сверим подходы, обменяемся опытом и обсудим, как AI меняет нашу работу. Смотрите

3👍1🔥1

23 Jul 2026, 11:45 UTC≈3,800 views23 reactionsread 10 August 2026
Photo

⚡️ Разработка для разработки: проект Amptrace Всем привет, на связи Александр Батин и Олег Артамонов, технические руководители проектов в Алисе AI и Умных устройствах. Порой в ходе разработки у нас возникает проблема: нам нужны измерительные приборы, которых нет на рынке. Готовые решения часто не подходят под специфику задач или слишком дорогие. 👳‍♂️ Что делать? Правильно: создавать их самостоятельно. Об одном так

👍10🔥921🦄1

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

Citation-graph rank

Citation-graph rank — 89,061 of 1,160,990entries 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

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 8 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.

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.

Яндекс
@yandex · 547,158
Telegram ranks this channel #12 of 96 here — alongside 95 others — read 9 August 2026
ТЕХНО: Яндекс про технологии
@techno_yandex · 233,428
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 11 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Yandex for Developers” (@Yandex4Developers), 28,550 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Yandex4Developers.

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.