Telegram RegisterThe public register of Telegram
Telegram profile photo for Стартап-лаборатория

Channel

Стартап-лаборатория

@vzlomannye_igry

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

6,961subscribers

-979 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001106784314
TypeChannel
Username@vzlomannye_igry
DescriptionСоздание и развитие продуктов/стартапов, поиск ценности и роста, управление командами и привлечение инвестиций. Без излишней информации, рекламы и ненужных подробностей.
CreatedBetween 1 February 2017 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/vzlomannye_igry

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

10,900 average views per post against 6,961 subscribers — an engagement rate of 157.2%. Across the 14,882 registered channels in the same cohort — 3,248–9,999 subscribers, posting mainly in Russian — the middle half sit between 6.95% and 25.4%, with a median of 13.7%.

What this was computed from
Window30 days (5 October 2026 – 4 November 2026)
Posts measured11 of 11 published in the window (0 exact, 11 rounded by Telegram)
Views totalled120,360
Mature posts only157.2% over 11 posts read at least 24h after publication
Subscribers6,961 measured 3 November 2026
Cohortb3162:rus · 14,882 channels · p10 3.58% · p25 6.95% · p50 13.7% · p75 25.4% · p90 41.6%
Position in cohort99.792th percentile · 11.5× the cohort median
Uncertainty±0.083% of the figure, from Telegram’s rounding
Post languageRussian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 4 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

6,9617,9407,450.57 August 2026 — 7,940 subscribers7 August 2026 — 7,940 subscribers7 August 2026 — 7,937 subscribers10 August 2026 — 7,916 subscribers14 August 2026 — 7,872 subscribers17 August 2026 — 7,842 subscribers20 August 2026 — 7,821 subscribers24 August 2026 — 7,796 subscribers27 August 2026 — 7,770 subscribers30 August 2026 — 7,749 subscribers2 September 2026 — 7,734 subscribers6 September 2026 — 7,687 subscribers11 September 2026 — 7,652 subscribers15 September 2026 — 7,632 subscribers19 September 2026 — 7,611 subscribers29 September 2026 — 7,517 subscribers6 October 2026 — 7,376 subscribers13 October 2026 — 7,254 subscribers15 October 2026 — 7,217 subscribers18 October 2026 — 7,201 subscribers21 October 2026 — 7,180 subscribers24 October 2026 — 7,135 subscribers27 October 2026 — 7,110 subscribers31 October 2026 — 7,031 subscribers3 November 2026 — 6,961 subscribers7 August 20263 November 2026
25 measurements spanning 88 days, net -979. 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 6,814–8,087 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
3 Nov 2026, 00:216,961-70
31 Oct 2026, 06:367,031-79
27 Oct 2026, 23:067,110-25
24 Oct 2026, 15:487,135-45
21 Oct 2026, 19:497,180-21
18 Oct 2026, 23:447,201-16
15 Oct 2026, 18:187,217-37
13 Oct 2026, 03:507,254-122
6 Oct 2026, 11:157,376-141
29 Sept 2026, 13:597,517-94
19 Sept 2026, 16:377,611-21
15 Sept 2026, 03:407,632-20
11 Sept 2026, 05:567,652-35
6 Sept 2026, 14:397,687-47
2 Sept 2026, 03:587,734-15
30 Aug 2026, 07:137,749-21
27 Aug 2026, 13:257,770-26
24 Aug 2026, 11:177,796-25
20 Aug 2026, 22:357,821-21
17 Aug 2026, 16:177,842first reading

Engagement

51 posts held, back to 23 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 21 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
157.2%
avg views ÷ 6,961 subscribers
Avg views / post
10,900
11 posts measured
Reaction rate
2.31%
reactions ÷ views · ER floor
Posts in window
11
of 51 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 6 of 11 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 2 November 2026
Posts held51 (23 June 2026 – 2 November 2026)
Views total120,360
Reactions total1,456
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 14:00 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,320
Videos
≈17
Links
≈88

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

