Telegram RegisterThe public register of Telegram
Telegram profile photo for Хантфлоу

Channel

Хантфлоу

@huntflow

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

15,100subscribers

+45 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001008517720
TypeChannel
Username@huntflow
Created24 December 2015measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/huntflow

Growth

15,04115,10415,072.55 August 2026 — 15,055 subscribers6 August 2026 — 15,055 subscribers6 August 2026 — 15,048 subscribers7 August 2026 — 15,041 subscribers8 August 2026 — 15,047 subscribers9 August 2026 — 15,052 subscribers10 August 2026 — 15,058 subscribers11 August 2026 — 15,057 subscribers13 August 2026 — 15,056 subscribers14 August 2026 — 15,073 subscribers15 August 2026 — 15,084 subscribers17 August 2026 — 15,092 subscribers18 August 2026 — 15,087 subscribers19 August 2026 — 15,095 subscribers20 August 2026 — 15,093 subscribers21 August 2026 — 15,095 subscribers22 August 2026 — 15,096 subscribers24 August 2026 — 15,101 subscribers25 August 2026 — 15,104 subscribers26 August 2026 — 15,102 subscribers27 August 2026 — 15,098 subscribers28 August 2026 — 15,096 subscribers29 August 2026 — 15,099 subscribers30 August 2026 — 15,095 subscribers31 August 2026 — 15,099 subscribers1 September 2026 — 15,097 subscribers2 September 2026 — 15,096 subscribers3 September 2026 — 15,092 subscribers5 September 2026 — 15,100 subscribers15,1005 August 20265 September 2026
29 measurements spanning 31 days, net +45. 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 15,032–15,113 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
5 Sept 2026, 15:5915,100+8
3 Sept 2026, 16:3815,092-4
2 Sept 2026, 08:2415,096-1
1 Sept 2026, 09:3315,097-2
31 Aug 2026, 11:0315,099+4
30 Aug 2026, 09:2715,095-4
29 Aug 2026, 08:1915,099+3
28 Aug 2026, 09:4815,096-2
27 Aug 2026, 10:3815,098-4
26 Aug 2026, 09:2815,102-2
25 Aug 2026, 06:3315,104+3
24 Aug 2026, 09:4315,101+5
22 Aug 2026, 17:2515,096+1
21 Aug 2026, 11:2615,095+2
20 Aug 2026, 07:4415,093-2
19 Aug 2026, 10:1215,095+8
18 Aug 2026, 10:3315,087-5
17 Aug 2026, 10:5415,092+8
15 Aug 2026, 19:4315,084+11
14 Aug 2026, 05:5815,073first reading

Engagement

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

ERR · 30 days
7.94%
avg views ÷ 15,100 subscribers
Avg views / post
1,200
61 posts measured
Reaction rate
1.90%
reactions ÷ views · ER floor
Posts in window
61
of 84 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
WindowRolling 30 days · latest post in window 3 September 2026
Posts held84 (31 July 20263 September 2026)
Views total73,173
Reactions total1,390
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:58 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

Video runtime
22s
Average length
11s

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

1,659 reactions across 73 posts, in 16 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁42925.9%
🔥30518.4%
29717.9%
💯21613.0%
👍925.55%
💅824.94%
custom 5346005927168335820412.47%
😇402.41%
custom 5300757802459888229342.05%
😍301.81%
💘271.63%
🙏201.21%
👏140.844%
🥴140.844%
130.784%
❤‍🔥50.301%

Custom emoji. 2 of the rows above are 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 counts beside them are Telegram’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 84 of the 84 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 1,885 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 84 most recent posts we hold, published 31 July 2026 to 3 September 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

3 Sept 2026, 06:04 UTC526 views43 reactionsread 3 September 2026
Photo

@huntflow

😁15😍1310custom 53460059271683358205

2 Sept 2026, 12:17 UTC784 views23 reactionsread 3 September 2026

💌 Это письмо группы компаний «Свеза» о достижении инженера Дмитрия {\__/} (•́ ᴗ •̀) / > 💌 Это основатель и СЕО Хантфлоу Михаил Танский. Он получил письмо, растрогался и переслал его в редакцию {\__/} (• ᴗ •) / > 🎙️ Это HR «Свезы». Она рассказала нам, зачем компании гордиться своими сотрудниками во весь голос {___/} (˶ᵔ ᵕ ᵔ˶) /つ🗞 Вы не справились с любопытством и читаете оооочень интересное интервью в Журнале Хантф

9👍7🔥7

2 Sept 2026, 09:25 UTC843 views18 reactionsread 3 September 2026

«Скинь шаблончик» немного вышло из-под контроля Мы впервые собрали в одном месте 2️⃣0️⃣ готовых документов, таблиц, калькуляторов и гайдов, которые закрывают большую часть операционки ⚡️руководителя рекрутмента⚡️ Все — из практики экспертов, с которыми мы делаем материалы, кейсы и ивенты. Если вам снова написали «скинь шаблончик» — просто отправьте это 👈 @huntflow

8🔥5🙏4👍1

2 Sept 2026, 06:35 UTC922 views19 reactionsread 3 September 2026
Photo

Посмотрите на это фото внимательнее. Хочется его нанять? Если да — проверку вы не прошли! 10 сентября приходите на бесплатную онлайн-конференцию Хантфлоу — разберем, как отличать сильных IT-специалистов от просто идеально подготовленных заек. Регистрируйтесь тут 🐰

🔥8😁7😇2👏1custom 53460059271683358201

