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

Channel

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

@sys_sa

On this record: Topic · Growth · Engagement · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

19,117subscribers

+36 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
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 October 2026
Measurements held37
Confirmed unchanged1 time, most recently 14 October 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 why it has no browse page of its own yet.

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 subscribers19,1177 August 202614 October 2026
37 measurements spanning 68 days, net +36. 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 37
Measured (UTC)SubscribersChange
14 Oct 2026, 11:1019,117+10
12 Oct 2026, 21:1619,107+14
8 Oct 2026, 11:4019,093-24
4 Oct 2026, 03:1819,117+10
25 Sept 2026, 06:1919,107-19
18 Sept 2026, 23:3819,126+10
16 Sept 2026, 15:3819,116+6
14 Sept 2026, 20:3919,110+9
13 Sept 2026, 08:1819,101+1
11 Sept 2026, 11:5919,100+17
8 Sept 2026, 15:3719,083+8
5 Sept 2026, 08:0019,075+1
3 Sept 2026, 10:1719,074-2
2 Sept 2026, 05:5819,076-2
1 Sept 2026, 08:3619,078-3
31 Aug 2026, 10:5719,081-2
30 Aug 2026, 12:4719,083+4
29 Aug 2026, 09:1419,079-5
28 Aug 2026, 11:5219,084+1
27 Aug 2026, 09:1419,083first reading

Engagement

23 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 57 pages 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 23 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

794 reactions across 22 posts, in 10 distinct kinds. The most used accounts for 34.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤27734.9%
🔥19624.7%
👍16821.2%
😁9512.0%
💩202.52%
⚡111.39%
👏111.39%
🤣111.39%
😢40.504%
👎10.126%

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

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

Telegram Stars

Stars received
4
across the posts below
Posts paid on
4
of 22 we hold a reading for · 18%
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 23 most recent posts we hold for this entry, published 14 January 2026 to 1 September 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
4.35%
1 of 23 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
2,010
over 1 measured post
Median views · rest
11,000
over 21 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
2SDnjdVJmgX11 September 20261 September 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 23 most recent posts we hold, published 14 January 2026 to 1 September 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

1 Sept 2026, 15:01 UTC≈2,010 views23 reactionsread 3 September 2026
Advertisementerid 2SDnjdVJmgXPhoto

100 откликов, 0 собеседований. Знакомо? Можно конечно продолжать винить рынок, каждые 5 минут обновлять HH, переписывать резюме в десятый раз Но лучше - наконец разобраться кого в этот период активно нанимают и перестроить маршрут Сейчас мало знать REST, SQL и прочий инструментарий На собесы за 250-300к+ зовут тех, кто понимает, как всё это работает вместе и как спроектировать систему Сильный айти спец сегодня -…

💩16❤6👎1

28 Aug 2026, 07:03 UTC≈2,790 views13 reactionsread 3 September 2026

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

🔥7❤4👍1👏1

19 Aug 2026, 09:09 UTC≈5,500 views16 reactionsread 3 September 2026

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

❤11👍4⚡1

14 Jul 2026, 07:04 UTC≈8,120 views24 reactions1 Starread 3 September 2026

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

🔥15❤8👍1

7 Jul 2026, 11:04 UTC≈8,170 views25 reactions1 Starread 3 September 2026
Photo

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

👍13❤7🔥4👏1

25 Jun 2026, 07:04 UTC≈10,300 views36 reactions1 Starread 3 September 2026

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

❤23👍8🔥5

18 Jun 2026, 07:04 UTC≈8,040 views13 reactionsread 3 September 2026
Forwarded from @lib_analystFile

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

🔥10👍2❤1

16 Jun 2026, 07:04 UTC≈8,380 views19 reactionsread 3 September 2026

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

🔥12❤4👍3

29 May 2026, 13:55 UTC≈9,410 views25 reactions1 Starread 3 September 2026

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

❤13🔥11👏1

16 May 2026, 07:10 UTC≈11,300 views25 reactionsread 3 September 2026

🛡 XSS-уязвимость XSS (Cross‑Site Scripting) — атака, при которой злоумышленник внедряет в веб‑страницу вредоносный код (обычно на JavaScript). Код выполняется в браузере другого пользователя (жертвы) ➡️ хакер находит место, куда можно «подложить» свой скрипт, когда жертва открывает страницу — скрипт крадёт её данные, подменяет содержимое или выполняет действия от её имени На этапе проектирования требований можно:…

👍16❤8👏1

