Таня Голубовская: инноватор, CEO «Импульс Кода» (>500 млн за 3 года).
Создатель digital-решений для EdTech, HRTech, MarCom с охватом 15+ млн и офлайн-участием 500+ тыс.
Лауреат РОТОР и Премии Рунета.
Канал о смыслах и идеях, меняющих реальность.
Created
Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
2 measurements taken within a single day. 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 147–149 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 20:31
148
no change
7 Aug 2026, 23:51
148
first reading
Engagement
8 posts held, back to 20 April 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
44.3%
avg views ÷ 148 subscribers
Avg views / post
65.5
2 posts measured
Reaction rate
31.3%
reactions ÷ views · ER floor
Posts in window
2
of 8 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 23 July 2026
Posts held
8 (20 April 2026 – 23 July 2026)
Views total
131
Reactions total
41
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 20:31 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
140
Videos
22
Links
42
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
8m 07s
Average length
4m 04s
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
130 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 36.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
47
36.2%
🔥
42
32.3%
🥰
13
10.0%
❤🔥
11
8.46%
⚡
8
6.15%
👍
3
2.31%
👏
3
2.31%
💯
1
0.769%
😘
1
0.769%
🤗
1
0.769%
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 7 of the 8 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 130reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 20 April 2026 to 23 July 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.
Масштабирование — звучит гордо! Но чем дальше точка от центра — тем больше хаоса и косяков 🫠
Причём неважно, что именно масштабировать — сеть филиалов, франшизу, логистику или клиентский сервис. Проблема всегда одна — управляемость размывается. До 70% компаний при региональном экспаншене сталкиваются с падением качества, просто потому что центральный офис узнаёт о сбоях с задержкой в недели, когда клиент уже ушёл к …
🤩 «Если в твоём поле зрения ребёнок, ты не можешь просто шагнуть в сторону, не передав контроль лично в руки»
Пока на канале была тишина, я успела слетать в мини-отпуск и отметить день рождения… прямо на лодке. Самый частый вопрос, который мне задавали до поездки: «Как?! Вы правда летите с малышом на лодку?!»
И мой самый честный ответ: всё решает подготовка и правила. Любой кайфовый опыт с ребёнком строится от внут…
2025
ХАКАТОН
ОТКРОЙ#МОСПРОМ
1 место. Лучший промышленный хакатон России.
🤍
Архитекторы смыслов и идеологи хакатонного движения в РФ - codepulse.ru
Обожаю то, как мы это делаем. Сколько лет, не теряя качество, превосходя свои же ожидания, поддерживая актуальность каждого, доводя до результата участников и партнёров.
Абсолютно заслуженная награда всей команды, и наших партнёров, экспертов, трекеров, модераторов. П…
В плотном рабочем графике, когда дни сливаются в один непрерывный поток задач, я всё чаще возвращаюсь мыслями к нашей недавней поездке на Байкал.
В этом году у мужа был юбилей (как-то внезапно мы стали старше 😁). И раз уж он из тех, у кого «есть я, а больше ничего и не надо», я решила собрать его самых давних и близких друзей и подарить ему удивительные воспоминания 🎁
Так началась операция «Зимний Байкал»: 9 месяце…
Как синхронизировать экипаж: стратсессия в формате космической миссии 🚀
Не секрет, что большинство корпоративных митапов оборачиваются для участников испытанием графиками и многочасовыми презентациями.
Можно ли это исправить? Конечно. Рассказываю на нашем кейсе.
Недавно команда «Импульса Кода» взялась за проект для крупного международного бренда. Перед нами стояла задача — провести стратсессию для 50 сотрудников и…
Наш семейный бизнес-план или СЕОмамапост о том, что спасет мой 2026 (спойлер: если откликается — жду в ЛС)
Встать в 7 утра в планку, в 8 медитативно пожарить безглютеновые сырники, а в 9 уже захватить мир — отличный сценарий для вирусных рилс. Но это настолько оторвано от реальности, что оставим такие истории в разделе «на помечтать» где-то между телепортацией и идеальным метаболизмом.
Если меня спросят про секрет …
Переезд в другой мессенджер — не техническая задача, а кризис-менеджмент отношений
Сбои в Telegram сейчас — тема номер один. Но я смотрю на проблему шире.
Вопрос не в том, упадёт ли TG окончательно или нет. Вопрос в том, останутся ли с вами клиенты, если завтра вам придется резко сменить адрес?
Как руководитель компании, в которой все продукты создаются вокруг той или иной формы коммуникаций, я выделяю три главны…
❤5🔥3🥰3
Showing the 8 most recent of 8 posts we hold for @tg_in_tg. 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.
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.
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 8 August 2026 — this
entry's latest reading, not the date you are reading this.
“Коллеги, а в чём смысл?” (@tg_in_tg), 148 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tg_in_tg.
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.