1 Sept 2026, 10:24 UTC889 views12 reactionsread 3 September 2026
Video

Как отправить резюме из Хантфлоу на почту нанимающему, если у него лапки? 🐾 Если заказчик живет только в почте — пусть живет. Хантфлоу поможет вам подстроиться и вовремя получить от него фидбэк по кандидатам. Подробнее об этом в статье 😍 @huntflow

7custom 53460059271683358203👍2

1 Sept 2026, 07:30 UTC939 views25 reactionsread 3 September 2026
Photo

😱Шок! 0 промптов потребовалось, чтобы создать программу форума НАЁМ и эту картинку Раз уж сегодня 1 сентября, показываем самостоятельную работу. Картинку к посту нарисовали руками. Программу главного форума про рекрутинг тоже собрали сами — потому что за 11 лет слишком хорошо знаем, что у рекрутеров болит. Поэтому на НАЁМе вас ждут не общие рассуждения про будущее HR, а насыщенные выступления экспертов. Они помогу

custom 53007578024598882298🔥7👍6💅4

31 Aug 2026, 15:20 UTC≈1,010 views25 reactionsread 3 September 2026

Кто не успел отдохнуть летом, тот HR 🙂 Но вы не переживайте: Хантфлоу официально объявляет эту осень сезоном подарков, движухи и приятных сюрпризов. Скоро все расскажем⚡️ @huntflow

🔥15💅4😁42

31 Aug 2026, 12:26 UTC≈1,150 views13 reactionsread 3 September 2026
Photo

Отменить собеседование — тот еще кринж 🫠 Но это нормальная часть работы рекрутера. Разобрали, как отменить или перенести интервью без неловкости, потери кандидата и «ой, мы забыли предупредить». Читайте в Журнале Хантфлоу ❤️

9😁2🙏2

31 Aug 2026, 08:34 UTC≈1,170 views36 reactionsread 3 September 2026

Рекрутер 1: Давай напишем нанимающему без смайлика? Рекрутер 2: Мне страшно. Давай! @huntflow

😁28🔥6💯2

28 Aug 2026, 14:37 UTC≈1,390 views18 reactionsread 3 September 2026
Photo

Мы просто даем рекрутеру лучшую кисть 🖼

11👏2💯2custom 53460059271683358202😁1

28 Aug 2026, 11:57 UTC≈1,420 views9 reactionsread 3 September 2026
Poll

Что больнее для рекрутера?

  1. Кандидат принимает другой оффер11%
  2. Рекрутер месяц ведет поиск, а вакансию в итоге закрывают по рекомендации знакомого11%
  3. Кандидат внезапно принимает контроффер от текущего работодателя9%
  4. Кандидат исчезает ровно на этапе оффера20%
  5. Заказчик ставит вакансию на паузу4%
  6. Нанимающий решает закрыть вакансию своими силами2%
  7. После идеального кандидата клиент говорит: «Давайте еще посмотрим резюме»26%
  8. Вакансия «срочная-пресрочная», пока не наступает момент дать фидбек17%

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

💯43👏2

28 Aug 2026, 07:11 UTC≈1,310 views15 reactionsread 3 September 2026
Photo

IT-вакансия открытаааАА. Паника тоже Откликов много, сильных кандидатов мало, проверять сложно, джунов нанимать страшно. Условия для рекрутера, мягко говоря, бодрящие. Поэтому открыли регистрацию на онлайн-конференцию Хантфлоу «Наем среди сотен откликов: как находить и удерживать сильных IT-специалистов». ⚡️10 сентября, 11:00 МСК. Бесплатно, онлайн⚡️ С экспертами PURRWEB, Умскул, Финтабло, Островка и Хантфлоу раз

8🔥5👏2

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

Posts edited after publishing

@huntflow edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
10 August 2026

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.

28 Aug 2026, 11:57 UTCAnonymous Poll235 voters

Что больнее для рекрутера?

  1. Кандидат принимает другой оффер11%
  2. Рекрутер месяц ведет поиск, а вакансию в итоге закрывают по рекомендации знакомого11%
  3. Кандидат внезапно принимает контроффер от текущего работодателя9%
  4. Кандидат исчезает ровно на этапе оффера20%
  5. Заказчик ставит вакансию на паузу4%
  6. Нанимающий решает закрыть вакансию своими силами2%
  7. После идеального кандидата клиент говорит: «Давайте еще посмотрим резюме»26%
  8. Вакансия «срочная-пресрочная», пока не наступает момент дать фидбек17%

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 84 most recent posts we hold, published 31 July 2026 to 3 September 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.

Forward network

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 4 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

HR-аналитика
@hranalitycs · 34,141
Telegram ranks this channel #10 of 100 here — alongside 99 others — read 3 September 2026
DigitalHR (ДиджиталлЭйчАр): работа | вакансии | рекрутинг | стартапы
@digital_hr · 31,569
Telegram ranks this channel #38 of 100 here — alongside 99 others — read 6 September 2026
Кадровику
@kadroviku · 45,251
Telegram ranks this channel #53 of 93 here — alongside 92 others — read 27 August 2026
Эйч
@careerwithh · 62,784
Telegram ranks this channel #66 of 96 here — alongside 95 others — read 21 August 2026
Зайдите в кадры!
@kadrovoedelojournal · 30,994
Telegram ranks this channel #79 of 100 here — alongside 99 others — read 6 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Хантфлоу” (@huntflow), 15,100 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/huntflow.

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.