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,645subscribers

+404 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 live23 October 2026
Measurements held45
Confirmed unchanged1 time, most recently 23 October 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,64522,4437 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 subscribers4 October 2026 — 22,536 subscribers9 October 2026 — 22,562 subscribers13 October 2026 — 22,591 subscribers14 October 2026 — 22,607 subscribers15 October 2026 — 22,612 subscribers16 October 2026 — 22,615 subscribers18 October 2026 — 22,622 subscribers19 October 2026 — 22,618 subscribers20 October 2026 — 22,623 subscribers21 October 2026 — 22,620 subscribers22 October 2026 — 22,643 subscribers23 October 2026 — 22,645 subscribers7 August 202623 October 2026
45 measurements spanning 77 days, net +404. 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,180–22,706 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
23 Oct 2026, 13:2722,645+2
22 Oct 2026, 14:2922,643+23
21 Oct 2026, 10:5622,620-3
20 Oct 2026, 07:3522,623+5
19 Oct 2026, 06:2022,618-4
18 Oct 2026, 02:5522,622+7
16 Oct 2026, 23:5022,615+3
15 Oct 2026, 21:2822,612+5
14 Oct 2026, 20:4622,607+16
13 Oct 2026, 11:5722,591+29
9 Oct 2026, 07:3722,562+26
4 Oct 2026, 17:3722,536+27
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,369first reading

Engagement

85 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 84 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.1%
avg views ÷ 22,645 subscribers
Avg views / post
2,510
30 posts measured
Reaction rate
1.33%
reactions ÷ views · ER floor
Posts in window
30
of 85 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 20 October 2026
Posts held85 (26 July 2026 – 20 October 2026)
Views total75,200
Reactions total1,001
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Oct 2026, 08:11 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
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,861 reactions across 84 posts, in 19 distinct kinds. The most used accounts for 45.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,30445.6%
🔥70324.6%
❤‍🔥29210.2%
👍2006.99%
🎉722.52%
🤣712.48%
😁662.31%
👎291.01%
💯230.804%
🦄200.699%
👀190.664%
🥰180.629%
👌130.454%
💔80.28%
🤔70.245%
⚡50.175%
😢40.14%
🤩40.14%
😱30.105%

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

Measured over the 85 most recent posts we hold, published 26 July 2026 to 20 October 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 85 we hold a reading for · 2%
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 85 most recent posts we hold for this entry, published 26 July 2026 to 20 October 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

20 Oct 2026, 13:07 UTC≈1,190 views20 reactionsread 21 October 2026
Photo

📁 Потоковая передача и Range: как отдавать большие файлы в REST API 📁 При передаче больших файлов часто смешивают два разных механизма: ✅ потоковую передачу ✅ получение файла частями с Range Но это не одно и то же. 📌 Потоковая передача файла При обычной потоковой передаче клиент отправляет запрос на получение файла: GET /files/4831/content Сервер проверяет права пользователя, начинает читать файл из хранил…

❤13👍6🤔1

20 Oct 2026, 06:02 UTC≈1,620 views26 reactionsread 21 October 2026
Photo

📁 Как вернуть файл в REST API: 5 вариантов реализации с реальными примерами 📁 Формулировки «метод возвращает файл» для разработки недостаточно. Нужно определить: ▫️ где хранится файл ▫️ передаём ли мы его в теле ответа или возвращаем ссылку ▫️ должен ли файл открываться в браузере или скачиваться 📌 1. Передать содержимое файла в теле ответа Подходит, если пользователь должен получить файл сразу, а API самостоят…

❤17🔥7❤‍🔥1🦄1

19 Oct 2026, 12:06 UTC≈2,010 views28 reactionsread 21 October 2026
Photo

📌 Шпаргалка по HTTP-методам: безопасность, идемпотентность, кэшируемость и тело JSON 📌 В англоязычной Wikipedia уже обновили таблицу свойств HTTP-методов: в ней появился новый метод QUERY, описанный в RFC 10008. https://en.wikipedia.org/wiki/HTTP#Request_methods Эта таблица — моя вечная шпаргалка для подготовки к собеседованиям. Свойства методов из таблицы 👇 📤 Запрос может содержать тело — Request payload Показ…

❤20🔥5👍3

19 Oct 2026, 06:03 UTC≈2,030 views11 reactionsread 21 October 2026
Photo

