Telegram RegisterThe public register of Telegram

Channel

Yandex for Backend

@yandexforbackend

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

9,975subscribers

+28 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001868919653
TypeChannel
Username@yandexforbackend
DescriptionКанал для бэкендеров от Яндекса. Рассказываем про события по Python, Go, Java и C++ и не только, делимся экспертизой, обсуждаем технологии и поддерживаем бэкенд-комьюнити. Другие каналы Яндекса по стекам разработки: https://t.me/addlist/Hrq31w2p1vUyOGZi
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/yandexforbackend

Growth

9,9479,9759,9616 August 2026 — 9,947 subscribers6 August 2026 — 9,947 subscribers6 August 2026 — 9,949 subscribers9 August 2026 — 9,960 subscribers12 August 2026 — 9,975 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +28. 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 9,943–9,979 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:159,975+15
9 Aug 2026, 17:029,960+11
6 Aug 2026, 20:239,949+2
6 Aug 2026, 02:499,947no change
6 Aug 2026, 02:029,947first reading

Engagement

9 posts held, back to 24 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 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.0%
avg views ÷ 9,975 subscribers
Avg views / post
2,290
9 posts measured
Reaction rate
0.679%
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 11 August 2026
Posts held9 (24 July 202611 August 2026)
Views total20,620
Reactions total140
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 05:30 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
904
Videos
59
Links
406

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

Reaction mix

140 reactions across 9 posts, in 26 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4935.0%
3424.3%
👍128.57%
👏107.14%
👌42.86%
🤩42.86%
32.14%
🙏32.14%
🌚21.43%
💋21.43%
💘21.43%
10.714%
❤‍🔥10.714%
🎅10.714%
👨‍💻10.714%
👾10.714%
💊10.714%
🗿10.714%
😇10.714%
😍10.714%
6 further kinds64.29%

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 140reactions 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 24 July 2026 to 11 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

11 Aug 2026, 09:04 UTC≈1,050 views9 reactionsread 13 August 2026
Photo

💹 Миллион устройств, один канал и никаких лишних TLS-рукопожатий Чтобы убрать обязательный хаб из умного дома, нужно столкнуться с серьёзными вопросами инженерии: устройства должны без посредников входить в экосистему, держать долгоживущее облачное соединение и обновляться. А мощным бэкендом здесь не поможешь, ведь все ограничения железа, памяти и CPU — на клиентской стороне. Меня зовут Вадим Иванов, я старший разр

4🔥3👍2

7 Aug 2026, 14:00 UTC≈1,740 views3 reactionsread 13 August 2026
Photo

🕵🏻‍♂️ Телеметрия обучений LLM: как мы контролируем наши GPU Привет, меня зовут Иван Мякиньков, я разработчик бригады инфраструктуры «Генезиса» в Поисковых сервисах и ИИ. Каждый день в Яндексе происходит более 5000 обучений LLM. Из них около 1500 по разным причинам заканчиваются неудачей. Раньше диагностика выглядела так: обучение упало → скачиваем логи → ищем в простыне текста ошибку → пытаемся понять причину. На э

1👏1🔥1

5 Aug 2026, 15:00 UTC≈1,820 views13 reactionsread 13 August 2026
Photo

🟢 Как мы пустили сторонний код в продукт с 600 000 пользователей Меня зовут Женя Успенский, я руковожу разработкой фронтенда в Яндекс Трекере и отвечаю за архитектуру платформы плагинов. Это отдельный механизм, который позволяет без навыков кодинга расширять Трекер собственными модулями без модификации его ядра. Хочу рассказать, как мы архитектурно разделили и встроили сторонние расширения в продукт с устоявшейся к

👏64🔥3

3 Aug 2026, 14:03 UTC≈2,030 views16 reactionsread 13 August 2026
Photo

🍏 Тысяча «яблок» для песочниц: как и зачем мы обновили стойки в дата-центрах Привет! Меня зовут Владимир Аксёнов, я руковожу группой IT‑поддержки дата-центра в Yandex Infrastructure. Более 10 лет назад, когда у наших инженеров появилась потребность писать софт под iOS, мы начали ставить для этих задач первые Apple Mac mini c габаритами 197×197×36 мм: серверных версий не было. Теоретически можно было бы установить и

