Telegram RegisterThe public register of Telegram
Telegram profile photo for balun.courses

Channel

balun.courses

@balun_courses

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,009subscribers

+8 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002070631849
TypeChannel
Username@balun_courses
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/balun_courses

Growth

3,0013,0093,0057 August 2026 — 3,001 subscribers7 August 2026 — 3,001 subscribers8 August 2026 — 3,002 subscribers11 August 2026 — 3,009 subscribers7 August 202611 August 2026
4 measurements spanning 3 days, net +8. 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 3,000–3,010 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:453,009+7
8 Aug 2026, 09:003,002+1
7 Aug 2026, 18:033,001no change
7 Aug 2026, 17:523,001first reading

Engagement

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

ERR · 30 days
38.0%
avg views ÷ 3,009 subscribers
Avg views / post
1,140
6 posts measured
Reaction rate
0.553%
reactions ÷ views · ER floor
Posts in window
6
of 20 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 7 August 2026
Posts held20 (24 June 20267 August 2026)
Views total6,869
Reactions total38
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:12 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.

Reaction mix

196 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8040.8%
👍6332.1%
🔥5327.0%

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

Measured over the 20 most recent posts we hold, published 24 June 2026 to 7 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

7 Aug 2026, 13:08 UTC437 views8 reactionsread 8 August 2026
Forwarded from @balun_courses_ai

Posted without readable text

6👍2

5 Aug 2026, 06:43 UTC742 views8 reactionsread 8 August 2026
Photo

Август будет насыщенным. Если давно собирались присоединиться к нашим активностям – вот, что мы что запланировали➡️ ◻️3 августа – старт курса «Concurrency в Go» Курс для тех, кто хочет разобраться, как действительно работает конкурентность в Go: без заучивания примитивов, а через понимание внутренних механизмов и большое количество практики. ◻️ 18 августа – бесплатная консультация для Junior и стажёров Поговорим

🔥61👍1

3 Aug 2026, 13:32 UTC≈1,010 views3 reactionsread 8 August 2026
Photo

⚡️Стартовал курс Concurrency в Go Это уже 10 (юбилейный) поток для наших студентов! На курсе изучаем: • внутреннее устройство горутин и планировщика Go; • подводные камни контекстов и барьеров памяти; • внутреннее устройство каналов, паттерны их использования и реализация; • паттерны конкуретных вычислений и live coding worker pool, синхронизатора кэша, scheduler и batcher; • примитивы синхронизации и как их реали

3

30 Jul 2026, 14:06 UTC≈1,530 views6 reactionsread 8 August 2026

⚡️ElasticSearch для разработчиков Привет, на связи Balun.Courses! Готовим углубленный курс для разработчиков по использованию ElasticSearch. И чтобы не «тыкать пальцем в небо», хотим спросить у вас напрямую: 1) Насколько этот инструмент для вас понятен? 2) Где вы вообще используете эластик? 3) Какие у вас возникают сложности? И есть ли они вообще? Подготовили небольшой опрос, который займет не больше 10 минут. 🎁

2👍2🔥2

28 Jul 2026, 09:13 UTC≈1,480 views2 reactionsread 8 August 2026
Photo

Расследование production-инцидентов с помощью OpenTelemetry + AI • 29 июля, CР • 19:00 по мск Открытый урок для разработчиков и DevOps. Покажем observability-стек и продвинутые возможности Otel, которые помогают искать и чинить инциденты с помощью AI-агента Что будет на уроке: 1️⃣База по OpenTelemetry для понимания контекста 2️⃣Продвинутые инструменты Otel, которые передают агенту связный контекст инцидента вмес

2

22 Jul 2026, 10:05 UTC≈1,670 views11 reactionsread 8 August 2026
Photo

⚡Напоминаем про июльские бесплатные консультации для Go-разработчиков В этом месяце проведём два Zoom-разбора под разные уровни подготовки: 1️⃣23 июля, чт, 19:00 МСК – консультация для начинающих (стажёры, Junior) Разберём вопросы по Go, рабочие задачи, подготовку к собеседованиям и карьерное развитие 2️⃣28 июля, вт, 19:00 МСК – консультация для опытных разработчиков (Middle, Senior, TeamLead) Обсудим архитектур

