3 measurements spanning 9 days, net +5. 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 122–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 20:34
128
+5
9 Aug 2026, 03:03
123
no change
6 Aug 2026, 04:05
123
first reading
Engagement
11 posts held, back to 23 June 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
141.9%
avg views ÷ 128 subscribers
Avg views / post
182
3 posts measured
Reaction rate
7.34%
reactions ÷ views · ER floor
Posts in window
3
of 11 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
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
11 (23 June 2026 – 5 August 2026)
Views total
545
Reactions total
40
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Aug 2026, 03:03 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
Video runtime
9s
Average length
9s
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
128 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 32.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
42
32.8%
🔥
19
14.8%
❤
16
12.5%
😁
11
8.59%
💯
8
6.25%
✍
7
5.47%
🏆
7
5.47%
custom 5332780103661282843
5
3.91%
👏
5
3.91%
🎉
3
2.34%
👻
3
2.34%
🤔
1
0.781%
🤣
1
0.781%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 11 of the 11 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 128reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 23 June 2026 to 5 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.
💠 ИИ есть у каждого сотрудника. Почему результатов нет у компании?
13 августа | 11:00 (мск)
Сегодня сотрудники почти всех компаний уже активно используют ИИ. Многие создают собственных ИИ-агентов. Однако разработать агента — самая простая часть задачи. Гораздо сложнее обеспечить безопасную работу с корпоративными данными, встроить его в процессы компании и сделать так, чтобы результат был воспроизводимым и масштабир…
Врываемся в новую неделю и в новый чат, как герои «Теории большого взрыва»
☕️ — если после общения с ИИ вам тоже нужны горячий напиток и психологическая поддержка
Берегись бэклога 💫
📄 Изучили для вас новую статью McKinsey об экономике корпоративных ИИ-агентов.
Что интересного:
👉 Стоимость обработки запросов моделью уровня GPT-3.5 снизилась с $20 до $0,07 за 1 млн токенов к концу 2024 года. Но за 12 месяцев, к концу 2025-го, расходы компаний на LLM утроились. 93% участников опроса McKinsey сообщили, что вышли за рамки ИИ-бюджета.
👉 Агентные сценарии расходуют в десятки раз больше ресурсов, чем…
#ЭТО_БАЗА: обзор лучших ИИ-кейсов рынка. Выпуск 6 ⚡️
Сегодня расскажем, как Morgan Stanley в 2 раза сократила время сложнейшей финансовой операции и получила экономию почти 1500 часов в неделю.
Самое интересное: результат получили не за счёт полностью автономных агентов. Наоборот, человек остался в центре процесса, а ИИ взял на себя только рутину. Кажется, такой подход уже становится стандартом для многих enterpris…
Пока закон об ИИ еще обсуждают, появляются новые документы, которые определят правила работы рынка.
На этот раз правительство подготовило проект постановления, по которому Минцифры станет главным ведомством по вопросам ИИ. Министерство получит около 20 новых полномочий: готовить профильные законы, определять меры поддержки разработчиков, регулировать доступ к государственным данным для обучения моделей и развивать И…
📰📰📰 Выпустили платформу KORUS AI для кратного роста личной и командной эффективности
Решение помогает перейти от разрозненного использования ИИ-сервисов к единой корпоративной среде. С помощью платформы можно быстро запускать ИИ-сценарии, сохранять контроль над данными и масштабировать успешные практики на разные подразделения.
В чем проблема сегодня
Компании тестируют ИИ-инструменты и запускают пилоты, но большинс…
ГК «КОРУС Консалтинг» — в лидерах «Рейтинга Рунета 2026»!
Среди 1094 участников команда «КОРУС Консалтинг» заняла сразу несколько первых строчек в ключевых направлениях:
⚡️ 1 место — «ПО десктопное/серверное/SaaS», сегмент «Интеграторы»;
⚡️ 1 место — «1С», сегмент «Корпоративное ПО»;
⚡️ 1 место — отраслевые рейтинги «Промышленность» и «Строительство и ремонт»;
⚡️ 2 место — «Подрядчики крупного бизнеса»;
⚡️ 3 место …
OpenAI совместно с американской компанией Trail of Bits запустили инициативу «Patch the Planet». Теперь ИИ-модель GPT-5.5-Cyber Pro помогает искать уязвимости в проектах с открытым кодом и предлагает варианты их исправления. За первую неделю работы она проверила 19 проектов и нашла 51 потенциальную уязвимость.
Спросили Елену Никитину, руководителя направления заказной разработки ГК «КОРУС Консалтинг», насколько поле…
Пятничная перекличка. Коллега из команды прислал настолько жизненный мем, что мы не могли не поделиться
👻 — если тоже успели поговорить с ИИ сегодня
Берегись бэклога 💫
📚 ИИ-дайджест: что почитать и посмотреть
За последние недели вышло много полезных материалов про ИИ, рынок и практику внедрения. Собрали несколько публикаций, которые будут интересны руководителям и командам, работающим с ИИ.
⚡ TAdviser: «Тенденции развития технологий искусственного интеллекта в России»
Большой обзор рынка ИИ: драйверы роста, ограничения и сценарии применения. Хороший материал, чтобы быстро понять,…
Как российскому бизнесу использовать ИИ и не нарушить закон?
Пока однозначного ответа нет, так как законодательство в сфере ИИ только формируется. Но на этой неделе рынок получил важный сигнал. 22 июня правительство России рассмотрело новую версию законопроекта об ИИ, которую существенно переработали после критики со стороны крупного бизнеса.
Разобрали в карточках
🟥как изменились акценты,
🟥что учесть компаниям, кот…
👍7✍5💯3
Showing the 11 most recent of 11 posts we hold for @backlogahead. 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 — 317,776 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 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.
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.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Берегись бэклога” (@backlogahead), 128 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/backlogahead.
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.