Telegram RegisterThe public register of Telegram
Telegram profile photo for GDG Minsk News

Channel

GDG Minsk News

@gdgminsk_news

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

137subscribers

-5 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001334355857
TypeChannel
Username@gdgminsk_news
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/gdgminsk_news

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 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

137142139.58 August 2026 — 142 subscribers8 August 2026 — 142 subscribers15 August 2026 — 140 subscribers22 August 2026 — 139 subscribers28 August 2026 — 138 subscribers5 September 2026 — 137 subscribers8 August 20265 September 2026
6 measurements spanning 28 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 136–143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 07:37137-1
28 Aug 2026, 23:04138-1
22 Aug 2026, 01:37139-1
15 Aug 2026, 19:16140-2
8 Aug 2026, 22:01142no change
8 Aug 2026, 02:16142first reading

Engagement

20 posts held, back to 15 February 2024 — 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 December 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

51 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1937.3%
👍1835.3%
🔥1121.6%
❤‍🔥11.96%
🎄11.96%
🤔11.96%

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 15 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 51 reactions 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 15 February 2024 to 31 December 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
215
over 1 measured post
Median views · rest
178
over 19 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.

Measured over the 20 most recent posts we hold, published 15 February 2024 to 31 December 2024. 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

31 Dec 2024, 15:01 UTC158 views7 reactionsread 8 August 2026
Photo

Друзья, с наступающим Новым годом! 🎄 Спасибо, что посещали мои встречи и были со мной в этом году. Хочу пожелать вам вдохновения в работе, уверенности в своих силах и много энергии и здоровья, чтобы достичь всех своих целей. Пусть всё задуманное получится, а работа приносит не только результат, но и удовольствие. Не забывайте конечно же и отдыхать. Тепла, добра и новых впечатлений в новом году 🥂🎉

❤6🎄1

16 Dec 2024, 10:01 UTC162 views3 reactionsread 8 August 2026
Photo

Итоги 2024 для мира IT | Онлайн-стрим Обсудим, что принёс 2024 год в айтишку и каким индустрия его запомнит. 📅 20 декабря, 17:00 CET 🗨 Язык – RU В агенде • ИИ в 2024: RAG и интеграция LLM в продукты • Кибербезопасность: уроки года и новые угрозы • Облака и датацентры: битва за производительность и стоимость • Стартапы, инвестиции и рынок труда Также попробуем предугадать, чего ждать от IT в 2025 🔮 👾 Этот стрим м…

👍3

31 Oct 2024, 07:02 UTC172 viewsread 8 August 2026
Photo

Знакомые из соседнего сообщества приглашают на большой Cloud Security митап, который пройдёт онлайн Эксперты из Orca Security представят реальные кейсы проблем в Azure, GCP и AWS и поделятся эффективными стратегиями защиты облачной инфраструктуры. Также обсудим, как неправильное понимание модели shared responsibility может стать причиной уязвимостей. 🗓 8 ноября, 18:00 📍Варшава, Google for Startups Campus В агенде:…

5 Sept 2024, 08:04 UTC190 views2 reactionsread 8 August 2026
Photo

☄️ В Минске стартует турнир по спортивному программированию Код Т1 🌟 Продемонстрируй знание алгоритмов и выиграй крутые призы от ИТ-холдинга Т1: игровой ноутбук HUAWEI MateBook D и Apple iPhone 15. 🎉 1️⃣ Предварительный онлайн-этап: 10 сентября с 10:00 до 23:59 (нужно решить 1 отборочную задачу в указанный срок) 2️⃣ Офлайн-этап: 13 сентября в 09:00. Место – отель Minsk Marriott 🖥 Код Т1 – это 3 часа решения алгори…

🔥2

9 Jul 2024, 10:01 UTC174 views6 reactionsread 8 August 2026
Photo

Coffee&Code: Kotlin Coroutines 🤗 Наконец-то разобрался с выступлением, где рассказал руководителям, что такое мобильная разработка, какие базовые вещи должен понимать руководитель, с какими проблемами можно столкнуться и т.д.Теперь возвращаюсь к продолжению изучения корутин 🔥 💡 Все детали встречи вы найдете ниже В прошлый раз мы прошлись по билдерам, корутин контексту. В следующий раз мы изучим: 🔸 Без пару заданий…

👍4❤2

29 May 2024, 07:08 UTC178 views3 reactionsread 8 August 2026
Photo