5👍3🔥3

12 Jul 2026, 10:34 UTC≈1,630 views13 reactionsread 8 August 2026
Photo

Расследование production-инцидентов с помощью OpenTelemetry + AI • 29 июля, CР • 19:00 по мск Открытый урок для разработчиков и DevOps. Покажем observability-стек и продвинутые возможности Otel, которые помогают искать и чинить инциденты с помощью AI-агента Что будет на уроке: 1️⃣База по OpenTelemetry для понимания контекста 2️⃣Продвинутые инструменты Otel, которые передают агенту связный контекст инцидента вмес

5👍4🔥4

9 Jul 2026, 14:32 UTC≈1,690 views12 reactionsread 8 August 2026
Photo

TeamLead, ты делаешь эти вещи неправильно • 22 июля, СР • 19:00 по мск Открытый урок по 10 популярным ошибкам, которые ты не замечаешь, и которые регулярно выходят «боком» команде, бизнесу и сомнениям к твоей работе ⁉️Для кого: • Опытные лиды. Узнаешь, что нужно перестроить, чтобы твои решения приносили больше пользы • Начинающие лиды. На старте работы поймешь, как лучше НЕ делать и не «наломать дров» Что будет

5🔥4👍3

9 Jul 2026, 11:03 UTC≈1,620 views17 reactionsread 8 August 2026

Ищем кандидатов для съёмок mock-собеседований: PostgreSQL, Elasticsearch, Team Lead, DevOps, SRE Всем привет 🙌🏻 Хотим записать для YouTube-канала школы несколько новых mock-собеседований и ищем интересных кандидатов. В ближайшее время планируем провести mock-собеседования с вопросами по PostgreSQL и Elasticsearch, а также отдельные собеседования на позиции Team Lead, DevOps и SRE. Если хотите поучаствовать, напиши

🔥76👍4

6 Jul 2026, 15:16 UTC≈1,840 views21 reactionsread 8 August 2026
Photo

PostgreSQL и тормозящие запросы: что делать, когда индексы есть, а толку – нет? • 20 июля, ПН • 19:00 по мск Открытый урок по PgSQL для разработчиков: частые ошибки с индексами, из-за которых тормозят запросы, и как это пофиксить Что будет на уроке: 1️⃣Почему PostgreSQL выбирает Seq Scan даже при наличии индекса, и когда это нормально 2️⃣Как читать EXPLAIN ANALYZE и за минуты находить причину медленного запроса

8👍7🔥6

3 Jul 2026, 10:44 UTC≈1,770 views8 reactionsread 8 August 2026

⚡️Новые тематические каналы школы Чтобы вам было проще следить только за теми темами, которые действительно интересны, мы разделили контент на отдельные каналы! Уже на этой неделе начнем публиковать первые материалы. Подписывайтесь на интересующие направления❤️ • Go для опытных разработчиков – Глубокий Go, Concurrency, Go-собеседования, практика Для тех, кто уже работает с Go и хочет глубже разобраться в языке, п

4👍2🔥2

30 Jun 2026, 10:58 UTC≈1,600 views9 reactionsread 8 August 2026
Photo

⚡️ Завтра в 10:00 летний code-календарь завершится Финальный день летнего code-календаря решили сделать особенным Мы открыли все лекции сразу – ровно на сутки. Если не успели посмотреть какой-то эфир или присоединились только сейчас, у вас есть возможность наверстать все материалы до завтра, 10:00. Но вместе с этим завтра завершатся и все специальные предложения. Не будет дополнительных скидок, закрытых комплект

3👍3🔥3

Showing the 12 most recent of 20 posts we hold for @balun_courses. 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 — 6,166 of 1,480,944entries 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.

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.

Mentions

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

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.

“balun.courses” (@balun_courses), 3,009 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/balun_courses.

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.