Telegram RegisterThe public register of Telegram
Telegram profile photo for HR Russia

Channel

HR Russia

@wanted_IT

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

914subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002145920095
TypeChannel
Username@wanted_IT
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/wanted_IT

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

907914910.57 August 2026 — 910 subscribers8 August 2026 — 910 subscribers24 August 2026 — 909 subscribers1 September 2026 — 910 subscribers16 September 2026 — 908 subscribers1 October 2026 — 907 subscribers12 October 2026 — 912 subscribers19 October 2026 — 913 subscribers3 November 2026 — 912 subscribers10 November 2026 — 914 subscribers7 August 202610 November 2026
10 measurements spanning 95 days, net +4. 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 906–915 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 19:08914+2
3 Nov 2026, 20:37912-1
19 Oct 2026, 20:41913+1
12 Oct 2026, 11:41912+5
1 Oct 2026, 18:16907-1
16 Sept 2026, 15:36908-2
1 Sept 2026, 02:15910+1
24 Aug 2026, 19:26909-1
8 Aug 2026, 01:02910no change
7 Aug 2026, 17:05910first reading

Engagement

5 posts held, back to 30 July 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 page of 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

25 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51996291209835415001040.0%
custom 53954067440861263811040.0%
custom 5400209569790042029520.0%

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

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

Recent posts

7 Aug 2026, 07:10 UTC32 views2 reactionsread 8 August 2026

О май... кажется, мы снова перестарались. 😂🍓 Кроме этого вас ждут: 🍓 мастер-класс по созданию ягодных настоек (сделаем, брендируем бутылочку и заберем с собой); 🧘‍♀️ мастер-класс по гвоздестоянию 😱; 🧠 практика по работе с выгоранием и восстановлению энергии; 🎻 живая скрипка; 🔥 вечер у костра с гитарой и маршмеллоу. И это еще не вся программа… 🤫

custom 53954067440861263812

5 Aug 2026, 12:34 UTC119 views9 reactionsread 8 August 2026
Photo

А что будет? 🍓

custom 51996291209835415007custom 53954067440861263812

5 Aug 2026, 12:28 UTC114 views6 reactionsread 8 August 2026
Photo

Мы готовы рассказать, где пройдет следующий HR Brunch. 🌿 После солнечной Италии мы решили сделать что-то совершенно другое. Представьте… 🌾 Ферма за городом. 🚐 Трансфер туда и обратно. 👥 Небольшая компания единомышленников. 🍽️ Ужин от шеф-повара. 🌅 Целый день, который хочется прожить без спешки, в разговорах, знакомствах и новых идеях. Это будет самый камерный HR Brunch, который мы когда-либо проводили. Именно поэт…

custom 53954067440861263816

30 Jul 2026, 08:10 UTC78 views5 reactionsread 8 August 2026
Photo

Не верьте презентациям. Смотрите на решения. За последнее время я все чаще замечаю одну закономерность. Когда в компании начинаются серьезные изменения, официальные сообщения почти всегда звучат одинаково. «Мы выходим на новый этап развития.» «У нас амбициозная стратегия на 5 лет.» «Впереди масштабный рост.» И это совершенно нормально. Ни один руководитель не выйдет к сотрудникам со словами: «Коллеги, у нас непрос…

custom 54002095697900420295

30 Jul 2026, 07:05 UTC61 views3 reactionsread 8 August 2026
Photo

Самый странный рынок труда, который я видела за последние годы. Кажется, мы одновременно живем в двух реальностях. Одни компании продолжают активно нанимать и говорят, что найти сильных специалистов невозможно. Другие — замораживают проекты, пересматривают бюджеты, объединяют команды и становятся гораздо осторожнее с наймом. И самое интересное, что оба утверждения могут быть правдой. Сегодня рынок уже нельзя описа…

custom 51996291209835415003

Showing the 5 most recent of 5 posts we hold for @wanted_IT. 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.

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

“HR Russia” (@wanted_IT), 914 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/wanted_IT.

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.