Telegram RegisterThe public register of Telegram
Telegram profile photo for Субсидиарная ответственность • Case by Case

Channel

Субсидиарная ответственность • Case by Case

@subsidiarka_kdl

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

21,073subscribers

+131 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001396867152
TypeChannel
Username@subsidiarka_kdl
DescriptionВсё о субсидиарной ответственности контролирующих лиц. Обратная связь @yulia_mikhalchuk, с других аккаунтов пишут мошенники. Мои другие каналы @Mikhalchuk_Yulia и @corplawpro Канал внесен в реестр https://www.gosuslugi.ru/snet/6740668cc577eb7c5212a5ff
Created11 July 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/subsidiarka_kdl

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@subsidiarka_kdl/4837 · this entry30 Jul 2026, 13:00 UTC@corplawpro/628930 Jul 2026, 14:04 UTC1.0065 minutes
@subsidiarka_kdl/4839 · this entry31 Jul 2026, 12:00 UTC@corplawpro/629231 Jul 2026, 14:00 UTC1.002.0 hours
@subsidiarka_kdl/4857 · this entry7 Aug 2026, 14:02 UTC@corplawpro/63117 Aug 2026, 14:34 UTC1.0031 minutes
@subsidiarka_kdl/5126 · this entry30 Oct 2026, 13:02 UTC@corplawpro/662831 Oct 2026, 16:33 UTC1.0028 hours
@subsidiarka_kdl/5133 · this entry31 Oct 2026, 16:59 UTC@corplawpro/66291 Nov 2026, 07:02 UTC1.0014 hours
@subsidiarka_kdl/5154 · this entry6 Nov 2026, 15:23 UTC@corplawpro/66567 Nov 2026, 10:35 UTC1.0019 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@corplawpro10 (8/8 hand-verifiable sample passed)1.008.0 hoursthis entry (10–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 80 comparable posts for this entry, running 28 July 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

20,90921,10521,00721,0736 August 202615 November 2026
63 measurements spanning 101 days, net +131. 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 20,880–21,134 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
15 Nov 2026, 15:5121,073-15
12 Nov 2026, 08:0421,088-2
10 Nov 2026, 07:1621,090-5
8 Nov 2026, 22:0921,095+5
7 Nov 2026, 13:5021,090+2
6 Nov 2026, 16:1521,088-1
5 Nov 2026, 13:1621,089+1
4 Nov 2026, 11:0421,088+5
3 Nov 2026, 11:4621,083-1
2 Nov 2026, 12:2821,084-3
1 Nov 2026, 15:0721,087-7
30 Oct 2026, 12:0421,094-5
29 Oct 2026, 12:4421,099-5
28 Oct 2026, 08:5021,104-1
27 Oct 2026, 12:2021,105+6
26 Oct 2026, 09:1621,099+4
25 Oct 2026, 08:0921,095+3
24 Oct 2026, 07:1621,092+8
23 Oct 2026, 09:4521,084+3
22 Oct 2026, 07:4021,081first reading

Engagement

82 posts held, back to 28 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 94 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.38%
avg views ÷ 21,073 subscribers
Avg views / post
922
28 posts measured
Reaction rate
0.323%
reactions ÷ views · ER floor
Posts in window
28
of 82 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 23 of 28 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 17 November 2026
Posts held82 (28 July 2026 – 17 November 2026)
Views total25,820
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 08:04 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
≈1,860
Videos
≈46
Links
≈3,090

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

260 reactions across 66 posts, in 10 distinct kinds. The most used accounts for 40.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10540.4%
🔥6424.6%
👍3915.0%
👏145.38%
😁114.23%
🙏103.85%
💯72.69%
🥰72.69%
🤩20.769%
🎉10.385%

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

Measured over the 82 most recent posts we hold, published 28 July 2026 to 17 November 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.

Advertising

Ad load
1.22%
1 of 82 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,300
over 1 measured post
Median views · rest
1,130
over 80 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqVJ3LveSs2ypbdQ18QWv6J36yTn38bFBsQVJ6111 August 202611 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 82 most recent posts we hold, published 28 July 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 28 posts held from the last 30 days (3.57%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 06:01 UTC386 viewsread 17 November 2026
Photo

Конкурсный управляющий не получает процентное вознаграждение за погашение требований дольщиков Фондом, если выплаты не стали результатом его эффективных действий #банкротство В банкротстве ООО «УК «Русская Усадьба» конкурсный управляющий Ануров И.И. потребовал установить и взыскать с ППК «Фонд развития территорий» 6,28 млн руб. процентов по вознаграждению. Первая и апелляционная инстанции требование удовлетворили.…

16 Nov 2026, 11:54 UTC729 views3 reactionsread 17 November 2026
Forwarded from @Mikhalchuk_YuliaPhoto

В экономколлегию ВС доходит одна жалоба из 50. Год назад – одна из 52 За десять месяцев 2026 года судьи Верховного суда передали в экономколлегию 298 дел. За тот же период 2025 года – 261. Это на 37 дел больше, рост на 14,2%. Для заявителя возможность добиться пересмотра изменилась незначительно. Об этом сегодня пишет «Коммерсантъ». За январь-октябрь прошлого года жалоб было 13 566, в этом году – 14 936. Если посчи…

💯3

16 Nov 2026, 06:03 UTC888 views3 reactionsread 17 November 2026
Photo

Кассационную жалобу нельзя вернуть из-за того, что суд первой инстанции несвоевременно передал в округ доказательства уплаты госпошлины Глыбина А.Н., привлеченная ответчиком в споре о субсидиарной ответственности по обязательствам ЖСК «Жилком», пыталась обжаловать судебный акт 2021 года о включении в реестр требования участника строительства. Апелляционный суд отказал ей в восстановлении срока на обжалование и прек…

❤3

15 Nov 2026, 13:06 UTC870 views3 reactionsread 17 November 2026
Photo

Кому оставить бизнес, если он кормит всю семью? Старший сын работает в компании и рассчитывает со временем её возглавить. Дочь в бизнесе не участвует, но отец помогает ей содержать семью. У предпринимателя есть жена, несовершеннолетний ребёнок и пожилые родители. Брат много лет руководит одним из направлений и считает, что тоже заслужил свою часть. Есть ещё бизнес-партнёр. Он переживает, что после смерти собственни…

🔥3

15 Nov 2026, 09:04 UTC759 views7 reactionsread 17 November 2026
Photo

Компания перестала работать. Кто ответит по её долгам? В Клубе корпоративных споров адвокат, основатель Клуба Юлия Михальчук и Марина Губенко, к.ю.н., доцент, судья в отставке, начали разбор Обзора ВС РФ от 19.11.2025 о субсидиарной ответственности по долгам недействующих компаний. Делимся выводами первой части дискуссии. 1️⃣ Исключение из ЕГРЮЛ не означает автоматической ответственности Нужно установить, как дейст…

❤4🔥2💯1

14 Nov 2026, 12:04 UTC809 views2 reactionsread 17 November 2026
Photo

Коллеги, 17 ноября начинаем курс «Ответственность контролирующих лиц по корпоративным и банкротным основаниям: актуальные вопросы права и судебная практика». Будем разбираться в наиболее сложных и дискуссионных вопросах привлечения контролирующих лиц к ответственности, обсуждать последние тенденции судебной практики и подходы судов к разрешению таких споров. На практике юристам всё чаще приходится сталкиваться с не…

👍2

14 Nov 2026, 06:00 UTC787 views1 reactionsread 17 November 2026
Photo

📣 Подготовили дайджест самых интересных судебных кейсов и новостей о субсидиарной ответственности за эту неделю! 📎 Формальная обособленность компаний не исключает субсидиарную ответственность, если через них последовательно переводился один и тот же бизнес с оставлением долгов на прежнем юрлице 📎 Если за те же действия с директора уже взысканы убытки, повторно привлекать его к субсидиарной ответственности нельзя 📎…

👍1

13 Nov 2026, 06:00 UTC873 views1 reactionsread 16 November 2026
Photo

Сам статус участника общества не позволяет автоматически привлечь его к субсидиарной ответственности вместе с директором - суд должен установить личный вклад в причинение вреда #субсидиарная_ответственность В банкротстве ООО «Логос Авто» конкурсный управляющий потребовал привлечь к субсидиарной ответственности бывшего директора Аглеева М.М., участника общества Аглееву В.М. и последующего директора Хакова И.А. Перв…

👏1

12 Nov 2026, 13:49 UTC899 views3 reactionsread 16 November 2026

Кассация потребовала исследовать перевод бизнеса должника Окружной суд отметил, что требования налоговой службы превышают 50% совокупного размера основной задолженности перед реестровыми кредиторами. Конкурсный управляющий ООО «Производственная компания Славянская трапеза» обратился с заявлением о привлечении контролирующих лиц к субсидиарной ответственности. Кредитор КПК «Крым», поддержанный ООО «СтартМани», также…

❤1👍1😁1

12 Nov 2026, 06:01 UTC907 views3 reactionsread 15 November 2026
Photo

Погашение реестра третьим лицом не дает управляющему автоматического права на 7% вознаграждения - нужно доказать, что именно его действия привели к расчетам с кредиторами #банкротство После полного погашения требований кредиторов ООО «Кронверк» конкурсный управляющий Румак Н.А. потребовала установить ей процентное вознаграждение в размере 36,9 млн руб. - 7% от суммы реестровых требований. Требования кредиторов пог…

❤2🔥1

11 Nov 2026, 06:03 UTC946 views3 reactionsread 15 November 2026
Photo

Непередача документов новым руководителем не доказывает, что предыдущий директор сохранил контроль над обществом и тоже не передал документацию #субсидиарная_ответственность В банкротстве ООО «Проксима Консалтинг» конкурсный управляющий потребовал привлечь к субсидиарной ответственности нескольких бывших руководителей общества. Первая инстанция и Девятый ААС признали основания ответственности доказанными в отношен…

❤2👍1

10 Nov 2026, 12:43 UTC≈1,040 views3 reactionsread 15 November 2026

Кассация признала, что финансовый управляющий не может быть лишен вознаграждения по причине погашения требований третьим лицом. Индивидуальный предприниматель Нина Шарипова была признана банкротом, а финансовым управляющим был утвержден Виталий Чулков. Управляющий обратился в суд с заявлением о взыскании с должника процентов по вознаграждению в размере 1,9 млн рублей. Суды первой инстанции и апелляция отказали в удо…

❤3

Showing the 12 most recent of 82 posts we hold for @subsidiarka_kdl. 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.

Posts recorded as deleted after publishing

We recorded 19 posts on @subsidiarka_kdl as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
13 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
6

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

Named by 10 registered channels — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Корпоративные споры • Case by Case
@corplawpro · 23,632
#1
PROбанкротство
@probankrotstvoru · 15,246
#2
Юлия Михальчук • Адвокат
@Mikhalchuk_Yulia · 16,672
#3
Судебная практика по банкротству
@sudpraktik_bankrot_demo · 26,804
#4
Ничего нового для образованного юноши
@educatedyoungman · 6,079
#5
Право.ru
@pravo_pravo · 58,040
#6
Банкротный Клуб
@BankruptcyClub · 4,932
#7
Ликвидация и банкротство
@a_d_v_o_k_a_t_RUSSIA · 8,267
#8
Частное право от Евгения Суворова
@insolvencylaw · 3,386
#9
💀 Анатомия убытков
@damagesanatomy · 8,497
#10
Новости ВС РФ
@vsrf_ru · 59,737
#11
Закон.ру
@zakon_news · 16,330
#12
Банкротство. the other side
@bankrotorg2 · 6,289
#13
Банкротный Волк
@bankrotwolf · 11,004
#14
Федресурс: банкротные новости
@fedresurs_insolvency · 4,441
#15
Журнал "Цивилистика"
@privlaw_journal · 7,968
#16
domnin.sa | Сергей Дóмнин
@domnin_sa · 2,977
#17
ШОРТРИД для юристов
@shortreadlaw · 12,710
#18
Субсидиарная ответственность, Кейсы
@AlenaShlegel · 1,880
#19
Банкротство.Новости
@bankrotnews · 8,492
#20
Доктор Права
@doktorprava · 20,833
#21
М-Логос
@m_logos · 9,741
#22
Представитель без доверки
@pbd_nikradio · 5,613
#23
Сделано для юриста
@made4lawyers · 7,512
#24
Банкротный Talk
@bankrotalk · 1,451
#25
ОРПАУ - Общероссийский профсоюз арбитражных управляющих
@orpau · 2,380
#26
Завтра собес!
@zavtrasobes · 11,631
#27
Арбитражный процесс для бизнеса
@arbitrium_processus · 7,871
#28
ПостГлоссатор
@PostGloss · 5,201
#29
Дмитрий Мирончук | Закон и право
@ruslaw · 25,184
#30
Лидия Эссен Антикризисный менеджмент как искусство
@LidiyaEssen · 2,237
#31
ACTIO_PAULIANA
@actio_pauliana · 1,015
#32
Субсидиатор | Об ответственности при банкротстве организации
@chupr_subsidiator · 1,732
#33
Практическое КУ
@corp_practice · 8,365
#34
Защита арбитражных управляющих
@shapovalovagroup · 2,614
#35
ЮрТехКонсалт
@ytc_legal · 1,740
#36
Pepeliaev Group | Пепеляев Групп
@pgp_official · 5,416
#37
Анонсы.Law
@anons_law · 12,923
#38
Марина Ивановна
@Marina_Gubenkolaw · 1,830
#39
Конституционный Суд
@ksrf_ru · 28,138
#40
Shokobear (Олег Зайцев о банкротстве)
@Shokobear · 10,575
#41
Loader from SVO
@loaderfromSVO · 40,423
#42
AVE in Law
@lawegorov · 13,942
#43
РУЛЬФЫ, ИЛЬФЫ И ИНХАУСЫ
@LawFirms · 21,704
#44
ilovedocs
@ilovedocs · 19,297
#45
Судебная практика АС Московского округа
@arbitrationpractice · 13,991
#46
Private Law Library | PLL Право
@privlawlib · 34,394
#47
Никифоров || Юридический менеджмент
@AlexeyNikiforov_Legalmanagement · 6,394
#48
В Зоне 14.13 (Ю. Федораев о банкротстве)
@vZone1413 · 4,129
#49
Legally_bald (Даниил Савченко)
@legally_bald · 3,875
#50
Дихотомия права
@dihotomya · 13,806
#51
Ольга Новикова | Документы юриста
@novikovalaw · 7,667
#52
Убытки АУ
@audamage · 2,721
#53
LetterRogatory v.2
@disputesandsanctions · 2,733
#54
GoodDocs
@GoodDocsDesign · 11,214
#55
Верховный суд - Главное от Закон.ру
@zakon_vsrf · 5,078
#56
Юридические вакансии
@legal_jobs · 36,269
#57
РИА Новости: дела арбитражные
@zarbitrazhy · 4,227
#58
Поворот на Право
@povorotnapravo · 50,723
#59
НСПАУ - Национальный Союз профессионалов антикризисного управления
@tgnspau · 1,739
#60
Записки пана Smertch’a
@smertchnotes · 3,010
#61
Илья Жарский печатает...
@i_zharskiy · 2,934
#62
Томашевская!
@tomashevskaya_zhanna · 4,372
#63
Азиза хейтит AI
@legaldesigner · 8,538
#64
Class Action Lab
@ClassActionLab · 2,377
#65
Анонимный управляющий
@anonim_au · 1,212
#66
Soft Law Community
@soft_law · 3,223
#67
Все цивильно
@VseCivilno · 7,269
#68
Рунетлекс
@runetlex · 8,571
#69
Pro IP
@ipmir · 9,669
#70
СУДЕБНАЯ ПРАКТИКА IP и IT
@sudpraktik_IPIT_demo · 22,955
#71
SOCIETAS
@societas_AK · 6,946
#72
LegalTech
@Lgltech · 15,331
#73
Четыре мнения
@the4opinions · 9,443
#74
На мушке 🪰
@namushkee · 12,367
#75
Хороший, плохой, злой
@arbitraghnik · 769
#76
Налоговые споры
@nalogi_sud · 23,328
#77
Всё идёт по праву
@DeoAuctore · 2,704
#78
ЛИЧНЫЕ НАЛОГИ
@persontaxes · 31,330
#79
efremov.online
@vefremovonline · 1,251
#80
Bilal Kurbanow
@libro_segreto · 1,020
#81
Апостол Права
@apostol_prava · 1,559
#82
Банкротные шутейки
@BANKRO_S · 5,594
#83
m_tserkovnikov
@tserkovnikov · 5,590
#84
Анонимный Молотников 🎓
@AMolotnikov2020 · 9,416
#85
Ты ж Юрист
@you_lawyers · 13,680
#86
На связи Legalconf
@legalconf · 2,962
#87
Научно-правовая библиотека
@NP_Biblioteka · 11,949
#88

Read from Telegram’s recommendation API, most recently 25 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Корпоративные споры • Case by Case
@corplawpro · 23,632
Telegram ranks this channel #2 of 91 here — alongside 90 others — read 18 September 2026
Судебная практика СКЭС ВС РФ
@vs_court · 56,547
Telegram ranks this channel #4 of 88 here — alongside 87 others — read 23 August 2026
Новости ВС РФ
@vsrf_ru · 59,737
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 23 August 2026
Дмитрий Мирончук | Закон и право
@ruslaw · 25,184
Telegram ranks this channel #13 of 86 here — alongside 85 others — read 14 September 2026
Право.ru
@pravo_pravo · 58,040
Telegram ranks this channel #17 of 90 here — alongside 89 others — read 23 August 2026
ЮРИСПРУДЕНЦИЯ
@yrisprudencia · 23,554
Telegram ranks this channel #34 of 86 here — alongside 85 others — read 17 September 2026
PRO Семейные права
@prosemuy · 20,279
Telegram ranks this channel #35 of 82 here — alongside 81 others — read 28 September 2026
Доктор Права
@doktorprava · 20,833
Telegram ranks this channel #38 of 86 here — alongside 85 others — read 25 September 2026
Налоговые споры
@nalogi_sud · 23,328
Telegram ranks this channel #42 of 92 here — alongside 91 others — read 18 September 2026
Loader from SVO
@loaderfromSVO · 40,423
Telegram ranks this channel #61 of 88 here — alongside 87 others — read 30 August 2026
ЛИЧНЫЕ НАЛОГИ
@persontaxes · 31,330
Telegram ranks this channel #64 of 91 here — alongside 90 others — read 6 September 2026
СУДЕБНАЯ ПРАКТИКА IP и IT
@sudpraktik_IPIT_demo · 22,955
Telegram ranks this channel #65 of 89 here — alongside 88 others — read 19 September 2026
Поворот на Право
@povorotnapravo · 50,723
Telegram ranks this channel #68 of 87 here — alongside 86 others — read 25 August 2026
Прокурорские будни
@anon_prok_press · 20,565
Telegram ranks this channel #69 of 86 here — alongside 85 others — read 26 September 2026
Юрист объясняет l Евгений Фурин
@furinlaw · 47,909
Telegram ranks this channel #73 of 79 here — alongside 78 others — read 3 September 2026
Библиотека юриста
@library_lawyer · 25,750
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 14 September 2026
Народный Юрист
@PeopleIsLawyer · 23,480
Telegram ranks this channel #80 of 84 here — alongside 83 others — read 17 September 2026
Законодатель
@zaconodatel · 21,471
Telegram ranks this channel #81 of 89 here — alongside 88 others — read 22 September 2026
Private Law Library | PLL Право
@privlawlib · 34,394
Telegram ranks this channel #87 of 88 here — alongside 87 others — read 4 September 2026
ilovedocs
@ilovedocs · 19,297
Telegram ranks this channel #89 of 92 here — alongside 91 others — read 2 October 2026

This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Субсидиарная ответственность • Case by Case” (@subsidiarka_kdl), 21,073 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/subsidiarka_kdl.

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.