Channel
@zavorotami
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,715subscribers
+132 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001356061174 |
|---|---|
| Type | Channel |
| Username | @zavorotami |
| Created | 21 April 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zavorotami |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 19:17 | 1,715 | +7 |
| 13 Sept 2026, 05:58 | 1,708 | +12 |
| 9 Sept 2026, 14:39 | 1,696 | +40 |
| 4 Sept 2026, 07:38 | 1,656 | +3 |
| 31 Aug 2026, 10:36 | 1,653 | +5 |
| 28 Aug 2026, 11:04 | 1,648 | +61 |
| 25 Aug 2026, 00:53 | 1,587 | +1 |
| 18 Aug 2026, 18:05 | 1,586 | +2 |
| 16 Aug 2026, 04:14 | 1,584 | -1 |
| 10 Aug 2026, 01:41 | 1,585 | +2 |
| 6 Aug 2026, 07:33 | 1,583 | no change |
| 6 Aug 2026, 07:23 | 1,583 | first reading |
9 posts held, back to 17 June 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 2 pages 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 9 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
1,256 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 43.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235956830546466279 | 540 | 43.0% | |
| custom 5233684590983419201 | 244 | 19.4% | |
| custom 5233475292932117650 | 167 | 13.3% | |
| custom 5238144283160121720 | 137 | 10.9% | |
| custom 5235452631450684320 | 77 | 6.13% | |
| custom 5233504262486527308 | 53 | 4.22% | |
| custom 5233192821522994747 | 38 | 3.03% |
Custom emoji. Every row above is a 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 9 of the 9 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 1,256 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 17 June 2026 to 29 July 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.
Традиции не объясняют — их передают. 📍Архангельск'26
custom 523595683054646627951custom 523368459098341920119custom 52334752929321176509custom 52335042624865273083
Всем бодрого и продуктивного дня от нашего брата с передовой🤙🏻
custom 523595683054646627978custom 523814428316012172023custom 523545263145068432012custom 52336845909834192016custom 52335042624865273081
📍Ниагарский водопад
custom 523595683054646627961custom 523368459098341920122custom 523814428316012172012
Бейся за ЦСКА 👊🏻
custom 523347529293211765074custom 523595683054646627945custom 523368459098341920132custom 523814428316012172013custom 52335042624865273086custom 52354526314506843205custom 52331928215229947472
Страханеᛏ
custom 523595683054646627996custom 523814428316012172044custom 523319282152299474715custom 52354526314506843209custom 52336845909834192016custom 52335042624865273081
ТОЛЬКО ЮГЕНД!
custom 5235956830546466279181custom 523545263145068432046custom 523814428316012172039custom 52336845909834192019custom 52331928215229947476custom 52335042624865273081
Наскребли копейку и все-таки нарисовали кусок. С Днем Рождения нас! Отдельное спасибо братве из Картеля и Джолли за содействие на стене, проведенное время, помощь с носилками и за то, что не дали вновь пропить общак и притащили сливовицу. Спасибо за все! А также глубочайшая благодарность красно-белым ультрас, которые внесли свой вклад и любезно поделились краской. Слава ЦСКА! Bad Company - 12 лет!
custom 523368459098341920156custom 523595683054646627926custom 523319282152299474713custom 52334752929321176506custom 52335042624865273085custom 52354526314506843203custom 52381442831601217201
В любом месте одно и то же.
custom 523347529293211765053custom 523368459098341920126custom 523350426248652730811custom 52331928215229947471custom 52354526314506843201custom 52359568305464662791custom 52381442831601217201
•ВЕСЕННЯЯ ПОДБОРКА• Уже началось лето, а у нас осталось много не опубликованного контента. Поэтому ловите небольшую подборку Весной и покатались на выезда, и отметились качественным перфомансом в стане врага, знатно угарели на юбилее у парней из Бульдогов и много чего другого1️⃣2️⃣ А уже скоро расскажем о подготовке текстовика «100% ЦСКА» и о том, что нужно делать, чтобы перфомансы не рвались 😉 ЦСКА …
custom 523368459098341920168custom 523347529293211765025custom 523350426248652730825custom 52381442831601217204custom 52331928215229947471custom 52354526314506843201custom 52359568305464662791
Showing the 9 most recent of 9 posts we hold for @zavorotami. 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“За воротами” (@zavorotami), 1,715 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zavorotami.
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.