14,072 reactions across 45 posts, in 10 distinct kinds. The most used accounts for 19.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉2,78119.8%
🔥2,74919.5%
❤‍🔥2,40017.1%
💯2,40017.1%
🥰2,35616.7%
👍4743.37%
😁4473.18%
❤4313.06%
💋210.149%
👏130.092%

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

Measured over the 51 most recent posts we hold, published 23 June 2026 to 2 November 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

Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

2 Nov 2026, 05:44 UTC≈9,820 viewsread 4 November 2026
Photo

Пятничная чистка бэклога за 30 минут Задачи, висящие дольше недели, сами не оживают. Они тянут внимание команды и ломают планирование спринта. Получасовой ритуал в пятницу возвращает бэклогу честность. Как это работает. Берём всё, что старше 7 дней, и по каждой задаче называем одну причину застоя из трёх: нет владельца, нет входных данных, нет приоритета. Третьего не дано, иначе разбор утонет в обсуждении. Действи…

28 Oct 2026, 09:16 UTC≈12,500 viewsread 4 November 2026
Photo

7 стоп-слов интервьюера: как не испортить разговор с клиентом Типичная ошибка проблемного интервью: фаундер идёт проверять гипотезу, а за 20 минут её же подтверждает. Не потому что она верна, а потому что вопросы наводящие. Собеседник вежливо кивнул - команда ушла строить продукт на пустом фундаменте. Остановитесь, если услышали в своей речи: - «А вы бы…»: проекция, а не поведение. - «Представьте, что…»: фантазия …

27 Oct 2026, 11:19 UTC≈11,400 viewsread 4 November 2026
Photo

BANT за 15 минут: как отсеять пустой пилот на первом звонке Фаундер созванивается с операционным директором сети. Тот кивает, просит «прислать презентацию и обсудить пилот». Через месяц сделка умирает: бюджета не было, решение принимал не он. Чтобы не повторять, в первый час хватает 7 открытых вопросов: - Что пытались закрыть до нас и почему не вышло - Что будет, если оставить как есть - Кто ещё должен сказать «да…

26 Oct 2026, 08:53 UTC≈13,000 viewsread 4 November 2026
Photo

Личный AI-стек фаундера: универсальный помощник против узкого набора Фаундер теряет до дня в неделю на почту, созвоны, ресёрч и черновики. Есть два способа вернуть эти часы. Вариант 1. Универсальный ассистент (ChatGPT и аналоги) закрывает всё: входящие, саммари звонков, ресёрч, подготовку к встречам, черновики писем и договоров. ▪️ Кому: команда до 10 человек, процессы меняются. ▪️ Риски: ручной перенос данных, уте…

24 Oct 2026, 06:01 UTC≈10,600 viewsread 4 November 2026
Photo

Карта автоматизации на 1 листе: 10 минут на решение Автоматизация часто начинается с подписки на дорогую платформу, а заканчивается тем, что ею пользуется один человек. Прогоните задачу через четыре вопроса. Частота. Реже раза в неделю - руками. 2-3 раза - no-code. Ежедневно и в потоке - скрипт или API. Стоимость ошибки. Сбой стоит клиента, денег или штрафа - нужен скрипт с логами и тестами. Потери до 10 минут пра…

23 Oct 2026, 04:55 UTC≈11,300 views3 reactionsread 4 November 2026
Photo

OpenAI готовит раунд на 30 млрд при оценке 1,25 трлн перед IPO. Для фаундеров это повод пересобрать свой терминшит: верхушка задирает ожидания и у ваших инвесторов. Два подхода к раунду сейчас. ▪️ Идти за оценкой. Нарратив - рынок AI и темпы роста, просите максимум по мультипликатору. Условие: подтверждённая выручка, короткий цикл сделки, сильный лид. Риск - down-round через 12-18 месяцев и жёсткая ликвидационная п…

👍1🔥1😁1