💥 А вы бы решили эту задачу по SQL с JOIN на 4 таблицы? Ответ в конце, а разбор уже сегодня в 19:00 Мск 💥 ИИ может написать SQL-запрос за несколько секунд. Но системному аналитику всё равно нужно разбираться в SQL, чтобы понимать: ▫️ как связаны данные в таблицах; ▫️ как API читает и изменяет данные; ▫️ что нужно изменить в БД под новую функциональность; ▫️ не вернул ли ИИ работающий, но логически неправильный зап…

❤6👍5

18 Oct 2026, 07:38 UTC≈2,380 views36 reactionsread 21 October 2026
Photo

Искать работу сейчас сложно. Хоть джуну, хоть мидлу 😞 Делюсь актуальными новостями с полей: что нам рассказывают HR и работодатели и что мы видим со стороны кандидатов. 👉 Картина по всему миру примерно одинаковая: кандидатов больше, чем вакансий. ▫️HR получают тысячи откликов, а хорошие специалисты неделями не могут дойти даже до первого собеседования. ▫️Экономика плохая, а не AI всех заменил. ▫️ В то же время …

❤25❤‍🔥4🔥3👍2😢2

16 Oct 2026, 06:06 UTC≈3,150 views52 reactionsread 21 October 2026
Photo

❗️ Новый HTTP-метод QUERY: значительное изменение стандарта впервые за 16 лет ❗️ 👉 Новый стандарт RFC 10008 от 15 июня 2026 https://www.rfc-editor.org/info/rfc10008/ добавил новый HTTP-метод "QUERY". Он закрывает боль, с которой аналитики и разработчики встречаются каждый раз, когда проектируют работу со списками и поиском, где нужно: + много фильтров, + сортировки, + пагинация. 👉 Назначение QUERY: поиск по ката…

👍24🔥17❤7❤‍🔥4

15 Oct 2026, 10:12 UTC≈3,070 views61 reactionsread 21 October 2026
File

✅ 64 API-термина для системного аналитика ✅ Собрала мини-книгу по API для работы и подготовки к собеседованиям: короткие определения, примеры и пояснения понятий, которые часто путают 👇 👉 Основы API и HTTP 1. API — программный интерфейс 2. HTTP 3. HTTPS и TLS 4. REST API 5. Ресурс 6. URI и URL 7. Точка обращения к API (Endpoint) 8. Запрос и ответ 👉 Состав запроса и форматы данных 9. Методы HTTP 10. Параметры пут…

❤33🔥24👍2🤩2

14 Oct 2026, 06:06 UTC≈3,220 views14 reactionsread 21 October 2026
Photo

⚡ Если вы уже умеете писать простые SELECT, то следующий шаг, где чаще всего начинается боль — это JOIN. JOIN — это тот самый оператор в SQL, когда многие “вроде понимают”, но в реальной задаче внезапно: 🙁 пропали строки 🙁 появились дубли 🙁 “а почему тут пусто?” 🤖 С ИИ стало проще писать SQL, но не всегда проще понимать, что именно он написал и насколько корректный результат получился. А на технических собеседова…

❤12🔥2

13 Oct 2026, 06:23 UTC≈3,000 views40 reactionsread 21 October 2026
Photo

❌🙅‍♀️🙅‍♂️ Что системному аналитику НЕ нужно уметь в работе с логированием и мониторингом, а что нужно? 🔎 Нужно ли аналитику самостоятельно устанавливать OpenTelemetry Collector, разворачивать Prometheus и администрировать Elasticsearch? Нет. Это задача DevOps и/или разработчиков. Но и требования «логировать запросы и ошибки» или «добавить мониторинг» тоже не результат работы аналитика. 🟢 Задача СА определить: …

❤24👍11🔥3❤‍🔥2

12 Oct 2026, 09:56 UTC≈2,900 views37 reactionsread 21 October 2026
Photo

📊🔥 Grafana, Kibana, OpenTelemetry: какие инструменты наблюдаемости нужны системному аналитику? 🔎 «Посмотрите логи» — фраза, которую системный аналитик рано или поздно услышит на любом проекте. Пользователь сообщает об ошибке. Разработчик говорит, что сервис работает. На дашборде всё зелёное. В логах одного компонента запрос принят успешно. Но результат пользователь так и не получил. Чтобы разобраться, недостаточн…

🔥28❤8👀1

11 Oct 2026, 08:23 UTC≈2,410 views81 reactionsread 14 October 2026
Photo

