Telegram RegisterThe public register of Telegram
Telegram profile photo for GetAnalyst - Навыки • Системный анализ • Бизнес-анализ

Channel

GetAnalyst - Навыки • Системный анализ • Бизнес-анализ

@getanalysts

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

22,369subscribers

+128 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001576386485
TypeChannel
Username@getanalysts
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/getanalysts

Growth

22,24122,36922,3057 August 2026 — 22,241 subscribers8 August 2026 — 22,247 subscribers9 August 2026 — 22,251 subscribers10 August 2026 — 22,250 subscribers11 August 2026 — 22,256 subscribers12 August 2026 — 22,263 subscribers13 August 2026 — 22,272 subscribers15 August 2026 — 22,281 subscribers16 August 2026 — 22,290 subscribers17 August 2026 — 22,292 subscribers18 August 2026 — 22,310 subscribers19 August 2026 — 22,323 subscribers20 August 2026 — 22,327 subscribers22 August 2026 — 22,330 subscribers23 August 2026 — 22,325 subscribers25 August 2026 — 22,335 subscribers26 August 2026 — 22,341 subscribers27 August 2026 — 22,343 subscribers28 August 2026 — 22,341 subscribers29 August 2026 — 22,342 subscribers30 August 2026 — 22,349 subscribers31 August 2026 — 22,353 subscribers1 September 2026 — 22,354 subscribers2 September 2026 — 22,353 subscribers3 September 2026 — 22,364 subscribers5 September 2026 — 22,369 subscribers7 August 20265 September 2026
26 measurements spanning 29 days, net +128. 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 22,222–22,388 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
5 Sept 2026, 14:2122,369+5
3 Sept 2026, 18:2022,364+11
2 Sept 2026, 07:1822,353-1
1 Sept 2026, 06:4922,354+1
31 Aug 2026, 09:1322,353+4
30 Aug 2026, 05:5422,349+7
29 Aug 2026, 09:0622,342+1
28 Aug 2026, 06:4222,341-2
27 Aug 2026, 03:0822,343+2
26 Aug 2026, 00:3222,341+6
25 Aug 2026, 04:0322,335+10
23 Aug 2026, 21:4822,325-5
22 Aug 2026, 06:0622,330+3
20 Aug 2026, 19:4722,327+4
19 Aug 2026, 20:1622,323+13
18 Aug 2026, 19:4722,310+18
17 Aug 2026, 18:0922,292+2
16 Aug 2026, 17:3322,290+9
15 Aug 2026, 01:0322,281+9
13 Aug 2026, 14:1722,272first reading

Engagement

46 posts held, back to 26 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 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.8%
avg views ÷ 22,369 subscribers
Avg views / post
2,650
31 posts measured
Reaction rate
1.08%
reactions ÷ views · ER floor
Posts in window
31
of 46 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. It is computed over the 30 of 31 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held46 (26 July 20263 September 2026)
Views total82,056
Reactions total877
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 12:16 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
15s
Average length
15s

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

1,529 reactions across 45 posts, in 15 distinct kinds. The most used accounts for 47.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
71947.0%
🔥38525.2%
❤‍🔥1117.26%
👍875.69%
😁664.32%
🤣664.32%
👎261.70%
💯231.50%
🦄161.05%
👌130.85%
🥰60.392%
👀40.262%
30.196%
😱30.196%
🤔10.065%

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

Measured over the 46 most recent posts we hold, published 26 July 2026 to 3 September 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 Sept 2026, 10:57 UTC586 viewsread 3 September 2026
Photo

💎 Архитектура для СА: открыта предзапись, старт 15 сентября 💎 Вы уже уверенный Middle, Middle+ или Senior. Понимаете процессы, работаете с интеграциями и API. Микросервисы в теории понятны. Знаете, зачем нужна Kafka. Но как спроектировать реальный асинхронный процесс, в котором участвуют несколько сервисов? 🔴 Почему, например, остановка одного сервиса всё ещё блокирует процесс, несмотря на Kafka? Потому что асинх

2 Sept 2026, 11:56 UTC≈1,660 views9 reactionsread 3 September 2026
Photo

🧩 7 архитектурных решений, которые аналитик принимает раньше архитектора «Пользователь заказал товар, курьер загрузил посылку в постамат, пользователь её забрал». Один процесс. Но сколько вопросов появляется, когда начинаешь его проектировать: ▫️ какие микросервисы нужны ▫️ где хранить данные об отправлениях, ячейках и оплатах ▫️ какие API использовать ▫️ где ждать ответ, а где передавать событие через брокер ▫️ к

🔥8❤‍🔥1

2 Sept 2026, 06:04 UTC≈1,900 views30 reactionsread 3 September 2026
Photo

🔵🔥 Нотация C4 для архитектуры: теория, 7 примеров и практический видеоурок 🔥🔵 Как показать архитектуру системы так, чтобы её поняли и бизнес, и разработчики? Нотация моделирования архитектуры C4 поможет. Собрала в одном посте все материалы по C4: от теории до готовых схем с конкретными примерами 👇👇👇 🎬 Практический видеоурок: C4 за 90 минут Разбираем уровни Context, Container и Component и наглядно показываем, к

15👍9🔥6

1 Sept 2026, 10:52 UTC≈1,770 views29 reactionsread 3 September 2026
Photo

🧐 Нужен ли здесь брокер? Разбор реальной задачи ⁉️ Начинаем проектировать архитектуру #PostamatGA. На первом черновике схемы уже есть основные компоненты. Ваша задача — определить, где нужен брокер. Не просто поставить Kafka между всеми сервисами, а понять, какую проблему она должна решить 😃 📌 Основной сценарий Пользователь оформил заказ в маркетплейсе и выбрал доставку через постамат. Маркетплейс передал в на

