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

Channel

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

@getanalysts

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

22,509subscribers

+268 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
DescriptionРазбор задач на проектирование систем 🚀 Канал для системных аналитиков, бизнес-аналитиков, тестировщиков и менеджеров проектов Админ @getanalyst Сайт https://getanalyst.ru Чат t.me/getanalystchat Начинающим в IT @getanalyststart
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 live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/getanalysts

Topic

Education — 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 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

22,24122,50922,3757 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 subscribers8 September 2026 — 22,388 subscribers11 September 2026 — 22,406 subscribers13 September 2026 — 22,404 subscribers15 September 2026 — 22,411 subscribers17 September 2026 — 22,439 subscribers19 September 2026 — 22,456 subscribers26 September 2026 — 22,509 subscribers7 August 202626 September 2026
33 measurements spanning 50 days, net +268. 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,201–22,549 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 19:1722,509+53
19 Sept 2026, 15:3822,456+17
17 Sept 2026, 02:0022,439+28
15 Sept 2026, 02:0022,411+7
13 Sept 2026, 09:1422,404-2
11 Sept 2026, 14:5822,406+18
8 Sept 2026, 21:3622,388+19
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,330first reading

Engagement

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

ERR · 30 days
9.40%
avg views ÷ 22,509 subscribers
Avg views / post
2,110
22 posts measured
Reaction rate
1.78%
reactions ÷ views · ER floor
Posts in window
22
of 60 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 21 of 22 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 27 September 2026
Posts held60 (26 July 2026 – 27 September 2026)
Views total46,526
Reactions total816
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 14:51 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
≈2,600
Videos
≈98
Links
≈1,460

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 34s
Average length
47s

Measured directly from 2 videos 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

2,061 reactions across 59 posts, in 19 distinct kinds. The most used accounts for 43.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤90543.9%
🔥47623.1%
❤‍🔥23811.5%
👍1215.87%
🤣713.44%
🎉703.40%
😁663.20%
👎281.36%
💯231.12%
🦄180.873%
👌130.631%
🥰90.437%
💔80.388%
⚡40.194%
👀40.194%
😱30.146%
🤔20.097%
😢10.049%
🤩10.049%

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

Measured over the 60 most recent posts we hold, published 26 July 2026 to 27 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
5
across the posts below
Posts paid on
2
of 60 we hold a reading for · 3%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @getanalysts. 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 60 most recent posts we hold for this entry, published 26 July 2026 to 27 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.

Recent posts

27 Sept 2026, 07:11 UTC≈1,330 views47 reactions1 Starread 27 September 2026
Photo

Уже завтра на самолёт в Сан-Франциско, чтобы пообщаться с коллегами из OpenAI, Anthropic и Google ✈️ А пока эти выходные у меня наконец-то про отдых и перезагрузку после трёх недель работы и учёбы нон-стоп по 10+ часов в день, и нашего большого открытого практикума ❤️‍🔥 Иногда я вообще забываю, сколько всего классного есть рядом. Живу у океана, друзья постоянно зовут куда-то выбраться — покататься на лодке или ях…

❤‍🔥33❤7🔥7

25 Sept 2026, 06:06 UTC≈2,310 views50 reactionsread 27 September 2026
Photo

🔥❤️‍🔥🎉 Вау-вау-вау! Вот это мы отметили! 4 часа практики, море вопросов, десятки схем и невероятная энергия до самого финала. Мы это сделали! По доброй традиции, с учётом всех вопросов и погружений в отдельные темы, у нас получилось 4.5 часа полноценной практики по асинхронным интеграциям с ИИ. Больше 60% участников остались до самого конца, хотя о записи предупредили сразу! Вы просто невероятные 💙 Спасибо всем, к…

❤34🔥10❤‍🔥6

24 Sept 2026, 15:43 UTC≈2,110 views10 reactionsread 27 September 2026
Photo

😂👍👍❤️👌😅😊😊😍😘 ❗️До начала 15 минут❗️ 🧡 «Асинхронная интеграция с ИИ-сервисом: от архитектуры до требований в Confluence» [ЭФИР ЗАВЕРШЕН] Информация о доступе к записи: 🗓 2-6 октября 📌 Только для зарегистрированных участников ❗️ Если уже регистрировались на основной эфир, повторно регистрироваться не нужно. 👉 Получить доступ к записи

❤7❤‍🔥3