Coffee&Code: Kotlin Coroutines 🤗 В прошлый четверг не успели все обсудить, поэтому продолжим обсуждать в эту пятницу. 💡 Все детали встречи вы найдете ниже Агенда: 🔸 Вспомним прошлые наши знания и порешаем еще пару задачек 🔸 Добьем все что касается Job и разберемся что за паттерн такой Key в CoroutineContext и как он работает Основная цель встреч – это получить и закрепить знания, а также неформальное общение. Де…

👍2🔥1

21 May 2024, 14:09 UTC182 views1 reactionsread 8 August 2026
Photo

Coffee&Code: Kotlin Coroutines 🤗 ‼️ В рамках опроса побеждает четверг в 19:00 В прошлый раз мы начали с небольшой истории и успели затронуть: 📌 Что такое suspend функция и чем она отличается от стандартных функций 📌 Рассмотрели основные корутин билдеры 📌 Закрепили знания через практику Настало время продолжить изучать корутины на новой встрече. 💡 Все детали встречи вы найдете ниже Агенда: 🔸 Coroutine Context 🔸 …

❤1

20 May 2024, 14:24 UTC135 viewsread 8 August 2026
Poll

На этой неделе планирую провести вторую встречу по совместному изучению корутин. Как всегда начнем с повторения предыдущей сессии и потом пойдем по новым темам. Хочу понять какое время лучше всего подойдет для встречи:

  1. 19:00, 23.05 на Победителей 11067%
  2. 11:00, 26.05 в кафе Мануфактура67%
  3. 11:00, 26.05 в кафе Мануфактура33%

The shares total 167%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

13 May 2024, 08:00 UTC183 viewsread 8 August 2026
Photo

Друзья по технологиям из Mobile Broadcast приглашают на свой первый оффлайн митап в Минске. 👉Когда: 16.05.2024 (чт) 👉Где: Пространство "Innodom" (ул. Беломорская, 17) Программа митапа: 19:00 - Сбор гостей 19:15 - Доклад "Современная навигация в Jetpack Compose". Спикер - Егор Чепрасов, Android/Kotlin Multiplatform разработчик, IBA IT Park 20:00 - Кофе-брейк 20:15 - Доклад "Как безопасно обновлять состояние в Kotli…

29 Apr 2024, 13:01 UTC193 views6 reactionsread 8 August 2026
Photo

Встреча Coffe & Code: Kotlin Coroutines Вчера прошла очередная встреча в формате Coffe & Code, на которой мы начали изучать или повторять основы Kotlin Coroutines. Материалы, которые использовались на встрече: 🔸 Презентация 🔸 Код Следующая встреча предварительно планируется на 16 мая на вечер. Анонсы и обновления будут заранее 🤗 Всем хорошего начала недели и до новых встреч!

🔥5🤔1

23 Apr 2024, 10:01 UTC174 views4 reactionsread 8 August 2026
Photo

Давно не виделись, поэтому собираемся на новую встречу Coffee&Code 🤗 В прошлые разы мы успешно прошлись по теме многопоточности. Пришло время пойти дальше и заглянуть в основы Kotlin Coroutines. Понятие корутин в IT мире уже давно известно. Во многих языках присутствует такая механика и Kotlin не остался в сторонке. За несколько встреч мы рассмотрим основы, попрактикуемся и точно узнаем много нового. 💡 Все детали в…

👍4

17 Apr 2024, 06:58 UTC159 viewsread 8 August 2026
Poll

Лучшее время для встречи

  1. 10:00, вскр11%
  2. 11:00, вскр11%
  3. 12:00, вскр56%
  4. 13:00, вскр44%
  5. 14:00, вскр22%
  6. 15:00, вскр11%

The shares total 155%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 May 2024, 14:24 UTCFinal Results3 voters

На этой неделе планирую провести вторую встречу по совместному изучению корутин. Как всегда начнем с повторения предыдущей сессии и потом пойдем по новым темам. Хочу понять какое время лучше всего подойдет для встречи:

  1. 19:00, 23.05 на Победителей 11067%
  2. 11:00, 26.05 в кафе Мануфактура67%
  3. 11:00, 26.05 в кафе Мануфактура33%

The shares total 167%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

17 Apr 2024, 06:58 UTCFinal Results9 voters

Лучшее время для встречи

  1. 10:00, вскр11%
  2. 11:00, вскр11%
  3. 12:00, вскр56%
  4. 13:00, вскр44%
  5. 14:00, вскр22%
  6. 15:00, вскр11%

The shares total 155%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 15 February 2024 to 31 December 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“GDG Minsk News” (@gdgminsk_news), 137 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/gdgminsk_news.

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.