Telegram RegisterThe public register of Telegram

Channel

ProductSense

@productsense

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

16,463subscribers

-12 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-1001352006634
TypeChannel
Username@productsense
DescriptionДелаем ProductSense — ежегодную конференцию по менеджменту продуктов https://productsense.io/ Ведем подкаст @mspodcast РКН https://clck.ru/3ML3ms Поддержка @ps24supportbot Чат https://t.me/+yJg2crvG4ZI2YjMy Блог https://sense23.com/ Без рекламы
Created24 January 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 13 August 2026
On Telegramt.me/productsense

Growth

16,45916,47816,468.56 August 2026 — 16,475 subscribers6 August 2026 — 16,477 subscribers7 August 2026 — 16,478 subscribers8 August 2026 — 16,477 subscribers9 August 2026 — 16,469 subscribers11 August 2026 — 16,459 subscribers12 August 2026 — 16,463 subscribers16,4636 August 202612 August 2026
7 measurements spanning 6 days, net -12. 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 16,456–16,481 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:3216,463+4
11 Aug 2026, 00:2316,459-10
9 Aug 2026, 21:5116,469-8
8 Aug 2026, 20:5216,477-1
7 Aug 2026, 22:1416,478+1
6 Aug 2026, 22:2716,477+2
6 Aug 2026, 05:1716,475first reading

Engagement

17 posts held, back to 9 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.89%
avg views ÷ 16,463 subscribers
Avg views / post
1,300
13 posts measured
Reaction rate
0.492%
reactions ÷ views · ER floor
Posts in window
14
of 17 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. It is computed over the 11 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held17 (9 July 202611 August 2026)
Views total16,894
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00: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.

What this channel posts

Photos
1,230
Videos
31
Links
1,510

Lifetime counters from Telegram’s own channel header, read 13 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.

Reaction mix

87 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 59.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5259.8%
🔥2326.4%
👍1213.8%

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

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

Recent posts

11 Aug 2026, 15:26 UTC655 views1 reactionsread 13 August 2026
Photo

🔥 Деловые и иммерсивные игры на ProductSense’26 Слушать доклады про кейсы других — значит расширять свой кругозор, а участвовать в мастер-классах — значит приобретать собственный опыт и навыки ✌ На ProductSense’26 в этом году мы удвоили количество мастер-классов, а часть из них пройдет в формате деловых игр. Участники будут разбирать роли, принимать решения и видеть живые последствия каждого хода. Такой формат помог

🔥1

10 Aug 2026, 07:30 UTC854 views12 reactionsread 13 August 2026
Photo

Новые оттенки и новая глубина на ProductSense’26 Когда рынок растет, очень легко принять этот рост за собственный талант. Когда перестает — становится интереснее. Приходится заново искать, за счет чего все еще можно развиваться, что делать быстрее и дешевле, а что масштабировать. И вот настал тот самый момент, когда про рост продукта и бизнеса стоит поговорить под новым углом — в этом году на ProductSense’26 появит

6🔥5👍1

9 Aug 2026, 12:23 UTC925 views5 reactionsread 13 August 2026
Photo

За что любят конференцию ProductSense: отзывы участников прошлого года Осталось чуть больше месяца до ProductSense’26 — программа уже практически готова, работаем над созданием атмосферы. Решили заглянуть еще раз в архивы прошлого года — и чуть не прослезились от ностальгии, как же было насыщенно и ярко 😍 Постараемся в этом году сделать конференцию не менее полезной и вдохновляющей! А пока хочется поделиться кусочка

3👍2

4 Aug 2026, 17:28 UTC≈1,380 views11 reactionsread 13 August 2026

Как увидеть P&L за продуктовыми метриками: 8 вопросов для продакта Продуктовые метрики и деньги компании часто живут в разных системах и у разных людей: конверсия и ретеншен — в одном дашборде, выручка и себестоимость — в другом. Из-за этого решение может выглядеть отлично по продуктовым показателям и одновременно ничего не менять в прибыли. Вот восемь вопросов, которые стоит задавать до и после запуска. До запуска

🔥74

30 Jul 2026, 13:02 UTC≈1,570 viewsread 13 August 2026
Photo

Цены на билеты вырастут 1 августа Успейте забронировать участие до подорожания До ProductSense’26 осталось чуть больше месяца, расписание почти готово. В этот раз будет еще больше мастер-классов — треть программы по количеству выступлений, или больше половины программы по суммарному времени 🔥 📌 Смотреть расписание → До конца июля еще можно купить билет по текущей цене, а с 1 августа стоимость повысится: 🔵 «Лично»

30 Jul 2026, 07:28 UTC≈1,410 views8 reactionsread 13 August 2026

5 финансовых ошибок продакта, которые вредят бизнесу Умение видеть взаимосвязи между отдельными продуктовыми решениями и экономикой всего бизнеса все чаще звучит как база для менеджера продуктов. Но даже опытные команды все еще продолжают проходить похожие сценарии: радуются росту конверсии, удержания или числа активных пользователей — а через несколько месяцев обнаруживают, что прибыль почти не выросла или даже упа

8

25 Jul 2026, 11:15 UTC≈1,620 views6 reactionsread 13 August 2026

Сильная команда — еще не гарантия результата. Три убеждения, которые стоит пересмотреть Кажется, что если собрать опытную команду, все остальное сложится само собой. Но большинство сложных проектов не доводятся до результата не потому, что в них работают слабые специалисты. Часто это происходит потому, что между сильными специалистами плохо выстроено взаимодействие. На практике именно на стыках и появляются самые до

👍3🔥3

22 Jul 2026, 16:03 UTC≈1,360 views9 reactionsread 10 August 2026

Как делать взрывной рост в продуктах в ближайшие 10 лет: практики нейромаркетинга По мотивам доклада Сергея Паращенко на ProductSense'25 Последние 10 лет менеджеры продуктов растили метрики воронки (CAC, конверсии, CTR, ретеншн, активация, средний чек), но, вспоминая известную мысль о том, что «точки роста находятся в зонах нашей некомпетентности», стоит задать себе вопрос: а куда мы вообще не смотрим? Ответ — на по

9

21 Jul 2026, 15:01 UTC≈1,270 views1 reactionsread 10 August 2026

Опубликовали расписание ProductSense’26. Самое время выбрать доклады и зафиксировать стоимость билета 🏃 На сайте уже доступна программа конференции. Можно посмотреть, какие темы вошли в расписание, изучить состав спикеров и заранее отметить выступления, которые не хочется пропустить. В этом году вас ждут три тематических трека, 40+ докладов и 20+ мастер-классов — от стратегии и управления продуктом до исследований,

👍1

20 Jul 2026, 14:01 UTC≈1,100 viewsread 10 August 2026

Telegram обновился. Мы тоже. Думаем, вы заметили, что Telegram недавно добавил новые функции, а мы совсем недавно запустили Академию ProductSense. Решили совместить приятное с полезным: предлагаем вам обновить Telegram, чтобы узнать ответы на часто задаваемые вопросы про Академию ProductSense👇

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

Citation-graph rank

Citation-graph rank — 163,173 of 1,169,250entries 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 4 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.

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.

“ProductSense” (@productsense), 16,463 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/productsense.

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.