Telegram RegisterThe public register of Telegram
Telegram profile photo for Системный Аналитик

Channel

Системный Аналитик

@sys_sa

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

19,116subscribers

+35 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-1001433682288
TypeChannel
Username@sys_sa
DescriptionКанал для системных аналитиков и не только: подборки полезных материалов на все случаи жизни. Реклама и сотрудничество @radale https://gosuslugi.ru/snet/67b0613c6411ff785396754a
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/sys_sa

Topic

Job listings — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.

Growth

19,07419,12619,1007 August 2026 — 19,081 subscribers7 August 2026 — 19,081 subscribers8 August 2026 — 19,077 subscribers9 August 2026 — 19,081 subscribers10 August 2026 — 19,082 subscribers11 August 2026 — 19,083 subscribers12 August 2026 — 19,089 subscribers13 August 2026 — 19,096 subscribers14 August 2026 — 19,088 subscribers16 August 2026 — 19,090 subscribers17 August 2026 — 19,091 subscribers18 August 2026 — 19,095 subscribers19 August 2026 — 19,094 subscribers20 August 2026 — 19,089 subscribers22 August 2026 — 19,082 subscribers23 August 2026 — 19,077 subscribers25 August 2026 — 19,084 subscribers27 August 2026 — 19,083 subscribers28 August 2026 — 19,084 subscribers29 August 2026 — 19,079 subscribers30 August 2026 — 19,083 subscribers31 August 2026 — 19,081 subscribers1 September 2026 — 19,078 subscribers2 September 2026 — 19,076 subscribers3 September 2026 — 19,074 subscribers5 September 2026 — 19,075 subscribers8 September 2026 — 19,083 subscribers11 September 2026 — 19,100 subscribers13 September 2026 — 19,101 subscribers14 September 2026 — 19,110 subscribers16 September 2026 — 19,116 subscribers18 September 2026 — 19,126 subscribers25 September 2026 — 19,107 subscribers4 October 2026 — 19,117 subscribers8 October 2026 — 19,093 subscribers12 October 2026 — 19,107 subscribers14 October 2026 — 19,117 subscribers15 October 2026 — 19,119 subscribers17 October 2026 — 19,120 subscribers19 October 2026 — 19,117 subscribers20 October 2026 — 19,111 subscribers21 October 2026 — 19,107 subscribers23 October 2026 — 19,106 subscribers24 October 2026 — 19,102 subscribers25 October 2026 — 19,099 subscribers27 October 2026 — 19,100 subscribers27 October 2026 — 19,099 subscribers29 October 2026 — 19,097 subscribers30 October 2026 — 19,098 subscribers31 October 2026 — 19,101 subscribers1 November 2026 — 19,106 subscribers2 November 2026 — 19,104 subscribers3 November 2026 — 19,106 subscribers4 November 2026 — 19,109 subscribers5 November 2026 — 19,108 subscribers6 November 2026 — 19,104 subscribers7 November 2026 — 19,101 subscribers8 November 2026 — 19,103 subscribers10 November 2026 — 19,111 subscribers12 November 2026 — 19,116 subscribers19,1167 August 202612 November 2026
60 measurements spanning 97 days, net +35. 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 19,066–19,134 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
12 Nov 2026, 09:1619,116+5
10 Nov 2026, 05:2019,111+8
8 Nov 2026, 16:1719,103+2
7 Nov 2026, 06:5919,101-3
6 Nov 2026, 02:5819,104-4
5 Nov 2026, 00:4619,108-1
4 Nov 2026, 03:1519,109+3
3 Nov 2026, 05:4519,106+2
2 Nov 2026, 08:1919,104-2
1 Nov 2026, 05:1919,106+5
31 Oct 2026, 08:0619,101+3
30 Oct 2026, 06:5919,098+1
29 Oct 2026, 04:4119,097-2
27 Oct 2026, 23:2919,099-1
27 Oct 2026, 02:2819,100+1
25 Oct 2026, 02:2019,099-3
24 Oct 2026, 01:2719,102-4
23 Oct 2026, 02:4819,106-1
21 Oct 2026, 23:4619,107-4
20 Oct 2026, 16:3619,111first reading

