Telegram RegisterThe public register of Telegram

Channel

Analyst Games in Central Asia & CIS

@analystgames

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,117subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001110664051
TypeChannel
Username@analystgames
CreatedBetween 1 February 2017 and 31 March 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/analystgames

Growth

1,1171,1181,117.56 August 2026 — 1,118 subscribers6 August 2026 — 1,118 subscribers12 August 2026 — 1,117 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net -1. 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 1,117–1,118 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:071,117-1
6 Aug 2026, 12:051,118no change
6 Aug 2026, 02:201,118first reading

Engagement

20 posts held, back to 28 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.2%
avg views ÷ 1,117 subscribers
Avg views / post
136
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 22 July 2026
Posts held20 (28 November 202522 July 2026)
Views total272
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 12:05 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.

Reaction mix

9 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
333.3%
222.2%
❤‍🔥222.2%
😱222.2%

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

Measured over the 20 most recent posts we hold, published 28 November 2025 to 22 July 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.

Recent posts

22 Jul 2026, 19:03 UTC106 viewsread 6 August 2026
Forwarded from @your_event_horizonPhoto

От VUCA к Lo-RAIT: похоже, эпоха неопределенности закончилась. Началась эпоха потери человеческой роли. 😎 Почти 40 лет менеджмент пытался описать мир с помощью разных моделей. Сначала был VUCA — мир нестабильности после холодной войны и финансовых кризисов. Затем пришел BANI, объясняющий хрупкость мира после пандемии. 🤯 Теперь исследователи и консультанты HU-X предлагают новый фреймворк — Lo-RAIT, который описывает

Signed Alex Petrov

15 Jul 2026, 10:32 UTC166 viewsread 6 August 2026

Всем привет, друзья, как ваши дела?))) 🙂 Я к вам с новым интересным мероприятием, очень интересная тема по Agentic AI! 🧠 Agentic Workflows in Practice: Building Automation with n8nПрактический часовой воркшоп, посвященный изучению и созданию агентных рабочих процессов (agentic workflows) на платформе n8n.В ходе мероприятия участники познакомятся с базовыми концепциями и вариантами развертывания n8n, пройдут практич

Signed Alex Petrov

25 Jun 2026, 16:45 UTC218 viewsread 6 August 2026
Forwarded from @your_event_horizon

Разбор статьи Уилла Маршалла (основателя Planet Labs) в The Economist «Человечество не готово к грядущему взрывному росту интеллекта». 🤖 Ключевые угрозы по мнению Маршалла: 🔜 Риск катастрофы от ИИ — 10–50% по оценкам экспертов (для АЭС — 1/1000000). 🔜 Инвестиции в ИИ в 100 раз больше Манхэттенского проекта, а расходы на безопасность — в 100 раз меньше. 🔜 Основатели ИИ-лабораторий открыто признают экзистенциальную уг

Signed Alex Petrov

19 Jun 2026, 10:02 UTC247 viewsread 6 August 2026

доброго дня всем! делимся материалами со вчерашнего вебинара: 🔹полная запись вебинара 🔹презентация

Signed Alex Petrov

2 Jun 2026, 09:15 UTC299 viewsread 6 August 2026
Forwarded from @reunicoPhoto

Вы когда-нибудь ловили себя на мысли, что BPMN-схемы в итоге остаются просто красивыми картинками в Confluence или PDF? 🧐 Процесс нарисовали. Согласовали. Положили в документацию. И… на этом всё. 📆 18 июня в 15:00 (GMT+5) проведём бесплатный вебинар для бизнес- и системных аналитиков о том, как процессы перестают быть «рисунками» и начинают реально управлять системой. Это вебинар не про теорию ради теории и не про

Signed Alex Petrov

1 Jun 2026, 10:45 UTC209 viewsread 6 August 2026
Forwarded from @ai_nomPhoto

Риски ИИ превосходят угрозу ядерного оружия Это заявление не членов Qanon, а военных и представителей международных организаций на одном из ключевых азиатских форумов по безопасности Shangri-La Dialogue в Сингапуре. Начальник обороны Нидерландов Онно Эйхелсхейм заявил: ИИ — это огромный риск с точки зрения эскалации. Но я не наивен. Его будут использовать. Его уже используют. ⬛️Параллельно с этим — заявление от с

Signed Alex Petrov

27 May 2026, 14:45 UTC225 viewsread 6 August 2026
Forwarded from @scrum_masteryPhoto

🎲 Мы приглашаем на открытую онлайн игру в мультикомандный Featureban 📅 Когда: 01.06.2026 ⏰ Время: 19:00 по МСК 📌 Мультикомандный Featureban — это бизнес-симуляция, целью которой является вскрытие вопросов и проблем межкомандной коммуникации и координации действий, когда у вас несколько команд работают над одним продуктом или портфелем проектов. Мы не просто будем играть, но и разберем: ✅ Какие стратегии помогают

Signed Alex Petrov

9 May 2026, 14:00 UTC295 views2 reactionsread 6 August 2026
Photo

✨ С Праздником Великой Победы! ✨ Фото: соцсети (гор. Фрунзе, 9 Мая 1945 года).

2

Signed Alex Petrov

7 May 2026, 12:45 UTC315 views2 reactionsread 6 August 2026
Forwarded from @edu_in_IT

📌Что такое RAG и зачем он нужен в AI-системах? Когда мы работаем с LLM, важно, чтобы модель не просто «генерировала ответ», а опиралась на актуальные и проверенные данные: документы, базы знаний, регламенты, таблицы или внутреннюю документацию компании. Для этого используется подход RAG — Retrieval-Augmented Generation. Если проще: система сначала находит релевантную информацию во внешних источниках, а затем перед

😱2

Signed Alex Petrov

12 Apr 2026, 12:00 UTC347 views3 reactionsread 6 August 2026
Photo

С праздником! ✨

❤‍🔥21

Signed Alex Petrov

1 Apr 2026, 08:31 UTC439 viewsread 6 August 2026

Анонс ценного мероприятия: Наши партнеры Camunda проводят 30-го апреля конференцию в Стамбуле Мероприятие будет полезно руководителям бизнес и ИТ подразделений, enterprise архитекторам. • Представители крупных банков и телеком компаний Турции расскажут о своих кейсах использования Camunda • Будет возможность лично познакомиться и обменяться опытом как руководителями местных компаний так и с руководством Camunda.

Signed Alex Petrov

16 Mar 2026, 02:32 UTC406 viewsread 6 August 2026

Всем доброе утро! Запись вебинара уже готова 🚀

Signed Alex Petrov

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

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.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Analyst Games in Central Asia & CIS” (@analystgames), 1,117 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/analystgames.

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.