Telegram RegisterThe public register of Telegram

Channel

ИИволюция 👾

@ai_volution

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Cite this entry

11,663subscribers

-8 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001909270971
TypeChannel
Username@ai_volution
DescriptionАвторский канал Сергея Пахандрина про AI, нейросети, AI-разработку, ChatGPT (и другие LLM). Строю AI-first компанию. Рассказываю о своём опыте и экспериментах с AI. По всем вопросам: @pakhandrin РКН: https://clck.ru/3QJLiL В ВП и папках не участвую
CreatedBetween 1 March 2023 and 30 November 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/ai_volution

Growth

11,66311,67411,668.56 August 2026 — 11,671 subscribers6 August 2026 — 11,671 subscribers6 August 2026 — 11,670 subscribers7 August 2026 — 11,674 subscribers8 August 2026 — 11,673 subscribers9 August 2026 — 11,669 subscribers10 August 2026 — 11,667 subscribers11 August 2026 — 11,663 subscribers6 August 202611 August 2026
8 measurements spanning 5 days, net -8. 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 11,661–11,676 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:2111,663-4
10 Aug 2026, 09:0111,667-2
9 Aug 2026, 10:5111,669-4
8 Aug 2026, 09:1211,673-1
7 Aug 2026, 11:1011,674+4
6 Aug 2026, 12:1011,670-1
6 Aug 2026, 02:3511,671no change
6 Aug 2026, 00:5211,671first reading

Engagement

21 posts held, back to 22 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.1%
avg views ÷ 11,663 subscribers
Avg views / post
2,930
21 posts measured
Reaction rate
1.14%
reactions ÷ views · ER floor
Posts in window
21
of 21 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 9 August 2026
Posts held21 (22 July 20269 August 2026)
Views total61,560
Reactions total701
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 13:02 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
1,010
Videos
377
Links
841

Lifetime counters from Telegram’s own channel header, read 12 August 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 28s
Average length
44s

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

701 reactions across 21 posts, in 8 distinct kinds. The most used accounts for 36.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥25936.9%
🤣24835.4%
9113.0%
👍8211.7%
🤔101.43%
😭50.713%
🍓40.571%
👾20.285%

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

Measured over the 21 most recent posts we hold, published 22 July 2026 to 9 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
4
of 21 we hold a reading for · 19%
Most on one post
2
single highest reading

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

Advertising

Ad load
4.76%
1 of 21 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
3,820
over 1 measured post
Median views · rest
2,880
over 20 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
2W5zFFz6TQD130 July 202630 July 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 21 most recent posts we hold, published 22 July 2026 to 9 August 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

9 Aug 2026, 04:54 UTC≈1,930 views20 reactionsread 12 August 2026

Когда снова сброс лимитов в Codex? Если вы всегда гадаете использовать ли накопленный сброс лимитов в Codex или дождаться, пока команда OpenAI сделает “бесплатны” массовый сброс, появился вот такой сайт, где можно узнать когда был последний сброс и хронологию, а так же получить вероятностный прогноз когда можно ожидать очередной сброс https://www.willcodexquotareset.com/

🔥155

8 Aug 2026, 12:11 UTC≈2,180 views47 reactionsread 12 August 2026
Photo

На злобу дня и всех этих сбеганий моделей от хозяина

🤣39👍6🔥2

7 Aug 2026, 13:39 UTC≈2,140 views8 reactionsread 12 August 2026

Сегодня пятница, давайте поговорим о вечном 😁 Какие книги прочитали в этом году? Какие вас удивили? На какие книги было зря потрачено время? Какие книги оставили долгое послевкусие? Любые книги. Делитесь в комментариях, очень интересно!

7👍1

5 Aug 2026, 11:33 UTC≈2,700 views36 reactions1 Starread 12 August 2026
Forwarded from @tips_aiPhoto

meat-proxy — человек который отправляет ответ ИИ вместо своей точки зрения не будьте meat-proxy 😏 @tips_ai

🔥19🤣17

5 Aug 2026, 11:33 UTC≈2,660 views10 reactionsread 12 August 2026

Кожаные мешки, мясные прокси, дальше прокладками будут называть или уже?😁 А потом вселенная схлопнется. Вы кстати грешите тем, что на любой вопрос просто пересылаете ответ из кодекса/клод кода в чат? 😁 👇

🤣10

4 Aug 2026, 11:04 UTC≈3,230 views79 reactionsread 12 August 2026
Photo

И в чем он не прав? 🤔

🤣6011🔥5👍2🤔1

4 Aug 2026, 09:01 UTC≈3,140 views26 reactionsread 12 August 2026
Video

В Yandex AI Studio стало проще понимать, почему агент «сломался» Добавили в интерфейс Yandex AI Studio возможность анализа трейсов на базе observability-платформы Monium. Трейсы — один из ключевых сигналов для observability ИИ-агентов. Они наглядно показывает всю цепочку работы агента, а в спанах хранится контекст каждого шага — то, что реально повлияло на поведение агента, включая вызовы инструментов. Для агентны

🤣18👍62

2 Aug 2026, 05:36 UTC≈3,310 views31 reactionsread 12 August 2026
Photo

– я могу навайбкодить 5 приложений за 1 день! Теперь я король! спустя месяц: – у меня 0 пользователей. Да, реальный баланс сил теперь такой: маркетинг 99%, 1% разработка.

16🤣7👍4🔥3🍓1

30 Jul 2026, 08:29 UTC≈3,820 views15 reactionsread 12 August 2026
Advertisementerid 2W5zFFz6TQDPhoto

⚡Все топовые нейросети в одном окне без оплаты зарубежными картами ⚡ Нужно внедрить ИИ в команде за часы без регистрации и смс инженеров, валютных вложений и контрактов с разными вендорами? Сделайте это в пару кликов с помощью ИИ-роутера от Selectel. Сервис дает доступ к большинству актуальных генеративных моделей с оплатой в рублях по потреблению. Чем хорош сервис? ⚡300+ ведущих ИИ-моделей от мировых вендоров; ⚡

🤔7🤣61👍1

29 Jul 2026, 07:18 UTC≈3,290 views13 reactionsread 12 August 2026

Стратегия регулярных сбросов лимитов прекрасно отражена на этом видео, в качестве напоминания)) Только в данном случае, рядом с креветкой еще и бутылочка холодного пива, только пиво для антуража, оно не для вас 😂

🤣13

29 Jul 2026, 05:43 UTC≈3,350 views27 reactionsread 12 August 2026
Photo

OpenAI сбросила лимиты всем пользователям ChatGPT Work и Codex после жалоб на то, что GPT-5.6 Sol слишком быстро их съедает. Они провели расследование и проблема оказалась в самой модели. Sol чаще продолжает работу дольше, делает больше вызовов инструментов, подключает субагентов и активнее запускает задачи параллельно. Даже при одинаковом уровне рассуждений она может тратить больше токенов, чем GPT-5.5. Особенно б

🔥186👍3

29 Jul 2026, 04:30 UTC≈2,980 views16 reactions1 Starread 12 August 2026

MCP получил одно из крупнейших обновлений с момента запуска Вышла новая версия протокола MCP 2026-07-28, через который AI-агенты подключаются к приложениям, данным и внешним инструментам. Главное изменение: MCP становится stateless. Серверу больше не нужно постоянно хранить состояние сессии. Каждый запрос теперь можно обрабатывать отдельно, поэтому MCP-серверы будет проще запускать на serverless и масштабировать по

🔥11👍32

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

Citation-graph rank

Citation-graph rank — 302,404 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 8 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.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“ИИволюция 👾” (@ai_volution), 11,663 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ai_volution.

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.