4 measurements spanning 7 days, net +14. 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 7,143–7,168 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 03:45
7,165
+19
11 Aug 2026, 03:11
7,146
-6
8 Aug 2026, 09:02
7,152
+1
7 Aug 2026, 10:46
7,151
first reading
Engagement
19 posts held, back to 20 June 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 10 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
8.90%
avg views ÷ 7,165 subscribers
Avg views / post
638
7 posts measured
Reaction rate
2.78%
reactions ÷ views · ER floor
Posts in window
7
of 19 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
Window
Rolling 30 days · latest post in window 11 August 2026
Posts held
19 (20 June 2026 – 11 August 2026)
Views total
4,465
Reactions total
124
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 02:20 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
365 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 27.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
100
27.4%
👍
97
26.6%
❤
88
24.1%
😁
39
10.7%
👏
12
3.29%
🏆
10
2.74%
🤩
7
1.92%
🤝
6
1.64%
❤🔥
2
0.548%
🥰
2
0.548%
🐳
1
0.274%
🙏
1
0.274%
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 19 of the 19 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 365reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 20 June 2026 to 11 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
2
across the posts below
Posts paid on
2
of 19 we hold a reading for · 11%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @prologinov. 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 19 most recent posts we hold for this entry, published 20 June 2026 to 11 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.
Как получить разрешение от РКН на использование VPN для компании 😎
Как и у большинства IT-компаний после 22 года у нас появился свой VPN, чтобы оставаться на связи, работать с зарубежными партнерами и сервисами.
К слову, сейчас с нейронками развернуть впн — вопрос 1 часа для любого человека, а для разработчика вообще раз плюнуть. Публиковать тут инструкции не буду, их много в интернете на любой вкус и цвет (а так же…
😎 Расскажу про продвижение в нейронках на Форуме "Клуба Строителей"
Воронеж, 13 августа.
Клиенты все чаще ищут подрядчиков не в Яндексе, не в Гугле, а спрашивают у чата GPT и у Алисы. И вопрос один: кого нейросеть порекомендует, вас или вашего конкурента?
13 августа я выступаю на открытии представительства "Клуба Строителей" в Воронеже, и расскажу, как вашему бизнесу попасть в ответы нейросетей и как получать оттуд…
А вас раздражает, когда человек вам отвечает, копируя ответ из нейронки?
Кажется, это новый тренд в общении в мессенджерах и соцсетках. Бесит, как раньше бесили голосовушки.
Но если голосовое хотя бы содержит реальные мысли собеседника, и ты смиряешься (или нет) с его «эээ и ммм», то в ответ нейронки зачастую еще надо сильно вдумываться — что сказать-то хотел? Люди копируют, не редактируя, типа, сам разберешься. А …
Что нужно знать, чтобы оцифровать Воронку продаж предприятия?
Как сделать контролируемым весь путь клиента от первого контакта до момента покупки и последующих допродаж?
📖 Делюсь полезным списком литературы с коментариями
Основная методология — теория ограничений Элияху Голдратта.
📎 Книга «Цель. Процесс непрерывного совершенствования» обязательна к прочтению любому предпринимателю.
Найти ограничение; Выжать максиму…
Ура, снова разыгрываем Макбук за подписку!
Подписаться на канал легко. Найти тот, который не захочется закрыть через неделю — уже сложнее.
Поэтому собрали подборку каналов руководителей агентств, студий и digital-команд. Без мотивационных простыней и пересказов чужих постов — только опыт, ошибки, процессы, управление, клиенты и деньги.
👉 https://t.me/addlist/mop2nxVci3UzYmUy
Мой канал тоже есть в подборке. Если и…
Я почему раньше вредный был?
Потому что договора приходилось вручную делать, или юриста/секретаря привлекать, и долго им объяснять, что я хотел бы получить в итоге.
А теперь что?
Показал нейронке, где у меня шаблоны договоров лежат. Завел проект с базовыми правилами. Разочек ей подробно пообъяснял, как изменения вносить, что форматирование нельзя менять, и как приложения к договорам у меня работают, какие варианты …
Да что ты будешь делать! Опять перенесли дедлайн.
Все выходные (в отпуске, между прочим!) сидел и рефакторил свои проекты с Fable 5, т.к. ее грозились отключить сегодня (12 июля) для всех и продавать только за тыщи баксов по API... и ее вновь продлили. Уже третий раз.
Кто не знает, FABLE 5 — это самая топовая модель в Claude, которая очень хорошо, практически с первого раза, создает проекты и решает сложные задачи…
И такие отзывы я люблю 😎
После очередного выступления перед предпринимателями, пришел за обратной связью к организаторам... и, оказывается, что это было лучшее мероприятие в июне. Чертовски приятно! 💖
Кому рассказать про Продвижение в нейросетях (GEO/AEO/SEO), приглашайте онлайн или офлайн!
—
😎 Логинов Про
🌟 Бустануть канал | Подписаться в MAX
📁 Подборка материалов для продвижения в нейросетях
2 июля мы совместно с IMEXPERT провели вебинар «AI-поиск, GEO, экспертный контент и сайт для производителей».
Я рассказал про то, как продвигать производственные компании в нейросетях:
▶️ Запись моего выступления про нейросети и доклады коллег про экспертный контент можно посмотреть по ссылке.
Материалов про GEO у меня получилось гораздо больше, чем влезало в д…
Вот такие отзывы я люблю! 😎
Оставлю тут для потомков прекрасный отзыв от Дины Андреевой, финансового директора компании "Спасилен", для которой мы провели аудит сайта и всех рекламных каналов.
Эта услуга у нас называется "Маркетинговый чек-ап", и вы можете заказать себе такой же, просто написав мне в личку @login_4rome.
🔥 Уже в первый месяц после нашего аудита Спасилен стали экономить 1 миллион бюджета на рекламу…
Showing the 12 most recent of 19 posts we hold for @prologinov. 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 — 25,189 of 1,481,243entries 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Логинов Про” (@prologinov), 7,165 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/prologinov.
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.