Channel
@SorokinCoach
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
97subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002047696028 |
|---|---|
| Type | Channel |
| Username | @SorokinCoach |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/SorokinCoach |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 12:01 | 97 | no change |
| 7 Aug 2026, 12:07 | 97 | first reading |
13 posts held, back to 13 March 2025 — the 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 13 posts for this entry, the most recent from 16 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
Measured directly from 4 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.
77 reactions across 11 posts, in 14 distinct kinds. The most used accounts for 31.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 24 | 31.2% | |
| ❤ | 13 | 16.9% | |
| 🤣 | 11 | 14.3% | |
| 😁 | 10 | 13.0% | |
| 👍 | 4 | 5.19% | |
| 💯 | 4 | 5.19% | |
| 🍌 | 2 | 2.60% | |
| 👏 | 2 | 2.60% | |
| 😐 | 2 | 2.60% | |
| 🏆 | 1 | 1.30% | |
| 💔 | 1 | 1.30% | |
| 😎 | 1 | 1.30% | |
| 🤓 | 1 | 1.30% | |
| 🤡 | 1 | 1.30% |
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 11 of the 13 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 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 13 March 2025 to 16 February 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.
Курага это не только потому что вкусно с кашей залетает, это один из самых богатых калием продуктов. Зачем? Да чтобы не узнать, что такое эналаприл раньше времени от терапевта или другого какого врача. Мотору нашему всегда нужна будет забота, так вот мнение такого, что 4 грамма калия станут отличным вариантом профилактики, набирать которые лучше всего из продуктов разумеется. Кстати, спортсмены за ночь теряют окол…
❤2👏2🔥2
Photo, posted without a caption
❤1🤣1
❗️❗️❗️Амплитуда решает, полная амплитуда в выигрыше как в случае развития силы, так и в случае сохранения здоровья вашего суставо-связочного аппарата. ❗️❗️❗️Тренировки с полной амплитудой гарантируют, что сустав будет двигаться в полной амплитуде без каких либо ограничений, а это в свою очередь дает возможность для питания хрящевой ткани, для укрепления связок и сухожилий, для улучшения подвижности суставов, для про…
❤7👍1🔥1
Календарь на групповой этап сезона 2026
🔥3🏆1
Для тех кто переживает за Евгеньйо и его колено, потому что мы покой обменяли на нагрузку Кстати уже на 140 осиляет, как нибудь засниму
Х времени назад мой подопечный словил рецидив, собственная связка колена вновь пострадала, но ни то чтобы в баскетболе это редкость 🙃 Так вот, с коленом как видите, все уже почти прекрасно, есть вопросы к паттерну латерального торможения и торможения в целом, но я обязательно смогу пофиксить и это тоже 👌 Но я сделал одно очень важное открытие, нет, я знал это и ранее, но отчасти забыл или отодвинул это в ящик стола…
🔥2
Как же неожиданно (в рамках качалки разве что), если я скажу, что неповоротливый полуфабрикат не может быть атлетом глобально 🙃 Что это значит? Я говорю о всестороннем развитии физических навыков, ведь штангу трогает и легкоатлет, и игровик, и пловец 🫣 Вот только обратно стрелочка не поворачивается, что указывает на отсутствие гармонии в развитии. Стремитесь быть универсальными 🤝
🔥6
Photo, posted without a caption
🤣10
Сколько можно защищать омегу и пытаться убедить остальных, что полезнее только чистый воздух в деревне? Вот ещё материал, почему лучше не тратить свои шекели https://www.ahajournals.org/doi/full/10.1161/CIRCULATIONAHA.121.055654 В кратце, если переводчик не ваш выбор: прием 1 грамма добавки вызывал аритмию чаще 😀 Все еще хочешь защищать сердце этим?
🔥3🤓1😎1
Photo, posted without a caption
🍌2👍2🔥2🤡1
Дали жизни ногам
Сегодня пыхтела, старалась 😮💨🤝🏼 Через не хочу, через не могу, сначала поною, но потом все равно делаю 😂🤭🙇🏻♀️
🔥5❤2💯2👍1
Showing the 12 most recent of 13 posts we hold for @SorokinCoach. 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.
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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Качалка на диване|SorokinCoach” (@SorokinCoach), 97 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/SorokinCoach.
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.