20 Apr 2026, 07:06 UTC≈13,600 views20 reactionsread 3 September 2026

⌛ Impact mapping Impact mapping — техника планирования, которая помогает связать требования с бизнес-результатом Результат — визуальная карта, отвечает на вопросы по порядку: 1. Зачем это делаем? (Цель) 2. Кто может помочь или помешать? (Актор) 3. Как должно измениться их поведение? (Влияние) 4. Что можем создать, чтобы вызвать это изменение? (Результат) 💡 Не строятся функции. Меняется поведение акторов для до…

👍11🔥5❤4

3 Apr 2026, 15:46 UTC≈11,000 views23 reactionsread 3 September 2026

🌐 Web as Native WebView и Web as Native WebView — встроенный в мобильное приложение компонент, который отображает веб-страницы (HTML, CSS, JavaScript) внутри приложения Важно: 🔹 это не отдельное приложение (не Chrome/Safari) 🔹он управляется нативным кодом 🔹 пользователь не видит, что это веб Web as Native — подход, при котором веб-интерфейс используется как мобильное приложение Web — интерфейс и часть логики…

❤18⚡4🔥1

Showing the 12 most recent of 23 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.

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,398
#1
BA & SA | 10000 Interview questions
@SystemAnalystInterview · 10,196
#2
GetAnalyst - Навыки • Системный анализ • Бизнес-анализ
@getanalysts · 22,591
#3
Analyst IT
@analysis_it · 12,291
#4
Systems.Education: Системный Анализ и Проектирование информационных систем: архитектура, интеграции, базы данных
@systems_education · 8,708
#5
Yet Another Burakov
@another_sa · 6,536
#6
Business | System analyst
@ba_and_sa · 17,698
#7
Системный подход
@systemspodhod · 4,259
#8
Старт карьеры IT | System Analyst | Ольга Пономарёва
@start_IT_Olepo · 5,627
#9
Бизнес-анализ | ИТ | ИИ
@bamrus · 18,699
#10
GetAnalyst - Старт карьеры в IT • Системный аналитик • Бизнес-аналитик
@getanalyststart · 5,165
#11
Заметки Аналитика | IT
@notes_analyst · 7,962
#12
Архитектура, Процессы и котики
@bpmn2ru · 13,401
#13
Шерлок в IT
@ItSherlock · 3,233
#14
Tech Analyst Club - проектирование, архитектура, AI
@techanalyst_club · 3,400
#15
Владислав Князев
@godnolytika · 6,540
#16
Заметки системного аналитика
@cacaovmacao · 3,884
#17
Analyst Boost. Никита Харичкин
@Analyst_Boost · 5,522
#18
Кунг-Фу Аналитика
@kungfuanalytic · 2,198
#19
BApedia | Бизнес-анализ
@ba_wiki · 4,056
#20
Пасека аналитика | System Analysis
@apiaryanalyst · 1,434
#21
Системные аналитики Контура
@analysis_conference_kontur · 2,100
#22
Системный аналитик с нуля | Альбина Гараева
@garaeva_it · 1,082
#23
V{IT}A ZAEBYMBA | Путь корпората
@vitazaebymba · 8,900
#24
ПРО АНАЛИТИКА | СИСТЕМНЫЙ АНАЛИТИК | АЛЕКСАНДР НЕЗДЕМИНА
@proanalitica · 5,979
#25
IT АНАЛитика | Вильд Виктор
@it_deep_sight · 2,065
#26
Про_БА
@pro_ba_it · 779
#27
Системный анализ | Чулан системного аналитика | Антон Зимин
@sa_chulan · 1,809
#28
Бизнес-аналитик | IT
@business_analyst_ru · 5,356
#29
Кладовка аналитика в IT
@analysts_storeroom · 417
#30
Системный и Бизнес-анализ
@ba_sa_analytics · 52,150
#31
Друлеги системного аналитика
@drulegi · 585
#32
аналитик от бога
@godofanalysis · 2,031
#33
Системный суетолог
@systemsyetolog · 917
#34
IT Meeting - митапы и конференции по разработке
@ITMeeting · 15,440
#35
Артем Шпак | Академия Аналитиков
@analyst_academy · 4,598
#36
SA LEAD
@lead_sa · 249
#37
Project management | IT
@pm_and_it · 11,355
#38
Alfa Digital
@alfadigital_jobs · 54,321
#39
👩🏻‍💻 Подкаст Системных Аналитиков | GetAnalyst
@kateit · 2,341
#40
Плохой менеджер Артём Арюткин
@badTechProject · 14,201
#41
Анализ и Лидство | Настя Шкваренко
@shkvarenko_analyst · 751
#42
Системный сдвиг
@systemswing · 10,176
#43
(Не)Системная аналитика by Андрей Царев
@notsystemanalysis · 7,180
#44
PRO продукты и системы | Иннокентий Бодров
@spherical_analyst · 2,622
#45
Денис Бесков написал
@denis_beskov · 3,791
#46
API. Архитектура. Веб-сервисы | Глеб Учитель
@openstudyit · 3,364
#47
BABOK-School: бизнес-анализ и проектирование ИС, архитектура и интеграция: статьи, тесты
@babok_school · 3,562
#48
Анна Сретенская¦ Управление изменениями
@clvlmanagement · 3,431
#49
Наташа Косинова. Варю айти СУП
@start_in_IT · 2,570
#50
Валентин Заботин | Аналитик маминой подруги
@life_in_analytics · 2,347
#51
Карьера аналитика
@analytics_career · 2,745
#52
Системный сервант
@breakfront · 2,654
#53
Listen IT
@listenit_channel · 7,643 (as read 3 October 2026)
#54
Сёрф Бизнес-анализ
@surf_analyst · 1,170
#55
Архитектура ИТ-решений
@it_arch · 16,244
#56
Клуб (вне)системных аналитиков
@sys_analyst_club · 1,793
#57
Книжный куб
@book_cube · 15,774
#58
BA / SA Materials
@ba_sa_materials · 1,204
#59
ИТ-Пикник
@IT_picnic · 23,040
#60
Концепт Разработка
@concept_software · 380
#61
YK's Daily Links
@yksdailylinks · 202
#62
Команда T1
@t1career · 12,777
#63
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 38,297
#64
Айтишник обыкновенный 🐰
@default_itshnik · 1,910
#65
HR-Tech.Карьера 🔥
@HRTech_Jobs · 9,877
#66
Хабр
@habr_com · 133,162
#67
Вакансии в HR-Аналитике
@HR_Analytics_Jobs · 7,313
#68
Минцифры России
@mintsifry · 233,805
#69
Уставший техдир
@tired_glebmikheev · 17,296
#70
Programmer & IT Memes
@itmemes · 122,671
#71
Максим Цепков
@mtsepkov · 2,330
#72
ITKatya: культурные паттерны в IT
@ValueGoalsDDD · 1,764
#73
SPb BA/SA: накапливая знания
@spbcoachanel · 3,236
#74
ИТ наизнанку | Владимир Ловцов
@it_underside · 972
#75
Марина Ахрамеева |По делу
@BA_by_MA · 609
#76
Т-Образование
@tbank_education · 113,619
#77
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 27,982
#78
Russian Association of Software Architects
@ru_arc · 4,345
#79
Aston
@astonit · 2,799
#80
Летний Аналитический Фестиваль
@lafestconf · 519
#81
BA community
@BAunity · 2,501
#82
Chief Philosophy Officer
@chief_philosophy_officer · 6,766
#83
Продуктовая полка
@productshelf · 6,415
#84
Процессы BPM, проекты PM, архитектура предприятий EA, стратегия
@timethod · 3,969
#85
Код Желтый
@kod_zheltyi · 33,366
#86
T-Crew
@t_crew · 43,499
#87
getmatch: канал про карьеру в IT
@g_jobchannel · 18,891
#88
Деплой | Ваня Ботанов
@dev_yttg · 7,218
#89
Ozon Tech
@ozon_tech · 29,962
#90
На собесе как на танцполе
@tryoutonadancefloor · 5,794
#91
Записная книжка аналитика
@AnalyticsHumor · 1,978
#92
Вакансии аналитиков без опыта · BA, SA
@job4analyst_junior · 1,399
#93
Бэкдор
@whackdoor · 1,571,825
#94
Антонов такой Антонов
@auantonov · 321,322
#95
Job for Analysts & Data Scientists
@foranalysts · 37,226
#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,591
Telegram ranks this channel #2 of 96 here — alongside 95 others — read 20 September 2026
Системный анализ | Ольга Пономарева
@system_analyse · 31,398
Telegram ranks this channel #4 of 97 here — alongside 96 others — read 6 September 2026
Системный и Бизнес-анализ
@ba_sa_analytics · 52,150
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 14 October 2026 — this entry's latest reading, not the date you are reading this.

“Системный Аналитик” (@sys_sa), 19,117 subscribers as measured 14 October 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.