Telegram RegisterThe public register of Telegram
Telegram profile photo for Иван Шевелев • Shyft Agency

Channel

Иван Шевелев • Shyft Agency

@shevelaw

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

164subscribers

+1 since we began measuring on 27 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002343399229
TypeChannel
Username@shevelaw
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live12 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/shevelaw

Growth

163164163.527 August 2026 — 163 subscribers27 August 2026 — 163 subscribers12 September 2026 — 164 subscribers27 August 202612 September 2026
3 measurements spanning 16 days, net +1. 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 163–164 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 09:57164+1
27 Aug 2026, 16:30163no change
27 Aug 2026, 16:16163first reading

Engagement

17 posts held, back to 26 May 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.

ERR · 30 days
52.9%
avg views ÷ 164 subscribers
Avg views / post
86.8
4 posts measured
Reaction rate
13.0%
reactions ÷ views · ER floor
Posts in window
6
of 17 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 3 of 4 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 27 August 2026
Posts held17 (26 May 202627 August 2026)
Views total347
Reactions total39
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 16:30 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

211 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 37.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8037.9%
5626.5%
👍2612.3%
custom 52088853424421230632411.4%
custom 5206680211743100481157.11%
custom 520634914707397089683.79%
😁20.948%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 17 most recent posts we hold, published 26 May 2026 to 27 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

27 Aug 2026, 15:01 UTC39 views15 reactionsread 27 August 2026
Photo

⬛️ Запускаем Shyft Agency Практика сопровождения инновационного контента выросла. То, что начиналось как точечные консультации, теперь стало полноценной инфраструктурой. Сегодня я официально запускаю Shyft Agency — специализированное юридическое агентство. Мы с командой берем на себя: 🔍 Аудит ИИ-рисков: Правовая очистка пайплайнов для киностудий и платформ. 🛡 Защита цифрового образа: Защита образов публичных лиц о

🔥8custom 520888534244212306352

27 Aug 2026, 11:01 UTC48 views10 reactionsread 27 August 2026
Voice message

Voice message, posted without a caption

5👍3custom 52063491470739708962

27 Aug 2026, 11:01 UTC46 viewsread 27 August 2026

🎙 Короткие мысли между встречами: почему рынок ИИ-права перерос маленькие форматы, и что будет дальше.

27 Aug 2026, 07:03 UTC214 views14 reactionsread 27 August 2026
Photo

🎬 С Днем российского кино! Индустрия меняется быстрее, чем законы. Дипфейки, сценарии от GPT, сгенерированные саундтреки — ИИ уже плотно зашел на съемочную площадку. Ко Дню кино мы с командой подготовили шпаргалку, которая сэкономит продюсерам миллионы на стадии релиза: 1️⃣ Карточки: разбор фатальных ошибок в нейросетевом продакшене. 2️⃣ Видео-разбор: Мои выступления на кинофестивале «Евразия» о правовых реалиях

🔥75👍2

17 Aug 2026, 14:02 UTC96 views17 reactionsread 27 August 2026
Video

Всем привет! 👨🏻‍💻 ИИ, может, и работает 24/7, но кожаным юристам иногда требуется принудительная перезагрузка. Мой импровизированный трехнедельный отпуск официально подходит к концу) За это время накопилась критическая масса инсайтов, свежей судебной практики и просто абсурдных кейсов на стыке IT, медиа и права. Возвращаюсь к вам не с пустыми руками. В ближайшее время нас ждут новые темы, форматы, приколы и немног

🔥85👍4

27 Jul 2026, 15:30 UTC285 views20 reactionsread 27 August 2026
Photo

Мы долго ждали этого прецедента — и вот он: В России суд признал законным увольнение топ-менеджера за слив корпоративных данных в нейросеть Знаете, когда я выступал на конференциях (и писал в канале про риски «теневого ИИ»), некоторые смотрели на меня со снисходительной улыбкой. Мол, кто за такое увольняет? Или лучше: кто в здравом уме понесет коммерческую тайну в ChatGPT или Claude? Отвечаю: возможно, это ваши лу

🔥8custom 52066802117431004817custom 52088853424421230635

24 Jul 2026, 14:55 UTC164 views17 reactionsread 27 August 2026
Photo

🍓🍓👶🍌 YouTube отключает монетизацию ИИ-конвейерам: как алгоритмы платформы внезапно стали главными судьями по авторскому праву Халява официально закончилась. Если ваш бизнес-план на этот год состоял в том, чтобы запустить сетку «безликих» (faceless) каналов, где нейросети сами пишут сценарии, генерируют картинки и монотонно зачитывают их синтетическим голосом — YouTube вас расстроит. Платформа выкатила жесткие обнов

7custom 52088853424421230634👍3🔥1😁1custom 52066802117431004811

18 Jul 2026, 07:32 UTC121 views8 reactionsread 27 August 2026
Photo

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

3👍3😁1custom 52066802117431004811

14 Jul 2026, 07:32 UTC112 views11 reactionsread 27 August 2026
Photo

📏 Размер имеет значение: государство посчитало нейросети и решило, кто из них «настоящий» ИИ Продолжаем погружаться в новый федеральный закон об ИИ. Читаю итоговый текст и радуюсь попыткам измерить математику в штуках. И если вы думаете, что это забота только ИТ-гигантов, то ошибаетесь — это напрямую коснется тех, кто генерирует контент. Разбираемся, кого теперь официально пустят в клуб искусственного интеллекта, а

4custom 52063491470739708963custom 52066802117431004813🔥1

10 Jul 2026, 07:03 UTC397 views12 reactionsread 27 August 2026
Photo

⚖️ После кинофестиваля "Евразия" разбирали с режиссёром Юлией Панковой новый закон об ИИ Спойлер: паника не нужна, но готовиться — стоит. Готовьтесь, будем разбирать кейсы с Юлией и другими экспертами в эту субботу на паблик-токе "ИИ для CG: будущее креативных профессий" от Universal University ➡️ регистрация 🧠 Коротко по фактам · Госдума приняла закон, но не обязала авторов маркировать нейро-ролики. Штрафовать л

5🔥4custom 52066802117431004813

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

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.

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

“Иван Шевелев • Shyft Agency” (@shevelaw), 164 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/shevelaw.

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.