17🔥12

1 Sept 2026, 05:47 UTC≈1,910 views79 reactionsread 3 September 2026
Photo

🎒💐 День знаний, которого, скорее всего, не будет у моих детей 😭💐 Сегодня с утра половина российских рабочих чатов выглядит примерно так: — Буду после 11:00, у ребёнка линейка. — Я тоже на линейке, к 13 буду. — И я. — Понятно. До обеда никого не ищем 😃 По улицам идут дети с огромными букетами, первоклассники теряются среди бантов и школьной формы, а родители делают примерно 700 одинаковых фотографий у школы ❤️‍🔥

68❤‍🔥11

31 Aug 2026, 11:49 UTC≈1,930 views40 reactionsread 3 September 2026
Photo

📦 Новый проект #PostamatGA: брокеры, микросервисы, интеграции, IoT 📦 В этом месяце будем проектировать архитектуру и интеграции платформы для управления сетью постаматов. Разберём не абстрактную систему из учебника, а сценарии, в которых Backend должен управлять тысячами физических устройств, переживать потерю связи и при этом не выдавать одну посылку дважды. 👉 Сеть постаматов #PostamatGA — платформа, где: ▫️ ин

🔥25👍13❤‍🔥2

31 Aug 2026, 06:03 UTC≈2,690 views50 reactionsread 3 September 2026
File

📚 87 терминов по архитектуре для системного аналитика в одном справочнике [с определениями и наглядныими примерами] 📚 ◻️ Общие архитектурные понятия 1. Архитектура системы 2. Компонент 3. Модуль 4. Подсистема 5. Сервис 6. Backend 7. Frontend 8. Web-приложение 9. Сайт 10. Desktop-приложение 11. Мобильное приложение 12. Виджет 🧱 Архитектурные стили и подходы 13. Монолитная архитектура 14. Модульный монолит 15. Сервис

🔥3017❤‍🔥3

30 Aug 2026, 08:13 UTC≈2,540 views47 reactionsread 3 September 2026
Photo

Рабочая неделя в Сан-Франциско 🌉 Беспилотные Waymo и Zoox на каждом шагу. Многочисленные баннеры с ИИ стартапами. Вокруг офисы крупнейших технологических компаний и ощущение, что здесь постоянно запускают что-то новое. Всё-таки Сан-Франциско не просто так называют мировой столицей технологий. Жизнь кипит 🚀 Иногда приезжаю и думаю: «А может, всё-таки переехать сюда?». Но пока понимаю, что мне гораздо больше нр

35🔥12

28 Aug 2026, 09:56 UTC≈3,020 views23 reactionsread 2 September 2026
Video

Как лучше всего использовать перерывы между созвонами ☝️ Сегодня уже пятница, так что совсем скоро созвоны кончатся, и можно будет начать самые лучшие, душевные и последние выходные этого лета! ❤️☀️

😁185

28 Aug 2026, 05:54 UTC≈2,810 views40 reactionsread 2 September 2026
Photo

👀 Как понять, что кандидат отвечает сам, а не читает подсказки ИИ? 👀 Пишу руководителям и всем, кто проводит собеседования. Мы знаем, что сейчас кандидат может запустить программу, которая: ✔️ слушает вопросы ✔️ отправляет их в LLM / AI-чат ✔️ показывает готовый ответ поверх экрана И по ту сторону камеры вы видите почти идеального кандидата: отвечает быстро, уверенно и без ошибок 🧙 Демонстрация экрана не всегда

👎217🔥6👀4👌2

27 Aug 2026, 06:04 UTC≈2,780 views10 reactionsread 2 September 2026
Photo

🚀 Как ИИ меняет работу аналитика, и чему теперь нужно учиться 🚀 Уже почти четыре года я постоянно изучаю ИИ. Остановиться здесь невозможно: появляются новые модели, инструменты и подходы. Как и всегда в ИТ, знания приходится регулярно обновлять. За это время я: ▫️ прошла программы Harvard и Johns Hopkins University по ИИ ▫️ сейчас продолжаю обучение по ИИ-агентам ▫️ научилась писать код и создавать приложения ▫️ с

9👎1

26 Aug 2026, 09:03 UTC≈2,790 views27 reactionsread 2 September 2026
Photo

💸 За какие навыки аналитикам платят до 450 000 ₽? 💸 Не «когда-нибудь в будущем». А уже сейчас. Я не верю громким прогнозам о востребованности ИИ-навыков, а просто проверяю актуальные вакансии и сравниваю требования и зарплаты. Вот что получилось 👇 👉 Обычные вакансии системных аналитиков 🔹 Системный аналитик в edna 💸 250 000–350 000 ₽ 🔗 ссылка на hh Требуют REST API, OpenAPI, SQL, BPMN, ER-модели и умение чита

19👌5🔥3

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

Posts edited after publishing

@getanalysts edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
31 August 2026
Most recent edit
31 August 2026

Forward network

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 5 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Системный анализ | Ольга Пономарева
@system_analyse · 31,602
Telegram ranks this channel #5 of 97 here — alongside 96 others — read 6 September 2026
Системный и Бизнес-анализ
@ba_sa_analytics · 51,879
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 24 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“GetAnalyst - Навыки • Системный анализ • Бизнес-анализ” (@getanalysts), 22,369 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/getanalysts.

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.