Engagement

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

ERR · 30 days
13.8%
avg views ÷ 19,116 subscribers
Avg views / post
2,650
2 posts measured
Reaction rate
0.87%
reactions ÷ views · ER floor
Posts in window
2
of 26 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 13 November 2026
Posts held26 (14 January 2026 – 13 November 2026)
Views total5,290
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 17:58 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

Photos
94
Videos
4
Links
278

Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

876 reactions across 25 posts, in 10 distinct kinds. The most used accounts for 36.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤32036.5%
🔥20723.6%
👍19822.6%
😁9510.8%
👏121.37%
🤡121.37%
⚡111.26%
🤣111.26%
💩60.685%
😢40.457%

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

Measured over the 26 most recent posts we hold, published 14 January 2026 to 13 November 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
4
of 25 we hold a reading for · 16%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sys_sa. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 26 most recent posts we hold for this entry, published 14 January 2026 to 13 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
3.85%
1 of 26 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,950
over 1 measured post
Median views · rest
11,200
over 24 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFHjJ4i6113 November 202613 November 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 26 most recent posts we hold, published 14 January 2026 to 13 November 2026. 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

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 13:06 UTC≈1,950 views15 reactionsread 14 November 2026
Advertisementerid 2W5zFHjJ4i6

Работа аналитика теперь включает ИИ-агентов В работе СА все чаще появляется генеративный ИИ — для черновиков ТЗ, сводок по требованиям, разбора интервью. Точечные промпты в чате помогают, но результат все равно нужно собрать и разложить руками. Следующий уровень — собрать свой ИИ-агент: систему, которая принимает запрос, обращается к модели и сама сохраняет результат в нужном формате. Разберем сборку пошагово на бе…

🤡12💩2❤1

10 Nov 2026, 07:02 UTC≈3,340 views31 reactionsread 14 November 2026

🔄 Паттерны Outbox и Inbox Transactional Outbox и Transactional Inbox — парные паттерны надёжной доставки сообщений между сервисами через брокер ➡️ Outbox работает на стороне отправителя: событие уходит в брокер тогда и только тогда, когда зафиксировалась бизнес-транзакция ⬅️ Inbox — на стороне получателя: одно и то же сообщение не обрабатывается дважды Зачем нужны ❎ Типовая ошибка при интеграции через брокер — «…

👍23❤8

9 Oct 2026, 09:52 UTC≈6,240 views11 reactionsread 14 November 2026

💡 SMART SMART — методика постановки целей и задач ✨Их формулировка проверяется по 5 критериям: если не проходит хотя бы по одному пункту — нужно исправить ✨Превращает размытые пожелания в проверяемые формулировки Основные критерии ⚪️S — Specific (конкретная): цель однозначно описывает ожидаемый результат. Без «улучшить», «оптимизировать», «сделать удобнее» — такие слова каждый понимает по-своему. Контрольный воп…

❤7👍2🔥2

28 Sept 2026, 08:03 UTC≈7,430 views22 reactionsread 14 November 2026

🔼AMQP, MQTT и STOMP AMQP, MQTT и STOMP — независимые протоколы обмена сообщениями прикладного уровня Приложения используют их, чтобы общаться с брокером сообщений поверх TCP ✖️ это не версии одного протокола и не преемники друг друга ✔️ каждый создавался под свою задачу: 🟣 AMQP — надёжная корпоративная интеграция и гибкая маршрутизация 🟣 MQTT — лёгкий обмен с устройствами в нестабильной сети 🟣 STOMP — простой текс…

❤20👍1🔥1

28 Aug 2026, 07:03 UTC≈10,600 views21 reactionsread 14 November 2026

❓ ICAM (Incident Cause Analysis Method) ICAM (Incident Cause Analysis Method) — метод разбора инцидентов 💚 ищет системные причины, а не останавливается на ошибке конкретного человека 💚 по итогам разбора формулируют меры, чтобы инцидент не повторился 💚 Ключевой вопрос метода — не «кто виноват?», а «почему система это допустила?» 💚 Подходит для ИТ-инцидентов: сбоев систем, киберинцидентов, отказов бизнес-процессов …

