Channel
@bruskas_proxy
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
8,675subscribers
-597 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002380651418 |
|---|---|
| Type | Channel |
| Username | @bruskas_proxy |
| Created | 9 September 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/bruskas_proxy |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 04:28 | 8,675 | -26 |
| 31 Oct 2026, 21:29 | 8,701 | -19 |
| 29 Oct 2026, 05:00 | 8,720 | -19 |
| 26 Oct 2026, 04:10 | 8,739 | -28 |
| 22 Oct 2026, 23:16 | 8,767 | -22 |
| 20 Oct 2026, 00:30 | 8,789 | -19 |
| 16 Oct 2026, 22:56 | 8,808 | -26 |
| 13 Oct 2026, 14:58 | 8,834 | -40 |
| 7 Oct 2026, 11:16 | 8,874 | -43 |
| 30 Sept 2026, 22:20 | 8,917 | -91 |
| 16 Sept 2026, 09:37 | 9,008 | -24 |
| 12 Sept 2026, 10:16 | 9,032 | -22 |
| 8 Sept 2026, 13:37 | 9,054 | -42 |
| 3 Sept 2026, 00:15 | 9,096 | -13 |
| 30 Aug 2026, 22:48 | 9,109 | -25 |
| 27 Aug 2026, 15:35 | 9,134 | -27 |
| 24 Aug 2026, 08:18 | 9,161 | -27 |
| 20 Aug 2026, 07:46 | 9,188 | -14 |
| 17 Aug 2026, 18:34 | 9,202 | -27 |
| 14 Aug 2026, 11:45 | 9,229 | first reading |
2 posts held, back to 9 September 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 36 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 2 posts for this entry, the most recent from 31 October 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 November 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.
РЕЗЕРВ КАНАЛ, здесь не будет публиковаться реклама, новости, этот канал активизируется только при условии что основной пропадет, надеюсь такого не будет, просто подпишитесь и забудьте про него!!! /////////////////////////////////////////////////////////////////// RESERVE CHANNEL, here will not publish advertising, news, this channel will be activated only if the main channel will disappear, I hope this will not hap…
Channel created
Showing the 2 most recent of 2 posts we hold for @bruskas_proxy. 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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“BRUSKAS REZERV” (@bruskas_proxy), 8,675 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/bruskas_proxy.
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.