Мы так заняты тем, что ещё не получилось, что забываем радоваться тому, как далеко уже зашли 🥹 В эту поездку в Сан-Франциско меня прямо накрыло этим ощущением. Я наслаждалась каждой секундой и осознавала масштаб. ИИ, конференция, невероятные встречи, новые знакомства, потрясающие люди. Фото с самой конференции пока даже не трогаю 😀 Через общих знакомых из tech-сферы познакомилась с нереально крутой семьёй. Как же…

❤54🔥27

9 Oct 2026, 07:04 UTC≈1,760 views20 reactionsread 12 October 2026
Forwarded from @kateitPhoto

⚡️ Contract First API в эпоху ИИ-агентов: OpenAPI, AsyncAPI, MCP на практике 🤖 Сначала согласовать контракт API, а потом писать код — в этом суть подхода Contract First. Звучит понятно, пока в команде не возникают вопросы. ▫️ Кто разрабатывает контракт — аналитик или разработчик? ▫️ Что должно быть в OpenAPI-спецификации, а что остаётся в требованиях и документации? ❗️ И зачем системному аналитику разбираться в Git…

👍11🔥7❤‍🔥2

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

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,339
#1
Системный Аналитик
@sys_sa · 19,106
#2
BA & SA | 10000 Interview questions
@SystemAnalystInterview · 10,159
#3
GetAnalyst - Старт карьеры в IT • Системный аналитик • Бизнес-аналитик
@getanalyststart · 5,187
#4
Analyst IT
@analysis_it · 12,339
#5
Systems.Education: Системный Анализ и Проектирование информационных систем: архитектура, интеграции, базы данных
@systems_education · 8,694
#6
Business | System analyst
@ba_and_sa · 19,715
#7
Системный сдвиг
@systemswing · 10,174
#8
Бизнес-анализ | ИТ | ИИ
@bamrus · 18,696
#9
Yet Another Burakov
@another_sa · 6,535
#10
Заметки Аналитика | IT
@notes_analyst · 7,928
#11
Системный подход
@systemspodhod · 4,254
#12
Старт в системном анализе | Ольга Пономарёва
@start_IT_Olepo · 5,619
#13
Архитектура, Процессы и котики
@bpmn2ru · 13,385
#14
API. Архитектура. Веб-сервисы | Глеб Учитель
@openstudyit · 3,358
#15
PRO продукты и системы | Иннокентий Бодров
@spherical_analyst · 2,620
#16
Tech Analyst Club - проектирование, архитектура, AI
@techanalyst_club · 3,438
#17
Наташа Косинова. Варю айти СУП
@start_in_IT · 2,562
#18
Денис Бесков написал
@denis_beskov · 3,789
#19
Анна Сретенская¦ Управление изменениями
@clvlmanagement · 3,415
#20
Шерлок в IT
@ItSherlock · 3,229
#21
Карьера аналитика
@analytics_career · 2,736
#22
BApedia | Бизнес-анализ
@ba_wiki · 4,057
#23
Заметки системного аналитика
@cacaovmacao · 3,873
#24
BABOK-School: бизнес-анализ и проектирование ИС, архитектура и интеграция: статьи, тесты
@babok_school · 3,557
#25
Бизнес-аналитик | IT
@business_analyst_ru · 5,357
#26
Валентин Заботин | Аналитик маминой подруги
@life_in_analytics · 2,353
#27
👩🏻‍💻 Подкаст Системных Аналитиков | GetAnalyst
@kateit · 2,345
#28
Владислав Князев
@godnolytika · 6,498
#29
Клуб (вне)системных аналитиков
@sys_analyst_club · 1,792
#30
Analyst Boost. Никита Харичкин
@Analyst_Boost · 5,516
#31
Системный сервант
@breakfront · 2,638
#32
Кунг-Фу Аналитика
@kungfuanalytic · 2,190
#33
Системные аналитики Контура
@analysis_conference_kontur · 2,095
#34
Системный и Бизнес-анализ
@ba_sa_analytics · 52,666
#35
аналитик от бога
@godofanalysis · 2,029
#36
ПРО АНАЛИТИКА | СИСТЕМНЫЙ АНАЛИТИК | АЛЕКСАНДР НЕЗДЕМИНА
@proanalitica · 5,967
#37
ИТ-Пикник
@IT_picnic · 22,963
#38
Друлеги системного аналитика
@drulegi · 582
#39
Про_БА
@pro_ba_it · 780
#40
Пасека аналитика | System Analysis
@apiaryanalyst · 1,429
#41
V{IT}A ZAEBYMBA | Путь корпората
@vitazaebymba · 8,869
#42
Системный аналитик с нуля | Альбина Гараева
@garaeva_it · 1,079
#43
Сёрф Бизнес-анализ
@surf_analyst · 1,171
#44
БА/СА/Тоси-боси про анализ
@tosibosiba · 4,106
#45
IT АНАЛитика | Вильд Виктор
@it_deep_sight · 2,067
#46
Хабр
@habr_com · 133,496
#47
ИТ наизнанку | Владимир Ловцов
@it_underside · 965
#48
Системный анализ | Чулан системного аналитика | Антон Зимин
@sa_chulan · 1,803
#49
Системный суетолог
@systemsyetolog · 914
#50
Кладовка аналитика в IT
@analysts_storeroom · 416
#51
Бизнес и системный анализ с Максом Филипповым
@ba_with_max · 1,456
#52
Артем Шпак | Академия Аналитиков
@analyst_academy · 4,603
#53
Анализ и Лидство | Настя Шкваренко
@shkvarenko_analyst · 750
#54
SPb BA/SA: накапливая знания
@spbcoachanel · 3,237
#55
Alfa Digital
@alfadigital_jobs · 54,311
#56
Аналитик Pro
@ITAnalystPro · 845
#57
ITKatya: культурные паттерны в IT
@ValueGoalsDDD · 1,760
#58
Alfa Campus
@alfa_campus · 10,760
#59
SA LEAD
@lead_sa · 249
#60
Продуктовая полка
@productshelf · 6,406
#61
Холиварные аналитические посиделки
@holivarno · 1,123
#62
IT Meeting - митапы и конференции по разработке
@ITMeeting · 15,487
#63
Project management | IT
@pm_and_it · 11,330
#64
Анка Аналитик
@ankalytics · 476 (as read 20 September 2026)
#65
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 27,943
#66
Аналитика и growth mind-set
@analyticsgrowthmindset · 17,469
#67
Listen IT
@listenit_channel · 7,589 (as read 20 September 2026)
#68
SQL Academy: всё о реляционных БД и SQL
@sqlacademyofficial · 11,914
#69
(Не)Системная аналитика by Андрей Царев
@notsystemanalysis · 7,195
#70
На собесе как на танцполе
@tryoutonadancefloor · 5,786
#71
BA / SA Materials
@ba_sa_materials · 1,204
#72
Записная книжка аналитика
@AnalyticsHumor · 1,976
#73
Programmer & IT Memes
@itmemes · 122,383
#74
Книжный куб
@book_cube · 15,789
#75
BA & SA Jobs | Работа для бизнес и системных аналитиков
@analytics_jobs · 3,521
#76
Минцифры России
@mintsifry · 233,299
#77
Айтишник обыкновенный 🐰
@default_itshnik · 1,902
#78
Архитектура ИТ-решений
@it_arch · 16,248
#79
BA community
@BAunity · 2,490
#80
Команда T1
@t1career · 12,761
#81
Марина Ахрамеева |По делу
@BA_by_MA · 608
#82
YK's Daily Links
@yksdailylinks · 202
#83
Aston
@astonit · 2,799
#84
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 38,471
#85
Вакансии аналитиков без опыта · BA, SA
@job4analyst_junior · 1,402
#86
Т-Образование
@tbank_education · 113,657
#87
Бэкдор
@whackdoor · 1,560,723
#88
T-Crew
@t_crew · 43,608
#89
Уставший техдир
@tired_glebmikheev · 17,427
#90
Максим Цепков
@mtsepkov · 2,355
#91
Job for Analysts & Data Scientists
@foranalysts · 37,512
#92
HR-Tech.Карьера 🔥
@HRTech_Jobs · 9,879
#93
Дашич, беги🚀
@dashich_begi · 41,170
#94
Вакансии в HR-Аналитике
@HR_Analytics_Jobs · 7,290
#95
Naumen | Карьера
@naumen_job · 2,247
#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.

Системный Аналитик
@sys_sa · 19,106
Telegram ranks this channel #3 of 96 here — alongside 95 others — read 3 October 2026
Системный анализ | Ольга Пономарева
@system_analyse · 31,339
Telegram ranks this channel #5 of 97 here — alongside 96 others — read 6 September 2026
Системный и Бизнес-анализ
@ba_sa_analytics · 52,666
Telegram ranks this channel #9 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

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