Telegram RegisterThe public register of Telegram
Telegram profile photo for Lady in Red - Виктория Коржиновская

Channel

Lady in Red - Виктория Коржиновская

@smart_lady_in_red

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

146subscribers

+0 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-1002267276980
TypeChannel
Username@smart_lady_in_red
DescriptionТо, чем я живу
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/smart_lady_in_red

Growth

1467 Aug 2026, 16:02 — 146 subscribers8 Aug 2026, 21:00 — 146 subscribers7 Aug 2026, 16:028 Aug 2026, 21:00
2 measurements spanning 1 day. 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 145–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 21:00146no change
7 Aug 2026, 16:02146first reading

Engagement

15 posts held, back to 27 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
44.6%
avg views ÷ 146 subscribers
Avg views / post
65.1
15 posts measured
Reaction rate
6.45%
reactions ÷ views · ER floor
Posts in window
15
of 15 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 8 of 15 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 8 August 2026
Posts held15 (27 July 20268 August 2026)
Views total977
Reactions total35
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 21:00 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

Photos
884
Videos
116
Links
114

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.

Reaction mix

35 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 65.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2365.7%
🔥411.4%
💯38.57%
👍25.71%
😁12.86%
🙏12.86%
🤝12.86%

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

Measured over the 15 most recent posts we hold, published 27 July 2026 to 8 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

8 Aug 2026, 11:56 UTC24 viewsread 8 August 2026
Forwarded from @petrovskajaoksanaPhoto

Изменения неизбежны Спойлер, даже, если вы к ним не готовы Любой бизнес-процесс нуждается в владельце: человеке, который задаёт правила игры и несёт за них ответственность. Когда же правила непонятны участникам, наступает хаос. Поэтому в начале работы стоит задавать простой, но дисциплинирующий вопрос — какую именно задачу мы решаем. А чтобы эти вопросы не терялись, в команде полезно иметь человека, который их фикс

6 Aug 2026, 08:47 UTC38 viewsread 8 August 2026
Forwarded from @selecty_insidePhoto

Что делать, если пришла повестка? Как получить ИТ-отсрочку? Какие документы стоит подготовить заранее? И как работает бронь от мобилизации? 📕 Вместе с экспертами Selecty собрали ответы на самые важные вопросы в большом гайде — только то, что действительно нужно знать в 2026 году. ➿➿➿➿➿➿➿➿➿ 👉 Забирай гайд в нашем боте — @selecty_career_guide_bot #IT #ИТ #гайд #призыв #мобилизация

6 Aug 2026, 08:47 UTC49 views1 reactionsread 8 August 2026

Коллеги составили гайд, делюсь. Лучше верить в лучшее, но готовиться ко всему

👍1

5 Aug 2026, 06:28 UTC57 views8 reactionsread 8 August 2026

Подписываюсь под каждым словом!👆 Сегодня как раз выходит новый юрист к нам в команду и мы по традиции всем отделом идём вместе обедать и знакомиться☺️

8

5 Aug 2026, 06:28 UTC45 views11 reactionsread 8 August 2026
Forwarded from @Veselov_telegraph

Нужен ли команде тимбилдинг?! Чем дальше, тем больше убеждаюсь, что команду объединяют не только рабочие задачи. Понятно, что в юридической работе важны экспертиза, сроки, процессы, качество документов, ответственность и умение держать удар. Без этого никуда. Но если говорить честно, команда держится не только на этом. Она держится еще и на человеческих связях. Вот мы, например, собираемся с коллегами в ближайшие в

6💯3👍1🙏1

3 Aug 2026, 10:45 UTC59 views5 reactionsread 8 August 2026
Forwarded from @pravotechPhoto

💼 Справится ли ИИ с вашей юридической задачей? ПравоКонсультант готовит заключение с выводами, аргументами и судебной практикой. Но финальное решение все равно остается за юристом. Запустили конкурс: передайте ПравоКонсультант реальную задачу и проверьте ответ. Если найдете существенную ошибку и подтвердите ее судебной практикой — получите 4 000 ₽ за каждый засчитанный кейс. Как участвовать — рассказали в карточк

2🔥2🤝1

3 Aug 2026, 10:44 UTC62 viewsread 8 August 2026

Вот как раз и конкурс у коллег начался! Пробуем! #challenge_accepted

1 Aug 2026, 20:05 UTC78 viewsread 8 August 2026

P.S. Первый вопрос, который приходит в голову, когда открываешь систему право(консультант) - и чем же она отличается от нейросетей, которыми я сейчас пользуюсь, - т.к. интерфейс до боли знакомый, но когда начинаешь тестировать, понимаешь, чем) Пишите свои отзывы, мне любопытно, что получится у вас в ходе ваших экспериментов) Это поможет и мне лучше разобраться. Тем более есть пока возможность бесплатно почелленджить

1 Aug 2026, 20:03 UTC75 viewsread 8 August 2026
Photo

Право на консультанта Только недавно мы с коллегами в Санкт-Петербурге разбирали химию между инхаусами и консультантами (не подумайте, химичили мы в Питере рамках закона, никому не хотели насолить и разбирали мы там людей только в метафорическом смысле)) И вот сейчас мне представилась возможность разобрать еще то, как могут сложится отношения у меня, как у инхаус-юриста, руководителя юридического направления, с нов

28 Jul 2026, 16:31 UTC90 views3 reactionsread 8 August 2026
Forwarded from @privacy_kitchen_spbPhoto

⚡ Privacy Kitchen. Петербург приезжает в Москву. Есть вещи, которые лучше не менять. Например, традицию собираться за большим столом. На один вечер Privacy Kitchen переезжает в Москву. С той же атмосферой, тем же подходом и новым ужином, вдохновлённым Латинской Америкой. 📅 21 августа 🕖 19:00–22:30 👇 О чём поговорим? ▶️ Как из одного DPO вырастает полноценная privacy-функция: когда приходит время перестать делать

🔥21

28 Jul 2026, 16:31 UTC77 views4 reactionsread 8 August 2026

У Ерната, спикера, организатора квиза и дебатов в нашем книжном киноклубе Selecty, и вообще хорошего специалиста по privacy намечается камерное мероприятие, присоединяйтесь)

4

Showing the 12 most recent of 15 posts we hold for @smart_lady_in_red. 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 — 1,307,554 of 1,481,243entries 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

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Lady in Red - Виктория Коржиновская” (@smart_lady_in_red), 146 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/smart_lady_in_red.

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.