🔥10❤8👍2👏1

19 Aug 2026, 09:09 UTC≈9,860 views19 reactionsread 14 November 2026

🖥 NewSQL NewSQL — класс реляционных СУБД, который совмещает привычный SQL и строгие ACID -транзакции классических баз (с горизонтальной масштабируемостью и производительностью, характерными для NoSQL) Попытка убрать главный компромисс хранения данных: ➖ классические реляционные БД надёжны и согласованы, но плохо масштабируются горизонтально ➖ NoSQL отлично масштабируется, но часто жертвует строгой согласованностью…

❤14👍4⚡1

14 Jul 2026, 07:04 UTC≈10,600 views27 reactions1 Starread 14 November 2026

🔼 Server Driven UI (SDUI) Server Driven UI (SDUI) — архитектурный подход, при котором сервер определяет не только данные, но и структуру пользовательского интерфейса (какие компоненты, в каком порядке и с какими параметрами отрисовать на клиенте) 🍃В обычном приложении клиент «знает», как показать экран 🍃В SDUI клиент превращается в «движок рендеринга» — он просто отрисовывает то, что пришло с сервера в виде деклара…

🔥17❤9👍1

7 Jul 2026, 11:04 UTC≈10,100 views27 reactions1 Starread 14 November 2026
Photo

📊 Сравнение Баз данных и Хранилищ данных ▫️База данных – оперативное хранилище, где содержится "текущее состояние" бизнес-процессов: активные заказы, остатки на складе, профили пользователей и тд ▫️ OLTP (Online Transaction Processing) — обработка транзакций онлайн, способ эксплуатации этой базы 💙Хранилище данных (DWH)— информационная система, в которой хранятся данные из разных источников. Используется для анализ…

👍14❤7🔥4👏2

25 Jun 2026, 07:04 UTC≈12,100 views38 reactions1 Starread 14 November 2026

✏️ Принципы разработки KISS, Бритва Оккама, SSOT, DRY, YAGNI, SOLID Зачем нужны Инженерные принципы это не строгие правила, а ориентир Помогают: 🔸 уменьшать стоимость изменений 🔸 снижать количество ошибок 🔸 упрощать сопровождение 🔸 делать требования понятнее 🔸 избегать избыточных решений 💡 Для системного аналитика принципы служат фильтром при сборе требований, позволяют снизить затраты ещё до написания кода KISS…

❤24👍9🔥5

18 Jun 2026, 07:04 UTC≈9,070 views14 reactionsread 14 November 2026
Forwarded from @lib_analystFile

Ретроспектива в Agile Проверенные методы и инновационные подходы ✍️ Автор: Марк Лоффлер 🗓 Год издания: 2020 🔤 Язык: русский 📚 Объём: 176 стр. Книга представляет систематизированное руководство по проведению Agile-ретроспектив. Рассматриваются 💙базовые принципы ретроспектив 💙этапы подготовки и проведения 💙а также роль фасилитатора. Описаны расширенные подходы, включая системные, распределённые и ориентированные на …

🔥11👍2❤1

16 Jun 2026, 07:04 UTC≈9,470 views21 reactionsread 14 November 2026

🖥 Cookie-файлы Cookie — небольшие данные, которые сайт сохраняет в браузере пользователя и использует при последующих запросах ⏩ Cookie — как номерок в гардеробе. Гардеробщик не запоминает лично, а выдает номерок, по которому находит вещи ⏩ Работают схоже: браузер хранит идентификатор, а сервер по нему понимает, кто выполняет запрос Протокол HTTP — stateless (не хранит состояние). Каждый запрос сам по себе не знае…

🔥13❤5👍3

29 May 2026, 13:55 UTC≈10,100 views27 reactions1 Starread 14 November 2026

🔽 Гонка событий (Race Condition) Гонка событий — ситуация, при которой результат работы системы зависит от порядка выполнения операций Если несколько процессов одновременно работают с одним состоянием, итог может быть непредсказуемым Может возникать в: 🟢микросервисах 🟢распределённых системах 🟢очередях сообщений 🟢асинхронных API 🟢frontend-приложениях 🟢потоковой обработке данных 🍃Сложность гонки событий: проблема пр…

