2 measurements spanning 4 days. 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 38–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 20:17
39
no change
7 Aug 2026, 05:21
39
first reading
Engagement
7 posts held, back to 20 October 2022 — 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 7 posts for this entry, the most recent from 20 April 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
30
Links
34
Lifetime counters from Telegram’s own channel header, read 10 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.
Reaction mix
3 reactions across 2 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
3
100.0%
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 3 of the 7 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 20 October 2022 to 20 April 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔥 Новое интервью про Engineering Management уже на канале!
Что это за профессия, какими качествами должен обладать EM и как вкатиться в сферу. Кроме того, много говорили про развитие, про переезды и про будущее русскоязычного IT-сообщества.
Гость выпуска Илья Немиро, который долгое время проработал в позиции Engineering Manager в компании Toptal, а последние пол года работает в качестве Software Engineer в Wix.
👉 Y…
Давно тут не было апдейтов. год был сложный и одновременно интересный, каждый день какой-то новый челендж.
Мне всё больше нравится осознание того, что невозможно сделать вывод о компании только на основе рассказа одного человека, поэтому в планах нового сезона интервью будет особенная изюминка.
Пока я готовлю продакшн на новом месте смотрите как решил челендж ушедшего года (если пропустили уведомление на канале):
…
Здравствуйте, дорогие 🤜🏻🤛🏻
Хочу поделиться своим летним вело-лагерем.
Отличный сезон подошел к концу, весной и предположить не мог, что велосипед перейдет из разряда «регулярные тренировки 2-3 раза в неделю» в разряд «катать каждый день». Сезон дал огромный заряд на следующий, где я сдвину больше фокус на шеринг всего нового, что я ежедневно качаю в менеджменте, всё-таки каждый день ту мач 😄. Но пока в ближайших целя…
👍1
Signed Ilia Nemiro
Showing the 7 most recent of 7 posts we hold for @huntit. 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.
Mentions
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Хантит – Hunt IT” (@huntit), 39 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/huntit.
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.
