Telegram RegisterThe public register of Telegram
Telegram profile photo for Как Олег свой продукт запускал

Channel

Как Олег свой продукт запускал

@o_bukhtiyar

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

1,426subscribers

+3 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-1001131475185
TypeChannel
Username@o_bukhtiyar
CreatedBetween 1 June 2017 and 30 September 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/o_bukhtiyar

Growth

1,4231,4261,424.56 August 2026 — 1,423 subscribers6 August 2026 — 1,423 subscribers12 August 2026 — 1,425 subscribers16 August 2026 — 1,426 subscribers6 August 202616 August 2026
4 measurements spanning 10 days, net +3. 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,423–1,426 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:081,426+1
12 Aug 2026, 20:481,425+2
6 Aug 2026, 21:331,423no change
6 Aug 2026, 15:061,423first reading

Engagement

16 posts held, back to 19 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
34.5%
avg views ÷ 1,426 subscribers
Avg views / post
491
16 posts measured
Reaction rate
3.00%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 14 of 16 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 6 August 2026
Posts held16 (19 July 20266 August 2026)
Views total7,861
Reactions total205
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 15:06 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

205 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 58.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12058.5%
🌭188.78%
😁178.29%
👏167.80%
🔥157.32%
👍73.41%
🏆62.93%
🤔31.46%
🤯31.46%

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

Measured over the 16 most recent posts we hold, published 19 July 2026 to 6 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

6 Aug 2026, 14:18 UTC166 views11 reactionsread 6 August 2026
Video

Велком ту зе клаб меня

10🏆1

4 Aug 2026, 18:44 UTC336 views12 reactionsread 6 August 2026
Photo

а все говорили, что этот метод работает безотказно. что ещё посоветуете? )

😁12

4 Aug 2026, 16:39 UTC354 views30 reactionsread 6 August 2026
Photo

Кайфренция 2.0 Это было офигенски. Я провёл на площадке больше 12 часов — приехал на прогон к 10, а ушёл, когда нас уже стали выгонять охранники в 11 вечера, и мы вместе с Юрой Ветровым и оставшимися пошли в соседний бар смотреть финал ЧМ. Самое прикольное — я был там со своими. С женой Аней и с Сашей, а ещё повстречал однокурсников с Британки, которых не видел сто лет. А ещё развиртуализировался со многими ребята

🌭169🏆5

31 Jul 2026, 08:40 UTC540 views16 reactionsread 6 August 2026
Photo

Получил компенсацию от судьбы Меня не позвали на Product Fest, но я каким-то образом умудрился выиграть билеты на Айда Фест 😳 Так что сегодня буду там. Если вы тоже — рад пересечься 👋

👏16

30 Jul 2026, 09:18 UTC534 views21 reactionsread 6 August 2026

Вчера на завтраке познакомился с Настей Перельман, фаундером школы Anecole. Я далёк от образовательного бизнеса, но как же заряжает видеть, как люди смогли с нуля создать компанию с оборотом 100+ млн руб. и при этом остаются открытыми и вовлечёнными. Я опять рассказывал про свой бизнес, пытаясь на пальцах объяснить, что мы делаем (спасибо за пример с Pinterest, про который вы писали). Но Настя сразу всё поняла и н

14🤯3😁3👍1

29 Jul 2026, 16:16 UTC476 views6 reactionsread 6 August 2026

Посмотрите, как круто Макс Кукушкин подошёл к генерации макетов с помощью нейронок и MCP от Screen Gallery

🔥6

29 Jul 2026, 07:21 UTC457 views28 reactionsread 6 August 2026

Меня позвали в бизнес-клуб, или что я делал в воскресенье утром в Москва-Сити Денис Сметнёв (сооснователь Skyeng и uForce) предложил влететь в их бизнес-клуб «Твоя Опора». Недолго думая я согласился, прошёл месяц и вот на какие активности я уже успел залететь: • Пару онлайн-вебинаров (про безопасность и школу переговоров) • Парочка рандом-кофе созвонов • Офлайн-ужин с предпринимателем с крутым экзитом, где мы душе

17👍6🤔3🌭2

27 Jul 2026, 11:36 UTC467 viewsread 6 August 2026
Poll

Признавайтесь, зачем читаете

  1. Я из дизайна / продукта — польза очевидна46%
  2. Читаю ради истории, в продукт не вникаю19%
  3. Я чисто ради фоток кота5%
  4. Я мама Олега30%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

27 Jul 2026, 11:33 UTC458 views10 reactionsread 6 August 2026

Забавно, что последнее время часто рассказываю про продукт людям не из дизайна или даже не из продуктовой разработки — и они искренне изумляются, что галерея скринов вообще кому-то нужна 😅 Интересно, много ли среди вас таких )) Точно знаю, что канал читает мама — она просто меня поддерживает, независимо от сферы деятельности 🙂

8😁2

26 Jul 2026, 13:06 UTC533 views13 reactionsread 6 August 2026
Video

Поднялся в воскресенье с утра пораньше и опять оказался в Москоу сити А зачем расскажу на следующей неделе 😊 Ваши догадки как всегда принимаются )

13

23 Jul 2026, 14:22 UTC604 views10 reactionsread 6 August 2026
Photo

Залетайте на портфолио-ревью В эту субботу (25 июля) в рамках дней открытых дверей в ЦУ разберём с Сашей несколько работ в прямом эфире и поболтаем про проекты и учёбу. ➡️ Регистрация

7🔥3

22 Jul 2026, 13:03 UTC628 views13 reactionsread 6 August 2026

Дорогие продуктовые команды — вышел спец апдейт для вас. Если вы ещё не попросили своего лида организовать вам триальный доступ в Screen Gallery для всей команды — то вот вам знак 😊

13

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

27 Jul 2026, 11:36 UTCAnonymous Poll144 voters

Признавайтесь, зачем читаете

  1. Я из дизайна / продукта — польза очевидна46%
  2. Читаю ради истории, в продукт не вникаю19%
  3. Я чисто ради фоток кота5%
  4. Я мама Олега30%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 16 most recent posts we hold, published 19 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 180,371 of 1,480,975entries 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.

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.

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

“Как Олег свой продукт запускал” (@o_bukhtiyar), 1,426 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/o_bukhtiyar.

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.