Channel
@yurdirector
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
299subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003728008203 |
|---|---|
| Type | Channel |
| Username | @yurdirector |
| Description | Канал Анны Земновой про управление юридической командой и профессиональное развитие юриста и руководителя🎯 |
| Created | Between 1 February 2026 and 2 June 2026— 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/yurdirector |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 08:03 | 299 | no change |
| 7 Aug 2026, 19:05 | 299 | first reading |
8 posts held, back to 2 June 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 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 8 posts for this entry, the most recent from 15 July 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.
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.
58 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 17 | 29.3% | |
| 👏 | 11 | 19.0% | |
| 😁 | 10 | 17.2% | |
| 👍 | 8 | 13.8% | |
| 🏆 | 3 | 5.17% | |
| ❤ | 2 | 3.45% | |
| 👨💻 | 2 | 3.45% | |
| 💅 | 2 | 3.45% | |
| 💯 | 2 | 3.45% | |
| 🤝 | 1 | 1.72% |
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 8 of the 8 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 58reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 2 June 2026 to 15 July 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.
Получили сегодня решение о продлении IT аккредитации! Очень радостная новость и небольшой повод отметить) Если раньше аккредитация была больше формальностью, то в этом году она впервые продлевалась по новым правилам - было много нового и непонятного. Волнительно, когда от твоей команды зависит то, сможет ли бизнес продолжать пользоваться всеми льготами, которые дают IT компаниям очень хорошую финансовую поддержку. …
👏8🏆1💅1
По традиции #мемопятница🥂
😁4
На прошлой неделе основатель Legal Talents Ольга Демидова провела очередное закрытое мероприятие для руководителей юридических команд, на котором обсудили текущее состояние рынка юридического труда и то, как сейчас нанимать лучшие кадры. Тот случай, когда получилось вообще без воды, всё по делу и про реальную практику. Основные инсайты: 🎯 Выпуск по юриспруденции все еще до сих превышает кадровую потребность примерн…
👍5👨💻2🔥2❤1💯1
В минувшую пятницу в ВЭБ центре собрался весь crème de la crème юридического инхаус сообщества Москвы. Подводили итоги конкурса The Department-2026, проводимого редакцией журнала Legal Insight. Вот уже 21 год (!) редакция Legal Insight проводит конкурс среди всех юридических департаментов страны и определяет лучшие команды в различных номинациях. Мы с командой решили попробовать и в этом году тоже заявились в двух …
🔥6❤1
Пятница! По традиции врываюсь с мемами) #мемопятница
😁6🔥2
Уже в пятницу будут объявлены номинанты и победители конкурса лучших юридических департаментов страны. Мы в этом году решили впервые принять участие, поэтому с нетерпением ждем пятницу и результаты🤞
👏3🏆2
Осталось всего три дня до финала The DEPARTMENT — 2026 Работа в редакции кипит. Как всегда, готовим много сюрпризов для нетворкинга. Каждый раз придумываем новые игры, механики, форматы — чтобы атмосфера была не просто торжественной, а по-настоящему тёплой и живой. И вот, в процессе этих приготовлений, вспомнилось. А ведь в 2022 году специально для конкурса мы сняли мини-сериал про будни in-house-юристов. Про то, к…
🔥5
Парадокс работы юриста или почему юристов многие недолюбливают Представьте, что вы сделали свою работу объективно хорошо, даже отлично. И ожидаете, что вас похвалят, дадут «вымпел, ну или какую-то ручку». Но у юристов так часто не работает. Предположим, бизнес приносит какую-то идею, которая на его взгляд просто идеальна. Эта идея приходит на проработку и согласование юристам, которые находят в ней риски и неблагоп…
👍3🔥2💅1💯1🤝1
Showing the 8 most recent of 8 posts we hold for @yurdirector. 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.
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.
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.
“Директор ЮрДепа - Анна Земнова” (@yurdirector), 299 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/yurdirector.
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.