Telegram RegisterThe public register of Telegram

Channel

Zarlaw: право & IT

@digital_zarlaw

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

2,748subscribers

+6 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-1001392161203
TypeChannel
Username@digital_zarlaw
Created2 April 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/digital_zarlaw

Growth

2,7422,7482,7457 August 2026 — 2,742 subscribers7 August 2026 — 2,742 subscribers10 August 2026 — 2,743 subscribers13 August 2026 — 2,748 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +6. 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,741–2,749 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:552,748+5
10 Aug 2026, 13:072,743+1
7 Aug 2026, 01:302,742no change
7 Aug 2026, 01:192,742first reading

Engagement

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

ERR · 30 days
15.6%
avg views ÷ 2,748 subscribers
Avg views / post
428
18 posts measured
Reaction rate
1.67%
reactions ÷ views · ER floor
Posts in window
18
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (15 July 20265 August 2026)
Views total7,709
Reactions total129
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:12 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.

Reaction mix

139 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 31.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4431.7%
👍3122.3%
2115.1%
❤‍🔥1812.9%
👏85.76%
💯85.76%
🥰42.88%
🎉32.16%
🤔21.44%

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

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

5 Aug 2026, 14:20 UTC219 views8 reactionsread 7 August 2026
Photo

💲На практике возникают вопросы о том, могут ли некоммерческие организации претендовать на государственную аккредитацию IT-компаний. Мы решили направить запрос в Минцифры для получения разъяснений в отношении таких организаций. И вот, наконец получили разъяснения, которые проливают свет на особенности аккредитации таких организаций. Полезные выводы из ответа Минцифры: 1️⃣ Получить аккредитацию в качестве IT-компании

❤‍🔥6👏1🔥1

5 Aug 2026, 13:10 UTC224 views6 reactionsread 7 August 2026
Forwarded from @itpravotechFile

File, posted without a caption

🔥5👏1

5 Aug 2026, 13:10 UTC222 views7 reactionsread 7 August 2026
Forwarded from @itpravotechPhoto

Например, собрать рабочий плейбук для проверки договоров. На тренинге по ИИ мы взяли конкретную задачу: компания регулярно заключает договоры поставки с монтажом. И вместо очередного промта «проверь договор и найди риски» пошли другим путем. Сначала вместе сформулировали правила компании, по которым такие договоры должны проверяться. Например: ⏩️ договор должен оставаться именно договором поставки, несмотря на нал

2❤‍🔥2👍1💯1🥰1

4 Aug 2026, 09:26 UTC280 views11 reactionsread 7 August 2026
Photo

Мы видели десятки таких кейсов. ⚙️Бизнес решает: «Хватит рутины, внедряем IT-решение». Покупают дорогой конструктор, CRM, систему с ИИ. Громкий запуск, обучение, энтузиазм… А через полгода сотрудники тихо саботируют систему и втайне возвращаются к Excel, Word и пересылке файлов по почте. Почему так происходит❓ Софт здесь ни при чём. ⚠️Потому что нельзя автоматизировать то, что сломано изначально. Если у вас: ⚫️

👍5🔥3🤔2🥰1

3 Aug 2026, 14:32 UTC328 views7 reactionsread 7 August 2026
Photo

На вебинаре мы много говорили о том, что ФНС проверяет не только договор с самозанятым и наличие чеков. Налоговая сопоставляет договоры, акты, переписку, выплаты и то, как исполнитель фактически встроен в работу компании. Поэтому формально правильный договор может не помочь, если реальные отношения выглядят как трудовые. Вот пять вопросов для быстрой проверки своей модели. 1️⃣ Мы покупаем конкретный результат или р

3👏2🔥2

31 Jul 2026, 10:41 UTC435 views11 reactionsread 7 August 2026

💲Запись вебинара уже доступна! «Аудит IT-деятельности: как подтвердить право на налоговые льготы» Налоговые льготы для IT-компаний — это не только аккредитация. Чтобы сохранить право на их применение, важно понимать, что именно проверяет ФНС и какие документы подтверждают соответствие требованиям. На вебинаре разобрали: ➕ условия применения налоговых льгот ➕ какие доходы относятся к IT-выручке ➕ что проверяет ФНС

👍5❤‍🔥3🔥3

30 Jul 2026, 13:06 UTC414 views7 reactionsread 7 August 2026
Photo

💲В продолжение недавно проведённого вебинара отвечаем на вопросы, которые были нами получены в ходе вебинара: Если СМЗ находится за пределами нашей страны более 183 дней, то он теряет налоговое резидентство по НК РФ и статус СМЗ? ⏩️Нет. Статус налогового резидентства и режим самозанятости никак не связаны. Часто заключают просто ГПХ без самозанятости. Можно ли так делать, в чём отличия и риски? ⏩️Да, иногда физичес

❤‍🔥3👏3💯1

30 Jul 2026, 09:33 UTC394 views7 reactionsread 7 August 2026
Photo

22 июля 2026 года Государственная Дума приняла в третьем чтении законопроект № 959258-8 о внесении изменений в КоАП РФ. Поправки, разработанные Минэкономразвития России, вводят административную ответственность для операторов посреднических цифровых платформ и саморегулируемых организаций оценщиков. Основная часть изменений вступает в силу с 1 октября 2026 года. Напомним, закон о платформенной экономике был принят 31

🔥3👍21❤‍🔥1

29 Jul 2026, 11:13 UTC487 views11 reactionsread 7 August 2026
Photo

📅30 июля | 12:00 (МСК) Налоговые льготы для IT-компаний — это не только аккредитация. ФНС проверяет фактическую деятельность компании, структуру выручки, договоры, права на ПО и подтверждающие документы. На вебинаре разберем: ▫️ какие условия необходимо соблюдать для применения льгот ▫️ что именно проверяет ФНС ▫️ какие доходы относятся к IT-выручке ▫️ какие документы подтверждают право на льготы ▫️ как провести ау

👍5❤‍🔥2🎉2🔥2

29 Jul 2026, 09:47 UTC403 views2 reactionsread 7 August 2026
Photo

После вебинара собрали практический чек-лист, по которому можно проверить: 📶 все ли точки сбора данных учтены 📶 правильно ли распределены роли оператора и обработчика 📶 где действительно нужно согласие, а где есть другое основание 📶 как оформлена работа с подрядчиками 📶 подтверждается ли получение согласий 📶 готова ли команда к утечке и уведомлению Роскомнадзора 📶 соответствует ли юридическая модель реальному устрой

1💯1

28 Jul 2026, 14:21 UTC404 views10 reactionsread 7 August 2026
Photo

🚀Новый кейс от Людмилы Харитоновой Когда бизнес растет, старые юридические решения перестают работать. Но многие замечают это только тогда, когда возникают первые серьезные риски. В новой статье разбираем реальную ситуацию из практики, показываем, где была проблема, какие последствия она могла повлечь и как удалось выстроить рабочее юридическое решение. Полезно руководителям, основателям технологических компаний и

🔥5👍2🥰21

Showing the 12 most recent of 20 posts we hold for @digital_zarlaw. 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 — 69,323 of 1,345,403entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 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.

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

“Zarlaw: право & IT” (@digital_zarlaw), 2,748 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/digital_zarlaw.

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.