Незнание правил не освобождает от ответственности! 🌹 Вы будете заблокированы в чате за: 1. Флуд, в том числе реакциями. Стикер/GIF считается за несколько текстовых сообщений 2. Реклама в любом виде. Исключением является (разрешено): пиар клубов (не чаще 1 раза в день и не больше 256 символов в сообщении) 3. Купля, продажа, обмен товаров и услуг, реферальные ссылки 4. 18+ и шок/треш контент без цензуры в достаточ…
Channel
Правила группы Brawl Stars Datamines | Чат
@bsdchatrules
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,425subscribers
-18 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 | -1001890941352 |
|---|---|
| Type | Channel |
| Username | @bsdchatrules |
| Created | 15 October 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/bsdchatrules |
Topic
Gaming — 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 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 17:21 | 1,425 | +21 |
| 5 Oct 2026, 10:02 | 1,404 | +2 |
| 27 Sept 2026, 17:55 | 1,402 | -27 |
| 18 Sept 2026, 01:01 | 1,429 | +1 |
| 13 Sept 2026, 20:15 | 1,428 | +7 |
| 10 Sept 2026, 04:39 | 1,421 | +22 |
| 4 Sept 2026, 17:58 | 1,399 | -9 |
| 31 Aug 2026, 18:08 | 1,408 | -1 |
| 28 Aug 2026, 12:06 | 1,409 | -6 |
| 25 Aug 2026, 04:23 | 1,415 | -5 |
| 22 Aug 2026, 01:49 | 1,420 | -4 |
| 18 Aug 2026, 16:25 | 1,424 | -4 |
| 15 Aug 2026, 19:06 | 1,428 | -12 |
| 12 Aug 2026, 02:12 | 1,440 | -7 |
| 8 Aug 2026, 15:43 | 1,447 | +4 |
| 7 Aug 2026, 22:02 | 1,443 | no change |
| 7 Aug 2026, 16:15 | 1,443 | first reading |
Engagement
2 posts held, back to 15 October 2022 — 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 2 posts for this entry, the most recent from 16 January 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @bsdchatrules. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Правила группы Brawl Stars Datamines | Чат” (@bsdchatrules), 1,425 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/bsdchatrules.
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.