Telegram RegisterThe public register of Telegram

Channel

Дело в HR | Про людей и бизнес

@fromYazi

On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry

9,901subscribers

-35 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-1001226049424
TypeChannel
Username@fromYazi
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/fromYazi

Growth

9,9019,9369,918.57 August 2026 — 9,936 subscribers7 August 2026 — 9,935 subscribers10 August 2026 — 9,913 subscribers13 August 2026 — 9,901 subscribers7 August 202613 August 2026
4 measurements spanning 7 days, net -35. 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 9,896–9,941 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:399,901-12
10 Aug 2026, 05:249,913-22
7 Aug 2026, 06:129,935-1
7 Aug 2026, 01:019,936first reading

Engagement

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

ERR · 30 days
5.18%
avg views ÷ 9,901 subscribers
Avg views / post
513
17 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
17
of 19 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 13 of 17 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 12 August 2026
Posts held19 (14 July 202612 August 2026)
Views total8,720
Reactions total109
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 05:34 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

133 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5642.1%
4533.8%
😁129.02%
🦄75.26%
👍43.01%
🌚32.26%
😎32.26%
😢21.50%
🎉10.752%

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

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

Advertising

Ad load
5.26%
1 of 19 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
472
over 1 measured post
Median views · rest
505
over 18 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjeJYFA316 August 20266 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 19 most recent posts we hold, published 14 July 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

11 Aug 2026, 15:08 UTC255 views1 reactionsread 13 August 2026
Photo

Эксперт курса — директор по персоналу в POLAIR* Михаил Барков уже более 16 лет в предпринимательстве и управлении ресурсами. За это время успел возглавить следующие должности: 🔵 бизнес-партнер ИТ-подразделения «АвтоВАЗ»; 🔵 советник директора «Жигулевской долины» — технопарка в сфере высоких технологий; 🔵 организатор, модератор и спикер индустриальных и IT-конференций. В 2020 году Михаил стал победителем в номинаци

🔥1

10 Aug 2026, 16:00 UTC341 views3 reactionsread 13 August 2026
Photo

😀 Новый курс по HRBP — встречайте! Для кого: Для сильных эйчаров, которые устали тушить пожары и разгребать последствия чужих решений. Чему научитесь за 6 недель: ✔️ Понимать бизнес. ✔️ Говорить с CEO на одном языке. ✔️ Работать с HR-аналитикой и считать ROI инициатив. ✔️ Строить HR-стратегию. ✔️ Влиять на руководителей и проводить изменения. Программу модулей смотрите в карточках 💙 📌 Стоимость обучения — от 59 0

🎉1🔥1😎1

9 Aug 2026, 15:18 UTC415 views5 reactionsread 13 August 2026

Помните историю, где CEO заявил, что уволил весь HR-отдел и «проблемы исчезли»? Самое интересное в ней даже не увольнение. Беда в том, насколько легко руководитель смог сделать HR виноватым! Почему? Ценность HR не была очевидна для бизнеса. Всё до банального просто: CEO не понимает, как HR влияет на прибыль, скорость роста, удержание сотрудников и эффективность команды ↔️ HR превращается в первую статью расходов.

5

8 Aug 2026, 08:11 UTC440 views7 reactionsread 13 August 2026
Photo

Не все знают, но роль HR в компании определяется не названием должности, а уровнем влияния. Как должно быть в идеале, показали в карточках. 💻 Теперь давайте эксперимент: 🔵 напишите, какая у вас должность 🔵 в какой вы точке сейчас фактически — задача, функция, влияние 🔵 куда хотите прийти

4🌚2👍1

7 Aug 2026, 07:20 UTC489 views13 reactionsread 13 August 2026

Самая большая ошибка HR — всегда соглашаться «тушить пожары» Иногда это даже льстит: без меня ж не справятся! Но есть нюанс (как всегда 😁) Если собственник, CEO или руководители подразделений приходят к вам только со словами «Срочно!» — скорее всего, тушить уже поздно :))) Остается разгребать последствия. Уволился ключевой сотрудник? Команда выгорела? Снова сорвался наём — и всё это вам? Поздравляю! Вы аварийная

🔥12😎1

6 Aug 2026, 12:04 UTC472 viewsread 13 August 2026
Advertisementerid 2SDnjeJYFA3Photo

Понимаете, что уже переросли свои задачи и хотите карьерного роста? 📆 11 августа в 14:00 по МСК на бесплатном вебинаре "Как стать руководителем отдела обучения: стратегия и действия" вы узнаете, как оценить свои карьерные перспективы и выстроить кратчайший путь к должности руководителя отдела обучения. А ещё — поймёте, как подготовиться к собеседованию, чтобы впечатлить топ-менеджмент. В программе вебинара: ⚫️ разб

6 Aug 2026, 04:32 UTC437 views2 reactionsread 13 August 2026
Photo

Что общего между предпринимателем и HRBP? Кажется, что это разные миры. Один рискует своими деньгами. Другой сидит в найме и согласовывает офферы. Но если приглядеться — точки пересечения серьезные. 1. Оба живут в неопределённости Батлер в своём исследовании пишет: предприниматели не обязательно любят риск. Им просто комфортнее, чем другим, когда непонятно, что будет дальше. HRBP — то же самое. Бизнес меняет стра

1🔥1

5 Aug 2026, 03:34 UTC527 viewsread 13 August 2026
Photo

4 главные статьи, которые нужно прочитать начинающим и продвинутым HRBP Сколько платят HRBP в 2026: разбор рынка Как стать HRBP в 2026 году: путь к влиянию на бизнес-решения Метрики HRBP: что и зачем считать, чтобы бизнес вас слышал Чем HR Business Partner отличается от HR-менеджера и HR-директора в 2026 году 17 августа мы стартуем 1-ый поток обучающей программы Бизнес-партнер (HRBP) нового поколения. Здесь можн

3 Aug 2026, 03:44 UTC671 views22 reactionsread 12 August 2026
Photo

Рынок найма сошел с ума. Еще пару лет назад все было понятно: разместил вакансию, отобрал резюме, провел собеседование — нанял. Сегодня те же шаги дают ноль. Сильные кандидаты пропадают на финальном этапе. Классные специалисты уходят к конкурентам за день. Вакансии месяцами не закрываются, а те, кого все же наняли, — не проходят испытательный срок. Дело в том, что рынок изменился, а методы найма — нет. Два года

🔥163🦄3

29 Jul 2026, 04:39 UTC749 views14 reactionsread 10 August 2026
Photo

👀 Скоро расскажем об обучающей программе, который готовили несколько месяцев. Узнаваемая ситуация: тебя зовут в кабинет руководителя по двум поводам: "нужно уволить" и "срочно найдите мне человека". А когда приходишь со своей инициативой — вежливо кивают и... ничего не происходит. Через пару дней покажем, что с этим делать 😉 Что обычно происходит с вашими HR-инициативами у руководства? 🔥 Слушают и внедряют 🦄Слушаю

🔥12🌚1🦄1

Showing the 12 most recent of 19 posts we hold for @fromYazi. 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 — 19,160 of 1,345,403entries 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

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.

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.

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

“Дело в HR | Про людей и бизнес” (@fromYazi), 9,901 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/fromYazi.

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.