🔥9👏3👍2😇1😴1

1 Aug 2026, 08:04 UTC≈2,440 views10 reactionsread 13 August 2026
Photo

🚀 Back to Back начнётся через час! Уже сегодня состоится новая конференция Яндекса для бэкенд-инженеров, SRE и техлидов одновременно в Москве, Белграде и Ереване. 📺 Выбирайте город и подключайтесь к трансляции: 🗺 Москва, трек C++ Zero Cost: 🟢 Ютуб 🟢 VK Видео 🟢 Сайт 🗺 Москва, трек Architecture & Performance: 🟢 Ютуб 🟢 VK Видео 🟢 Сайт 🗺 Белград, трек C++ Zero Cost: 🟢 Ютуб 🟢 VK Видео 🟢 Сайт 🗺 Ереван, трек Archit

5👍2🔥2🤷‍♂1

30 Jul 2026, 15:04 UTC≈2,570 views30 reactionsread 13 August 2026
Photo

🟢 Старый сервис в новой реальности Многие из вас видели mirror.yandex.ru, возможно, качали ISO-образы дистрибутивов. Внешне сервис за последние 19 лет никак не трансформировался: всё те же файлы по HTTP и rsync. Но под капотом произошли некоторые изменения 👀 👨‍💻 Меня зовут Борис Литвиненко, я ведущий разработчик группы разработки сетевой инфраструктуры и мониторинга в Yandex Infrastructure. Хочу рассказать, с каким

🔥15👌43🌚211👾1💊1

28 Jul 2026, 09:01 UTC≈3,950 views6 reactionsread 13 August 2026
Photo

🛎 Back to Back пройдёт уже в эту субботу! 1 августа состоится конференция для бэкенд-инженеров, архитекторов, SRE и техлидов, поэтому не упустите возможность зарегистрироваться 🚀 ➖ Напоминаем главное: Back to Back пройдёт одновременно в Москве, Белграде и Ереване, а также онлайн для всех, кто далеко. 📍 В Москве мы соберём сразу два трека: 🟢 C++ Zero Cost — про производительность, системную разработку и инженерные

3🔥2👍1

27 Jul 2026, 14:22 UTC≈2,530 views29 reactionsread 13 August 2026
Photo

🤔 Как понять, куда уходит память Привет, меня зовут Сергей Кривохатский, я пишу прикладной код на C/C++ для умных устройств с Алисой. Сегодня я хочу рассказать, как мы работаем с памятью. Для нас это важная тема, потому что типичная умная колонка с Алисой имеет скромное железо и совсем немного оперативной памяти. Например, у наших младших моделей всего 256 Мб ОЗУ на всё устройство. За каждый мегабайт идёт настоящая

10🔥6👍5🙏3💘2❤‍🔥1💋1🗿1

24 Jul 2026, 14:30 UTC≈2,490 views24 reactionsread 7 August 2026
Photo

🤖 Observability на стероидах Когда у вас 3 миллиарда семплов в секунду, 60 гигабайт логов и 44 миллиона спанов, вы уже не просто настраиваете мониторинг — вы пишете его с нуля. Так внутри Яндекса вырос Monium — система наблюдаемости, которая теперь доступна как отдельный продукт. 🎧 В новом выпуске подкаста linkmeup sysadmins Владимир Гордийчук, CTO Yandex Monium, рассказал, зачем его команда написала свой мониторин

🔥86🤩4🎅1👨‍💻1💋1🤯1🥴1

Showing the 9 most recent of 9 posts we hold for @yandexforbackend. 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 — 247,307 of 1,345,403entries 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 4 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.

Young&&Yandex
@Young_and_Yandex · 110,414
Telegram ranks this channel #14 of 92 here — alongside 91 others — read 14 August 2026
Т-Образование
@tbank_education · 111,441
Telegram ranks this channel #71 of 91 here — alongside 90 others — read 14 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Yandex for Backend” (@yandexforbackend), 9,975 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/yandexforbackend.

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.