Если возникли вопросы по Июльке или регистрации – смело обращайтесь к Даниилу (@asmodey1) Всех очень ждем 17 июля! 🌞
❤1🔥1custom 53638157606804738141

Channel
@yavdele_HSE
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
353subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002391882524 |
|---|---|
| Type | Channel |
| Username | @yavdele_HSE |
| Description | Официальная группа программы "Я в деле" НИУ ВШЭ Сайт программы: https://явделе.рф Поддержка: https://t.me/Jumoresk |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/yavdele_HSE |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:47 | 353 | no change |
| 7 Aug 2026, 15:06 | 353 | first reading |
17 posts held, back to 9 December 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 28 June 2026. An engagement rate over an empty window would be a number about nothing.
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.
97 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 27.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5363815760680473814 | 27 | 27.8% | |
| ❤ | 27 | 27.8% | |
| 🔥 | 17 | 17.5% | |
| 🦄 | 10 | 10.3% | |
| ⚡ | 7 | 7.22% | |
| 😢 | 4 | 4.12% | |
| 💊 | 2 | 2.06% | |
| 🤯 | 2 | 2.06% | |
| ✍ | 1 | 1.03% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 15 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 97reactions 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 December 2025 to 28 June 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.
Если возникли вопросы по Июльке или регистрации – смело обращайтесь к Даниилу (@asmodey1) Всех очень ждем 17 июля! 🌞
❤1🔥1custom 53638157606804738141
☀️ Соскучились по Июльке? Мы тоже! В этом году вы станете частью особенной Июльки, ведь форум наставников «Я в деле» пройдёт уже в 5-й раз! В честь юбилея мы готовим много интересного: новые форматы мероприятий, любимые активности прошлых лет, партнерские локации и сюрпризы для участников. 📍 17–21 июля 2026 Поляна, с. Высоково, д. 20 ↩️ Регистрируйся до 7 июля: https://vk.cc/cYuzcc Хочешь узнать больше о форуме…
❤5⚡4custom 53638157606804738144
Напоминаем про мастер-класс сегодня. Аудитория: G108
Напоминаем про мастер-класс❗️ Ждем вас сегодня в аудитории K417
custom 53638157606804738142🦄1
Как создать первую рабочую версию продукта, чтобы проверить ценность идеи на клиентах, не тратя месяцы и миллионы. Разберёмся вместе на встрече с Максимом Чернухиным. Проектный директор Skillbox, key member рабочей группы по применению облачных технологий в финтех-секторе Ассоциации финтеха. До 2022 года работал в Альфа-Банке, где создал платформу цифровых продаж, которая успешно используется за пределами компании, …
custom 53638157606804738143❤2
Почему одни бизнесы растут, а другие застревают на месте? 🧐Часто дело не в идее, а в выбранной бизнес-модели. На этот вопрос ответим на мастер-классе и разберёмся, как устроены бизнес-модели и как они влияют на устойчивость и рост бизнеса. На встрече обсудим: ▶️ что такое бизнес-модель и зачем она нужна ▶️ какие бывают типы бизнес-моделей ▶️ какие риски в них заложены ▶️ почему важно не зацикливаться на одном спосо…
custom 53638157606804738142
Аудитория на сегодня: D511
❗️❗️❗️❗️❗️❗️❗️❗️❗️ Узнали дату проведения мастер-класса! Ждем вас 7 апреля в 18:00 на Покровском бульваре, 11 Скорее регистрируйтесь🚀
❤3✍1🤯1
❗️❗️❗️❗️❗️❗️❗️❗️❗️ Уважаемые участники, к сожалению, мы вынуждены перенести мастер-класс по CustDev. Новую дату сообщим позже Всем удачной сессии! 😊
❤6😢4💊2⚡1🦄1
Делать продукт “как чувствуешь” - долго и дорого. Разговаривать с клиентами - быстрее и честнее 26 марта проведём мастер-класс по CUSTDEV - поговорим о том, как проверять идеи и понимать, что вообще нужно людям На встрече разберём: ↗️как выходить на разговор с клиентами и не получать формальные ответы ↗️ о чём спрашивать, чтобы потом не оказалось “мы не это имели в виду” ↗️ как не переоценивать позитивный фидбек ↗️…
custom 53638157606804738145🔥1🤯1
⭐️Спасибо всем, кто был на мастер-классе по личному бренду 12 марта Разобрали личный бренд, доверие аудитории и способы монетизации через свой продукт. Отдельное спасибо Артему Бакину за ценные инсайты и опыт. ↘️Подписывайтесь на его телеграмм-канал - там много полезного. 🚀До встречи на следующих мероприятиях!
🦄6❤3
Аудитория R206 Всех ждём!
custom 53638157606804738141
Showing the 12 most recent of 17 posts we hold for @yavdele_HSE. 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 — 1,330,828 of 1,480,688entries 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.
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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“Я в деле! ВШЭ” (@yavdele_HSE), 353 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/yavdele_HSE.
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.