21 Oct 2026, 08:39 UTC≈9,940 views397 reactionsread 4 November 2026
Photo

Один вход для задач: жёсткая форма против живого хаба Когда команда растёт, задачи сыплются из почты, чатов и коридоров. Способов свести их в одну очередь по сути два. Подход 1. Жёсткая форма приёма. Задача заводится только через форму: автор, заказчик, срок, приоритет, контекст. Устную просьбу переносит тот, кто услышал. Когда: процессов много, цена ошибки высокая, команда от 15 человек. Риск: сопротивление, задач…

🥰91🎉85❤‍🔥81🔥71💯69

14 Oct 2026, 04:51 UTC≈10,400 views260 reactionsread 4 November 2026
Photo

Реферал за лид против реферала за оплату Партнерка ломается в одной точке: вы платите за контакт, а не за выручку. Партнер гонит объем, менеджеры разгребают любопытных, конверсия в оплату падает. Оплата за лид работает, когда продукт массовый, цикл сделки короткий, а квалификация дешевая. Иначе база засоряется, CAC растет. Процент от выручки с удержанием 3 месяца меняет логику: вознаграждение идет после второго-тр…

🔥60❤‍🔥57🎉57💯46🥰40

10 Oct 2026, 05:43 UTC≈10,500 views311 reactionsread 4 November 2026
Photo

Таблица против CRM: как фаундеру вести 20 B2B-сделок без продажников На ранней стадии воронку сразу тащат в CRM. Порядок есть, но недели уходят на поля и отчёты, которые некому читать. Альтернатива - таблица из пяти колонок: контакт, квалификация, демо, пилот, контракт. Плюс дата следующего шага и короткий комментарий. Утром сортируете по дате - видите, кому писать сегодня. Таблица тянет, пока: ▪️ до 20-30 активны…

🎉71🔥66❤‍🔥60💯60🥰54

7 Oct 2026, 08:11 UTC≈10,500 views271 reactionsread 4 November 2026
Photo

Пилот AI на троих за 4 недели: как вырастить спрос снизу Внедрение AI сверху упирается в тихий саботаж: люди защищают задачи и роли. Рабочий обход - узкий пилот на добровольцах, итоги которого видит вся компания. Четыре условия старта: ▪️ Состав. Трое добровольцев, каждый называет 2-3 рутинные задачи под AI. Нет желающих - нет пилота. ▪️ База. До старта зафиксируйте часы на этих задачах за неделю. Цифра в таблице…

🎉65🥰57❤‍🔥56🔥52💯41

6 Oct 2026, 11:44 UTC≈10,400 views214 reactionsread 4 November 2026
Photo

Weekly-синк на одной странице: 25 минут вместо часа Часовой созвон превращается в «как дела» и не оставляет следа. Одностраничный регламент из 4 блоков сокращает встречу и даёт готовый протокол. Контекст: продуктовая команда из 8 человек, понедельничный созвон стабильно растягивался до 70 минут - половина времени на пересказ задач из трекера. Решение: один документ, 4 блока строго по порядку. ▪️ Цели недели: 3-5 …

🥰46🔥44💯43❤‍🔥41🎉40

5 Oct 2026, 04:53 UTC≈10,400 views358 reactionsread 4 November 2026
Photo

Команда 12 человек, выручка растёт, фаундер впервые за полгода уходит в отпуск. Возвращается: двое кандидатов отказались из-за затянутого найма, релиз чинили в выходные, крупный клиент не получил счёт вовремя. Развилка. Стратегия 1. Закрывать дыры по мере появления. Риск: к 20 людям хаос станет культурой, и менять придётся привычки. Стратегия 2. До найма 15-го сотрудника зафиксировать 5 процессов, каждый на одну с…

💯85🥰74🔥73❤‍🔥69🎉55👍1👏1

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

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

“Стартап-лаборатория” (@vzlomannye_igry), 6,961 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/vzlomannye_igry.

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.