24 Sept 2026, 13:02 UTC≈2,290 views12 reactionsread 27 September 2026
Photo

❗️Уже через 3 часа встречаемся онлайн❗️ 👩‍💻 Открытый практикум с Екатериной Ананьевой 🔥 «Асинхронная интеграция с ИИ-сервисом: от архитектуры до требований в Confluence» 🟢 Онлайн ⏰ 19:00 Мск 👉 Зарегистрироваться Ссылку на эфир пришлем за 15 минут до начала. —— Запись будет доступна только для зарегистрированных участников.

❤10❤‍🔥2

24 Sept 2026, 06:04 UTC≈2,530 views85 reactions4 Starsread 27 September 2026
Photo

Пусть хотя бы сегодня всё пойдёт по happy path 🎉🙏🩷 Сегодня праздник у людей, которые слышат фразу «там всё просто», и сразу начинают уточнять роли, статусы, ограничения и альтернативные сценарии. У тех, кто видит 200 OK и первым спрашивает: «А что произойдёт при 429?». Кто превращает «хотим, чтобы было удобно» в требования, по которым действительно можно разработать систему. 👉 И чья работа часто остаётся незаметн…

🎉63❤‍🔥13❤6🔥3

23 Sept 2026, 09:49 UTC≈2,050 views33 reactionsread 27 September 2026
Photo

🧡 6 практических гайдов по Postman для системного аналитика: от REST API до OAuth 2.0 и mTLS 🧡 Документация ≠ реальность. Перед тем как отдавать интеграционную задачу в разработку, системному аналитику важно самостоятельно отправить запросы и проверить, как API внешней системы работает на самом деле. Так можно заранее обнаружить нюансы, которых нет в документации или примерах, и не перекладывать исследование API н…

❤21👍6🔥6

23 Sept 2026, 06:44 UTC≈1,940 views13 reactionsread 27 September 2026
Photo

🤖 Интеграция с AI: 10 требований, которые надо учесть аналитику 🤖 При интеграции с AI-сервисом недостаточно описать эндпоинт, JSON и возможные ошибки. Модель может отвечать по-разному, возвращать результат частями, запрашивать вызовы внутренних сервисов и расходовать непредсказуемое количество токенов. Собрала 10 особенностей, которые важно учесть аналитику в требованиях. 1️⃣ Недетерминированность AI не возвраща…

❤11🔥2

22 Sept 2026, 12:08 UTC≈2,520 views43 reactionsread 27 September 2026
Forwarded from @itgardennPhoto

Друзья, нужна ваша помощь У нашего ученика Вадима нашли рак ободочной кишки в 19 лет. Несмотря на болезнь и лечение, Вадим продолжает учиться в вузе и работать на двух работах, одна из которых – ночные смены курьером, чтобы платить за терапию. Из-за этого ему пришлось уйти из банка, так как совмещать работу в офисе с лечением и учебой стало невозможно. Весь этот год он тянул все сам и ни у кого не просил помощи, …

❤29💔8👍6

22 Sept 2026, 12:06 UTC≈2,030 views36 reactionsread 27 September 2026
Photo

Нужна ваша помощь 🙏 В эти выходные мне написал участник сообщества GetAnalyst и попросил поддержать репостом сбор на лечение для Вадима — молодого аналитика. Вадиму всего 19 лет. У него диагностировали рак ободочной кишки. Несмотря на лечение, он продолжает учиться в вузе и работать на двух работах, включая ночные смены курьером, чтобы оплачивать терапию... История Вадима: https://youtu.be/FYUriR6Pmc0?si=V1qvKq3Ay_…

❤30👍3🔥3

22 Sept 2026, 06:06 UTC≈2,180 views15 reactionsread 27 September 2026
Photo

🔥 [В четверг, 19:00 Мск] Бесплатный онлайн-практикум по асинхронной интеграции с ИИ-сервисом 🔥 В систему ежедневно поступают сотни заявок, которые должен обработать внешний ИИ. Но он отвечает не сразу, на пике возвращает 429, а иногда присылает невалидный JSON. Просто вызвать ИИ-сервис из запроса пользователя и дождаться ответа не получится. Нужно проектировать полноценный асинхронный процесс. Именно такую задачу …

🔥12❤2🦄1

21 Sept 2026, 11:05 UTC≈2,210 views16 reactionsread 27 September 2026
Photo

