Telegram RegisterThe public register of Telegram
Telegram profile photo for Антон Скутин | От BRM к SRE

Channel

Антон Скутин | От BRM к SRE

@BRM2SRE

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

211subscribers

-12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002185687187
TypeChannel
Username@BRM2SRE
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/BRM2SRE

Growth

2112232176 August 2026 — 223 subscribers7 August 2026 — 223 subscribers7 August 2026 — 222 subscribers15 August 2026 — 219 subscribers22 August 2026 — 218 subscribers30 August 2026 — 215 subscribers8 September 2026 — 214 subscribers15 September 2026 — 211 subscribers6 August 202615 September 2026
8 measurements spanning 40 days, net -12. 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 209–225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 09:16211-3
8 Sept 2026, 13:59214-1
30 Aug 2026, 17:55215-3
22 Aug 2026, 17:05218-1
15 Aug 2026, 10:18219-3
7 Aug 2026, 04:01222-1
7 Aug 2026, 03:03223no change
6 Aug 2026, 16:39223first reading

Engagement

20 posts held, back to 10 June 2025the 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 3 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,930 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 49.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥94649.0%
👍72137.4%
1407.25%
💯593.06%
🍾301.55%
🤣130.674%
🤝60.311%
😁50.259%
🥰40.207%
custom 518848127996371578120.104%
👀20.104%
👏20.104%

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 is Telegram’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 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 1,930 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 10 June 2025 to 3 April 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

3 Apr 2026, 12:28 UTC341 views43 reactionsread 7 August 2026
Video message

Video message, posted without a caption

👍23🔥191

1 Apr 2026, 14:35 UTC384 views34 reactionsread 7 August 2026
Photo

Снова в путь 🚄 В этот раз в столицу на DevOpsConf, буду рассказывать про то как мы прошли путь от фиксации инцидентов в Excel до построения системы метрик, объединившей бизнес и ИТ вокруг единых приоритетов 🧐 Кто тоже будет там - буду рад увидеться 😍

👍32🔥2

1 Apr 2026, 10:07 UTC384 views32 reactionsread 7 August 2026
Video message

Video message, posted without a caption

🍾20🤣12

1 Apr 2026, 10:00 UTC389 views78 reactionsread 7 August 2026
Photo

Друзья, привет. Обещал новость - рассказываю 😋 У меня новый отдел и я теперь HEAD 😎 В 40 лет всё только начинается Впереди очень много интересного 👷‍♂️

👍41🔥27🍾10

26 Mar 2026, 11:41 UTC405 views42 reactionsread 7 August 2026
Video message

Video message, posted without a caption

32🔥6🥰4

26 Mar 2026, 11:19 UTC395 views51 reactionsread 7 August 2026

Привет, друзья! 😎 На связи Антон Скутин из Петрович-Теха. В 40 лет перезагрузил карьеру: от BRM к SRE. 🔄 От Business Relationship Manager к head of Monitoring & Observability. 🚨 От переговоров с бизнесом к алертам и SLO. 📊 От встреч с заказчиками к дашбордам Grafana. Добро пожаловать в новую эру канала! Делюсь кейсами ITIL и observability. Подписывайся! ⚡️ #BRM2SRE

🔥47👍4

1 Sept 2025, 09:10 UTC≈1,350 views156 reactionsread 7 August 2026

Почему BRM должен быть "главным скептиком" в компании (и как это помогает) 🤔🔍 Иногда роль делает нас "противными критиками". Где просели реальные показатели, хотя метрики остаются в зеленой зоне? Почему злится заказчик? Действительно ли наша модель поддержки справляется с задачами бизнеса? К кому эти вопросы? Правильно, к BRM. И ответы на них могут быть неприятны. Когда говоришь правду, особенно если она неудобна,

🔥76👍6416

27 Aug 2025, 10:28 UTC≈1,160 views145 reactionsread 7 August 2026

Сложна жизнь BRM: почему я молчу, хотя есть что рассказать 😅🤐 Давно не писал, и вот почему: многое хочу рассказать, но… не могу. Да, такая вот сложная судьба у BRM Вокруг моей работы крутится столько всего интересного: новые проекты, активности, кейсы, которые хочется разобрать, обсудить, поделиться опытом. Но есть одна проблема — NDA. И даже если что-то пока не под NDA, с точки зрения стратегии и тактики компании

👍80🔥61🤝4

4 Aug 2025, 09:27 UTC827 views93 reactionsread 7 August 2026
Photo

Что должно быть в Welcome Box для BRM? 🤔📦 (Спойлер: не только мерч) У нас в компании недавно обновили Welcome Box для новичков. Теперь там куча классных штук, которые сразу настраивают на рабочий лад. Но когда я увидел этот бокс, задумался: а что должно быть в Welcome Box для BRM? Вот мой список того, что точно пригодится каждому BRM в первые дни работы 😅 ☀️ Бизнес-переводчик" 📚🌐 Первое, что нужно новому BRM — сл

🔥55👍37🤣1

28 Jul 2025, 10:54 UTC692 views60 reactionsread 7 August 2026
Photo

Жара в Питере сейчас, а когда термометр BRM зашкаливает? 🌡💼 Когда все говорят про жару в Питере, я думаю о своей "температурной карте" на работе. У BRM есть свои "пиковые сезоны", когда задачи накаляются до предела. Давайте разберу, какие периоды заставляют меня работать на максимуме и почему это действительно "самое-самое" 1️⃣ Осенний жар: согласование бюджета 💸🔥 Сентябрь-ноябрь — время, когда все хотят всё сразу

🔥37👍22🤝1

8 Jul 2025, 08:57 UTC856 views28 reactionsread 7 August 2026

Ушёл в отпуск. И да, это тоже часть работы 😌🌲 Друзья, я временно вне зоны доступа. Уехал в лес, закрылся в домике, и тут нет ни Wi-Fi, ни котов, которые случайно вызывают BRM 😹 Даже тот, кто любит общаться, иногда должен дать мозгу перезагрузку. Так что если вы меня искали — не ищите. Я на связи после отпуска 🚶‍♂️✨

🔥22👍3😁3

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

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

“Антон Скутин | От BRM к SRE” (@BRM2SRE), 211 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/BRM2SRE.

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.