Заняли второе место на BRO CUP в Алматы. Залутали чуть VRS, а самое главное материал и мысли, с которыми нужно работать дальше. По игре ощущения смешанные, много не доигрываем простых ситуаций
custom 53639781877536703188🏆2custom 54699707006493784691

Channel
@bullet_cs2
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,149subscribers
-16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001656479589 |
|---|---|
| Type | Channel |
| Username | @bullet_cs2 |
| Created | 22 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/bullet_cs2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 23:35 | 1,149 | +6 |
| 3 Sept 2026, 06:34 | 1,143 | -3 |
| 30 Aug 2026, 19:03 | 1,146 | +3 |
| 27 Aug 2026, 13:25 | 1,143 | -4 |
| 24 Aug 2026, 03:16 | 1,147 | -3 |
| 20 Aug 2026, 15:54 | 1,150 | -15 |
| 17 Aug 2026, 11:53 | 1,165 | +2 |
| 14 Aug 2026, 02:18 | 1,163 | -2 |
| 11 Aug 2026, 02:17 | 1,165 | +1 |
| 7 Aug 2026, 20:53 | 1,164 | -1 |
| 7 Aug 2026, 06:16 | 1,165 | first reading |
10 posts held, back to 25 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 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 10 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
88 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 40.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 36 | 40.9% | |
| 🏆 | 19 | 21.6% | |
| custom 5240103436787133470 | 16 | 18.2% | |
| custom 5363978187753670318 | 16 | 18.2% | |
| custom 5469970700649378469 | 1 | 1.14% |
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 10 of the 10 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 88 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 25 July 2026 to 2 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.
Заняли второе место на BRO CUP в Алматы. Залутали чуть VRS, а самое главное материал и мысли, с которыми нужно работать дальше. По игре ощущения смешанные, много не доигрываем простых ситуаций
custom 53639781877536703188🏆2custom 54699707006493784691
Вышли 2-0 во второй игровой день
🏆8🔥2custom 53639781877536703181
Все матчи нашей команды будут транслироваться на официальном YouTube-канале организации. Возможно, будут и другие трансляции, но если хотите поддержать нас - залетайте на наш стрим: https://www.youtube.com/watch?v=mdwiDf77VUI
custom 52401034367871334702🏆1🔥1custom 53639781877536703181
Завтра стартует второй лан для нашей команды. Было не так много времени на подготовку в связи с перелетами и трансфером из Павлодара в Астану, откуда мы вылетали сюда. Работали в ударном режиме, постараемся выложиться на максимум
🏆4🔥2custom 52401034367871334701
Кстати, если что, Деко заскаутил его
🔥8custom 52401034367871334705
Чуть фотографий с прошедшего турнира в г. Павлодар 🇰🇿
🔥9custom 52401034367871334704
Прилетели в Алматы на BRO SUMMER CUP 2026 Есть несколько дней на подготовку перед стартом. Спасибо нашей организации за то, что создала все необходимые условия для этого небольшого киберспортивного турне по Центральной Азии. Сейчас остается хорошо поработать и постараться показать достойный результат на этом турнире. После нас ждет еще один лан в Ташкенте
🏆2
Командный завтрак перед церемонией награждения, которая пройдет сегодня на набережной Павлодара. Турнир был приурочен ко Дню города. В целом получилась хорошая неделя. Конечно, результат нас не устраивает - всегда хочется бороться за самые высокие места. Но такие турниры тоже дают много информации: стало понятно, над чем нужно работать в первую очередь, где команда уже выглядит уверенно, а где пока не хватает стабил…
🔥8custom 53639781877536703186
Photo, posted without a caption
🔥6🏆2custom 52401034367871334701
Закончили лан в Павлодаре на 3-4 месте. За день сыграли 1 бо1 и 3 бо3. Проиграли в ходе турнира Rune Eaters и NOVAQ. Следующий лан через неделю в Алматы, есть чуть времени, чтобы поработать над ошибками
custom 52401034367871334703
Showing the 10 most recent of 10 posts we hold for @bullet_cs2. 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.
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.
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 2 seed channels' Telegram-generated recommendation lists 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“bullet CS2” (@bullet_cs2), 1,149 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/bullet_cs2.
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.