🎁 Дарю билет на «Стачку 2026» за лучшую тему для доклада Подвожу итоги конкурса, в котором нужно было придумать тему выступления на IT-конференции — серьёзную или смешную. Было много классных предложений, но больше всего мне запала в душу: «Как собрать требования из треда на 200+ сообщений и никого не потерять?» 🥺 (ссылка на сообщение) Кажется, в этой формулировке узнал себя каждый аналитик 😄 Тема получилась мак…

❤6🔥3🥰3❤‍🔥1🤔1🤣1🦄1

21 Sept 2026, 06:03 UTC≈2,320 views8 reactionsread 27 September 2026
Photo

🔥 Сегодня в 19:00 МСК: создаём JSON для API на основе БД и UI ✅🔔 При проектировании JSON аналитику важно связать потребности интерфейса со структурой БД: определить поля запроса и ответа, источники данных, типы и структуру объектов. Иначе между Frontend и Backend возникают расхождения, а требования приходится уточнять уже во время разработки. Сегодня разберём этот процесс на практике: 🧩 Маппинг данных: БД и JSON …

❤7⚡1

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

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

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.

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,554
#1
Системный Аналитик
@sys_sa · 19,107
#2
BA & SA | 10000 Interview questions
@SystemAnalystInterview · 10,331
#3
GetAnalyst - Старт карьеры в IT • Системный аналитик • Бизнес-аналитик
@getanalyststart · 5,134
#4
Analyst IT
@analysis_it · 12,323
#5
Systems.Education: Системный Анализ и Проектирование информационных систем: архитектура, интеграции, базы данных
@systems_education · 8,730
#6
Business | System analyst
@ba_and_sa · 17,725
#7
Системный сдвиг
@systemswing · 10,181
#8
Бизнес-анализ | ИТ | ИИ
@bamrus · 18,711
#9
Yet Another Burakov
@another_sa · 6,558
#10
Заметки Аналитика | IT
@notes_analyst · 8,034
#11
Системный подход
@systemspodhod · 4,273
#12
Старт карьеры IT | System Analyst | Ольга Пономарёва
@start_IT_Olepo · 5,650
#13
BPM, Бизнес-процессы и котики
@bpmn2ru · 13,409
#14
API. Архитектура. Веб-сервисы | Глеб Учитель
@openstudyit · 3,363
#15
PRO продукты и системы | Иннокентий Бодров
@spherical_analyst · 2,619
#16
Tech Analyst Club - проектирование, архитектура, AI
@techanalyst_club · 3,341
#17
Наташа Косинова. Варю айти СУП
@start_in_IT · 2,573
#18
Денис Бесков написал
@denis_beskov · 3,829
#19
Анна Сретенская
@clvlmanagement · 3,454
#20
Шерлок в IT
@ItSherlock · 3,252
#21
Карьера аналитика
@analytics_career · 2,757
#22
BApedia | Бизнес-анализ
@ba_wiki · 4,064
#23
Заметки системного аналитика
@cacaovmacao · 3,903
#24
BABOK-School: бизнес-анализ и проектирование ИС, архитектура и интеграция: статьи, тесты
@babok_school · 3,573
#25
Бизнес-аналитик | IT
@business_analyst_ru · 5,356
#26
Валентин Заботин | Аналитик маминой подруги
@life_in_analytics · 2,339
#27
👩🏻‍💻 Подкаст Системных Аналитиков | GetAnalyst
@kateit · 2,311
#28
Владислав Князев
@godnolytika · 6,598
#29
Клуб (вне)системных аналитиков
@sys_analyst_club · 1,797
#30
Analyst Boost. Никита Харичкин
@Analyst_Boost · 5,534
#31
Системный сервант
@breakfront · 2,668
#32
Кунг-Фу Аналитика
@kungfuanalytic · 2,212
#33
Системные аналитики Контура
@analysis_conference_kontur · 2,118
#34
Системный и Бизнес-анализ
@ba_sa_analytics · 51,700
#35
аналитик от бога
@godofanalysis · 2,033
#36
ПРО АНАЛИТИКА | СИСТЕМНЫЙ АНАЛИТИК | АЛЕКСАНДР НЕЗДЕМИНА
@proanalitica · 5,991
#37
ИТ-Пикник
@IT_picnic · 23,126
#38
Друлеги системного аналитика
@drulegi · 587
#39
Про_БА
@pro_ba_it · 766
#40
Пасека аналитика | System Analysis
@apiaryanalyst · 1,440
#41
V{IT}A ZAEBYMBA | Путь корпората
@vitazaebymba · 8,928
#42
Системный аналитик с нуля | Альбина Гараева
@garaeva_it · 1,095
#43
Сёрф Бизнес-анализ
@surf_analyst · 1,169
#44
БА/СА/Тоси-боси про анализ
@tosibosiba · 4,105
#45
IT АНАЛитика | Вильд Виктор
@it_deep_sight · 2,066
#46
Хабр
@habr_com · 132,465
#47
ИТ наизнанку | Владимир Ловцов
@it_underside · 972
#48
Системный анализ | Чулан системного аналитика | Антон Зимин
@sa_chulan · 1,818
#49
Системный суетолог
@systemsyetolog · 916
#50
Кладовка аналитика в IT
@analysts_storeroom · 418
#51
Бизнес и системный анализ с Максом Филипповым
@ba_with_max · 1,460
#52
Артем Шпак | Академия Аналитиков
@analyst_academy · 4,605
#53
Анализ и Лидство | Настя Шкваренко
@shkvarenko_analyst · 748
#54
SPb BA/SA: накапливая знания
@spbcoachanel · 3,221
#55
Alfa Digital
@alfadigital_jobs · 54,435
#56
Аналитик Pro
@ITAnalystPro · 853
#57
ITKatya: культурные паттерны в IT
@ValueGoalsDDD · 1,775
#58
Alfa Campus
@alfa_campus · 10,801
#59
SA LEAD
@lead_sa · 253
#60
Продуктовая полка
@productshelf · 6,417
#61
Холиварные аналитические посиделки
@holivarno · 1,130
#62
IT Meeting - митапы и конференции по разработке
@ITMeeting · 15,391
#63
Project management | IT
@pm_and_it · 11,370
#64
Анка Аналитик
@ankalytics · 476 (as read 20 September 2026)
#65
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 28,120
#66
Аналитика и growth mind-set
@analyticsgrowthmindset · 17,582
#67
Listen IT
@listenit_channel · 7,589 (as read 20 September 2026)
#68
SQL Academy: всё о реляционных БД и SQL
@sqlacademyofficial · 11,766
#69
(Не)Системная аналитика by Андрей Царев
@notsystemanalysis · 7,574
#70
На собесе как на танцполе
@tryoutonadancefloor · 5,809
#71
BA / SA Materials
@ba_sa_materials · 1,201
#72
Записная книжка аналитика
@AnalyticsHumor · 1,977
#73
Programmer & IT Memes
@itmemes · 123,290
#74
Книжный куб
@book_cube · 15,749
#75
BA & SA Jobs | Работа для бизнес и системных аналитиков
@analytics_jobs · 3,303
#76
Минцифры России
@mintsifry · 234,926
#77
Айтишник обыкновенный 🐰
@default_itshnik · 1,919
#78
Архитектура ИТ-решений
@it_arch · 16,225
#79
BA community
@BAunity · 2,494
#80
Команда T1
@t1career · 12,703
#81
Марина Ахрамеева |Думай в тишине
@BA_by_MA · 617
#82
YK's Daily Links
@yksdailylinks · 202
#83
Aston
@astonit · 2,792
#84
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 37,537
#85
Вакансии аналитиков без опыта · BA, SA
@job4analyst_junior · 1,404
#86
Т-Образование
@tbank_education · 113,416
#87
Бэкдор
@whackdoor · 1,603,481
#88
T-Crew
@t_crew · 43,385
#89
Уставший техдир
@tired_glebmikheev · 17,275
#90
Максим Цепков
@mtsepkov · 2,326
#91
Job for Analysts & Data Scientists
@foranalysts · 36,643
#92
HR-Tech.Карьера 🔥
@HRTech_Jobs · 9,701
#93
Дашич, беги🚀
@dashich_begi · 37,414
#94
Вакансии в HR-Аналитике
@HR_Analytics_Jobs · 7,172
#95
Naumen | Карьера
@naumen_job · 2,261
#96

Read from Telegram’s recommendation API, most recently 20 September 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.

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

“GetAnalyst - Навыки • Системный анализ • Бизнес-анализ” (@getanalysts), 22,509 subscribers as measured 26 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.