⚡ Через час начинаем вебинар «С чего начать стратегию защиты корпоративного ИИ: паспорт ИИ-системы» ⚡ Последняя возможность успеть зарегистрироваться 🗒
❤2

Channel
@mtsai
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
7,149subscribers
-92 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001593715747 |
|---|---|
| Type | Channel |
| Username | @mtsai |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/mtsai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 03:58 | 7,149 | -18 |
| 3 Sept 2026, 18:02 | 7,167 | -9 |
| 31 Aug 2026, 09:27 | 7,176 | +2 |
| 27 Aug 2026, 23:47 | 7,174 | -6 |
| 24 Aug 2026, 13:53 | 7,180 | -2 |
| 21 Aug 2026, 04:54 | 7,182 | -6 |
| 18 Aug 2026, 10:52 | 7,188 | -16 |
| 15 Aug 2026, 05:38 | 7,204 | -17 |
| 12 Aug 2026, 06:22 | 7,221 | -13 |
| 9 Aug 2026, 11:01 | 7,234 | -6 |
| 6 Aug 2026, 12:11 | 7,240 | -1 |
| 6 Aug 2026, 03:16 | 7,241 | no change |
| 5 Aug 2026, 22:01 | 7,241 | first reading |
15 posts held, back to 20 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 13 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 18 August 2026 |
|---|---|
| Posts held | 15 (20 July 2026 – 18 August 2026) |
| Views total | 2,640 |
| Reactions total | 65 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 11:55 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.
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.
192 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 60 | 31.3% | |
| custom 5219983464920555642 | 52 | 27.1% | |
| custom 5219679742013248718 | 45 | 23.4% | |
| custom 5219843663735070626 | 35 | 18.2% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 14 of the 15 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 209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 20 July 2026 to 18 August 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mtsai. 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 15 most recent posts we hold for this entry, published 20 July 2026 to 18 August 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.
⚡ Через час начинаем вебинар «С чего начать стратегию защиты корпоративного ИИ: паспорт ИИ-системы» ⚡ Последняя возможность успеть зарегистрироваться 🗒
❤2
ИИ должен быть доступен каждому ❤️ Вместе с МТС запускаем «Каждый включен» — бесплатную онлайн-программу для людей с инвалидностью и особенностями здоровья, которые хотят освоить ИИ с нуля и применять его в работе. За семь недель участники научатся: ✅ искать и анализировать информацию с помощью ИИ; ✅ работать с текстами и коммуникациями; ✅ создавать визуальный контент; ✅ автоматизировать рабочие задачи; ✅ использов…
❤10custom 52196797420132487184custom 52199834649205556424
⚡️ Уже завтра ⚡️ MWS AI и НИУ ВШЭ проведут открытую лекцию о безопасности корпоративного ИИ. Поговорим о том, как оценивать риски, считать последствия инцидентов и с чего начинать стратегию защиты. Регистрация 🗒
custom 52199834649205556424custom 52198436637350706262custom 52196797420132487181
Сначала автоматизируешь свою работу с помощью ИИ, а потом превращаешь этот опыт в продукт для других ⚡️ Так Арина Аймалетдинова перешла из продуктового маркетинга в продукт и теперь отвечает за копилот для маркетологов в MWS AI. За полторы минуты она рассказала о переходе в новую роль, о навыках, которые нужны новоиспечённому продуктологу, и о том, где в работе уже сложно обойтись без ИИ. А сколько своей работы вы…
custom 521998346492055564215❤10custom 52198436637350706267custom 52196797420132487186
4 «слона» безопасности ИИ в бизнесе 🛡 Когда ИИ-система выходит в прод и получает доступ к корпоративным данным, защищать приходится уже не только модель. Риски возникают в данных, промптах, интеграциях, действиях агентов и решениях на их основе. Одним фильтром или регламентом весь контур не закрыть, поэтому стратегия безопасности ИИ строится на четырёх опорах: ✅ карта рисков; ✅ архитектура защиты; ✅ процессы и роли…
❤2custom 52198436637350706261custom 52199834649205556421
ИИ-агенты изменят десятки существующих профессий? 👀 58% участников исследования Microsoft Work Trend Index 2026 уже выполняют с помощью нейросетей задачи, с которыми не смогли бы справиться год назад. При этом только 26% отмечают, что руководство объясняет, какую роль ИИ должен играть в работе компании и как будут меняться обязанности сотрудников. Главным вопросом для бизнеса сейчас становится то, кто будет выстраи…
❤6custom 52199834649205556423custom 52198436637350706262custom 52196797420132487181
В этом году снова встречаемся на True Tech Champ! В новом сезоне крупнейшего ИТ-чемпионата России на одной площадке встретятся сильнейшие разработчики, студенты и школьники со всей страны. Тебя снова ждут уникальные задачи, которых не встретишь на учёбе, и нетворкинг с коллегами разных уровней в МТС Live Холле. Выбирай свой трек: Алгоритмический трек Решай задачи, соревнуйся с лучшими и поднимайся в рейтинге. Пр…
❤4custom 52198436637350706262custom 52199834649205556421
MWS AI pinned a photo
Доверили ИИ данные, но можно ли доверять самому ИИ? Чтобы ответ на этот вопрос не пришлось искать уже после инцидента, 18 августа проведём первую открытую лекцию программы «Стратегия безопасности искусственного интеллекта» от Центра ИИ-трансформации MWS AI и НИУ ВШЭ. В программе: ✅ покажем свежую статистику по утечкам через ИИ и объясним, почему полный запрет нейросетей не решает проблему; ✅ разберём, из чего сост…
custom 52199834649205556425❤4custom 52198436637350706261
Как ИИ ускоряет одни разработки и сам зависит от других 🤖 Всемирный экономический форум совместно с научным издательством Frontiers опубликовал ежегодный список технологий, которые выходят за рамки фундаментальных исследований и приближаются к практическому применению. В этом году при подготовке доклада эксперты впервые использовали ИИ-инструменты для анализа тысяч научных публикаций и отраслевых материалов, после …
❤6custom 52196797420132487184custom 52198436637350706263
Почему мы сделали Cotype компактнее? 🤖 Продолжаем серию экспертных постов о технологиях, которые стоят за нашими продуктами. Последние несколько лет индустрия жила по одному правилу: чем больше параметров у модели, тем она умнее, и каждое следующее поколение LLM «наращивало веса». Но у такого пути развития есть потолок — даже два: технический и экономический. Недавно мы выпустили Cotype PRO 3 и Cotype LIGHT 3 — 27…
custom 52199834649205556425custom 52196797420132487184❤2
Рынок больше не ищет просто специалистов по ИБ? 👀 Мы решили разобраться, как ИИ меняет рынок труда в информационной безопасности, и изучили свежие исследования и отраслевые обзоры. Собрали главное 🗒 74% компаний уже перестроили команды информационной безопасности из-за внедрения ИИ. Рутинная аналитика всё чаще автоматизируется, а спрос смещается к специалистам, способным защищать ИИ-системы, управлять связанными с…
❤8custom 52196797420132487186custom 52198436637350706265
Showing the 12 most recent of 15 posts we hold for @mtsai. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 10 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“MWS AI” (@mtsai), 7,149 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mtsai.
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.