Telegram RegisterThe public register of Telegram
Telegram profile photo for Юридические секреты

Channel

Юридические секреты

@legal_secrets

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

2,104subscribers

+28 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

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

Growth

2,0752,1182,096.57 August 2026 — 2,076 subscribers7 August 2026 — 2,076 subscribers8 August 2026 — 2,075 subscribers13 August 2026 — 2,081 subscribers16 August 2026 — 2,091 subscribers19 August 2026 — 2,103 subscribers23 August 2026 — 2,111 subscribers27 August 2026 — 2,118 subscribers1 September 2026 — 2,115 subscribers5 September 2026 — 2,104 subscribers2,1047 August 20265 September 2026
10 measurements spanning 29 days, net +28. 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 2,069–2,124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 19:192,104-11
1 Sept 2026, 16:032,115-3
27 Aug 2026, 02:382,118+7
23 Aug 2026, 21:072,111+8
19 Aug 2026, 23:412,103+12
16 Aug 2026, 18:192,091+10
13 Aug 2026, 11:272,081+6
8 Aug 2026, 06:362,075-1
7 Aug 2026, 20:322,076no change
7 Aug 2026, 18:382,076first reading

Engagement

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

What this channel posts

Video runtime
55s
Average length
28s

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

39 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1846.2%
🔥1230.8%
💔410.3%
😱410.3%
👍12.56%

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

Measured over the 12 most recent posts we hold, published 23 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, 09:52 UTC90 views1 reactionsread 7 August 2026
Photo

Давно обещала рассказать про неправильное оформление маркировки рекламы,за которое можно получить штраф от ФАС В целом,нюансов в этой теме просто 🚊 и маленькая 🛒 Мало просто получить токен в ОРД, нужно еще: -правильно разместить маркировку с учетом всех особенностей платформы и деятельности рекламодателя -подать отчетность -оплатить 3% сбор за распространение рекламы Поэтому здесь нужно очень детально разбиратьс

🔥1

5 Aug 2026, 06:08 UTC175 views4 reactionsread 7 August 2026
Video

Как вам такая реклама? Увидели в ней нецензурные слова? *Информация о деле взята из открытых источников на сайте ФАС: https://fas.gov.ru/news/34777 А теперь давайте разберемся в чем суть: Реклама продвигает покупку ОСАГО через приложение Альфа-банка. В ролике несколько раз повторяется фраза: «Застрахуй машину, застрахуй…» В оригинале это песня Ноггано «Застрахуй братуху». В рекламе убрали прямую ненормативную лек

2🔥2

3 Aug 2026, 08:10 UTC205 views8 reactionsread 7 August 2026
Photo

Миниатюра: «Марина и ее шоппинг»😂 поняла, что давненько я не покупала новые книги * и да, у меня куча непрочитанных уже купленных книг, но ничего не поделаешь, они пока ждут своего часа😂 Кто-нибудь читал, как вам?

4🔥4

29 Jul 2026, 14:07 UTC243 views1 reactionsread 7 August 2026
Video message

Video message, posted without a caption

👍1

24 Jul 2026, 10:15 UTC302 views9 reactionsread 7 August 2026

Навигация по каналу для всех,кто недавно присоединился: ✔️Подкаст на тему «Запрет иностранных слов в бизнесе и рекламе» ✔️Подкаст на тему «Как безопасно продвигаться в социальных сетях» ✔️Подкаст на тему «Решение по делу,где блогер отметил бренды и избежал ответственности» ✔️ Подкаст на тему «Допустимые и безопасные форматы контента» ✔️Уроки по маркировке рекламы, которые помогут вам разобраться в том: как рекла

🔥54

23 Jul 2026, 08:06 UTC268 views9 reactionsread 7 August 2026
Photo

•Услугу дополнительную навязали •В записи на нужное мне время отказали •Из-за опоздания на 6 минут не пустили А потом удивляемся почему нет клиентов? Я сама работаю с людьми, и знаю что такое « человеческий фактор». Также я с уважением отношусь ко всем. Есть внутренние правила, которые нужно соблюдать, я тоже с этим согласна НО Ваши правила не должны ущемлять вашего клиента или доставлять ему неудобства. А персона

8😱1

23 Jul 2026, 03:50 UTC203 views5 reactionsread 7 August 2026
Video message

Video message, posted without a caption

😱3💔2

23 Jul 2026, 03:49 UTC180 views2 reactionsread 7 August 2026
Video message

Video message, posted without a caption

💔2

Showing the 12 most recent of 12 posts we hold for @legal_secrets. 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Юридические секреты” (@legal_secrets), 2,104 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/legal_secrets.

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.