❤15🔥11👏1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts recorded as deleted after publishing

We recorded 5 posts on @sys_sa as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 August 2026
Most recent seen missing
13 November 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
2

Forward network

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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Системный анализ | Ольга Пономарева
@system_analyse · 31,145
#1
BA & SA | 10000 Interview questions
@SystemAnalystInterview · 10,104
#2
GetAnalyst - Навыки • Системный анализ • Бизнес-анализ
@getanalysts · 22,722
#3
Analyst IT
@analysis_it · 12,366
#4
Systems.Education: Системный Анализ и Проектирование информационных систем: архитектура, интеграции, базы данных
@systems_education · 8,671
#5
Yet Another Burakov
@another_sa · 6,511
#6
Business | System analyst
@ba_and_sa · 19,463
#7
Системный подход
@systemspodhod · 4,236
#8
Старт в системном анализе | Ольга Пономарёва
@start_IT_Olepo · 5,585
#9
Бизнес-анализ | ИТ | ИИ
@bamrus · 18,644
#10
GetAnalyst - Старт карьеры в IT • Системный аналитик • Бизнес-аналитик
@getanalyststart · 5,182
#11
Заметки Аналитика | IT
@notes_analyst · 7,888
#12
Архитектура, Процессы и котики
@bpmn2ru · 13,323
#13
Шерлок в IT
@ItSherlock · 3,204
#14
Tech Analyst Club - проектирование, архитектура, AI
@techanalyst_club · 3,490
#15
Владислав Князев
@godnolytika · 6,418
#16
Заметки системного аналитика
@cacaovmacao · 3,855
#17
Analyst Boost. Никита Харичкин
@Analyst_Boost · 5,490
#18
Кунг-Фу Аналитика
@kungfuanalytic · 2,183
#19
BApedia | Бизнес-анализ
@ba_wiki · 4,038
#20
Пасека аналитика | System Analysis
@apiaryanalyst · 1,427
#21
Системные аналитики Контура
@analysis_conference_kontur · 2,086
#22
Системный аналитик с нуля | Альбина Гараева
@garaeva_it · 1,078
#23
V{IT}A ZAEBYMBA | Путь корпората
@vitazaebymba · 8,832
#24
ПРО АНАЛИТИКА | СИСТЕМНЫЙ АНАЛИТИК | АЛЕКСАНДР НЕЗДЕМИНА
@proanalitica · 6,085
#25
IT АНАЛитика | Вильд Виктор
@it_deep_sight · 2,052
#26
Про_БА
@pro_ba_it · 779
#27
Системный анализ | Чулан системного аналитика | Антон Зимин
@sa_chulan · 1,799
#28
Бизнес-аналитик | IT
@business_analyst_ru · 5,357
#29
Кладовка аналитика в IT
@analysts_storeroom · 417
#30
Системный и Бизнес-анализ
@ba_sa_analytics · 52,414
#31
Друлеги системного аналитика
@drulegi · 582
#32
аналитик от бога
@godofanalysis · 2,025
#33
Системный суетолог
@systemsyetolog · 912
#34
IT Meeting - митапы и конференции по разработке
@ITMeeting · 15,486
#35
Артем Шпак | Академия Аналитиков
@analyst_academy · 4,583
#36
SA LEAD
@lead_sa · 247
#37
Project management | IT
@pm_and_it · 11,295
#38
Alfa Digital
@alfadigital_jobs · 53,759
#39
👩🏻‍💻 Подкаст Системных Аналитиков | GetAnalyst
@kateit · 2,365
#40
Плохой менеджер Артём Арюткин
@badTechProject · 14,112
#41
Анализ и Лидство | Настя Шкваренко
@shkvarenko_analyst · 750
#42
Системный сдвиг
@systemswing · 10,144
#43
(Не)Системная аналитика by Андрей Царев
@notsystemanalysis · 7,198
#44
PRO продукты и системы | Иннокентий Бодров
@spherical_analyst · 2,605
#45
Денис Бесков написал
@denis_beskov · 3,748
#46
API. Архитектура. Веб-сервисы | Глеб Учитель
@openstudyit · 3,337
#47
BABOK-School: бизнес-анализ и проектирование ИС, архитектура и интеграция: статьи, тесты
@babok_school · 3,540
#48
Анна Сретенская¦ Управление изменениями
@clvlmanagement · 3,397
#49
Наташа Косинова. Варю айти СУП
@start_in_IT · 2,553
#50
Валентин Заботин | Аналитик маминой подруги
@life_in_analytics · 2,382
#51
Карьера аналитика
@analytics_career · 2,730
#52
Системный сервант
@breakfront · 2,632
#53
Listen IT
@listenit_channel · 7,643 (as read 3 October 2026)
#54
Сёрф Бизнес-анализ
@surf_analyst · 1,164
#55
Архитектура ИТ-решений
@it_arch · 16,299
#56
Клуб (вне)системных аналитиков
@sys_analyst_club · 1,787
#57
Книжный куб
@book_cube · 19,415
#58
BA / SA Materials
@ba_sa_materials · 1,203
#59
ИТ-Пикник
@IT_picnic · 22,772
#60
Концепт Разработка
@concept_software · 377
#61
YK's Daily Links
@yksdailylinks · 202
#62
Команда T1
@t1career · 12,849
#63
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 40,667
#64
Айтишник обыкновенный 🐰
@default_itshnik · 1,883
#65
HR-Tech.Карьера 🔥
@HRTech_Jobs · 9,833
#66
Хабр
@habr_com · 134,609
#67
Вакансии в HR-Аналитике
@HR_Analytics_Jobs · 7,247
#68
Минцифры России
@mintsifry · 232,323
#69
Уставший техдир
@tired_glebmikheev · 18,725
#70
Programmer & IT Memes
@itmemes · 121,889
#71
Максим Цепков
@mtsepkov · 2,364
#72
ITKatya: культурные паттерны в IT
@ValueGoalsDDD · 1,750
#73
SPb BA/SA: накапливая знания
@spbcoachanel · 3,236
#74
ИТ наизнанку | Владимир Ловцов
@it_underside · 1,245
#75
Марина Ахрамеева |По делу
@BA_by_MA · 605
#76
Т-Образование
@tbank_education · 113,733
#77
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 32,624
#78
Russian Association of Software Architects
@ru_arc · 4,346
#79
Aston
@astonit · 2,784
#80
Летний Аналитический Фестиваль
@lafestconf · 521
#81
BA community
@BAunity · 2,483
#82
Chief Philosophy Officer
@chief_philosophy_officer · 6,737
#83
Продуктовая полка
@productshelf · 6,366
#84
Процессы BPM, проекты PM, архитектура предприятий EA, стратегия
@timethod · 3,964
#85
Код Желтый
@kod_zheltyi · 33,570
#86
T-Crew
@t_crew · 43,528
#87
getmatch: канал про карьеру в IT
@g_jobchannel · 18,960
#88
Деплой | Ваня Ботанов
@dev_yttg · 7,184
#89
Ozon Tech
@ozon_tech · 30,231
#90
На собесе как на танцполе
@tryoutonadancefloor · 5,758
#91
Записная книжка аналитика
@AnalyticsHumor · 1,973
#92
Вакансии аналитиков без опыта · BA, SA
@job4analyst_junior · 1,397
#93
Бэкдор
@whackdoor · 1,535,262
#94
Антонов такой Антонов
@auantonov · 321,397
#95
Job for Analysts & Data Scientists
@foranalysts · 37,897
#96

Read from Telegram’s recommendation API, most recently 3 October 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

GetAnalyst - Навыки • Системный анализ • Бизнес-анализ
@getanalysts · 22,722
Telegram ranks this channel #2 of 96 here — alongside 95 others — read 20 September 2026
Системный анализ | Ольга Пономарева
@system_analyse · 31,145
Telegram ranks this channel #4 of 97 here — alongside 96 others — read 6 September 2026
Системный и Бизнес-анализ
@ba_sa_analytics · 52,414
Telegram ranks this channel #18 of 90 here — alongside 89 others — read 24 August 2026

This channel appears in 3 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Системный Аналитик” (@sys_sa), 19,116 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/sys_sa.

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.