Channel
Софт CaseBattle
@casebt
On this record: Growth · Engagement · Cite this entry
4,665subscribers
-146 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002478648065 |
|---|---|
| Type | Channel |
| Username | @casebt |
| Description | 👉Отзывы - t.me/otzivcasebt 🛡 👉По всем вопросам - @mngrcb 📞 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/casebt |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 22:00 | 4,665 | no change |
| 2 Sept 2026, 17:47 | 4,665 | -19 |
| 31 Aug 2026, 02:53 | 4,684 | -17 |
| 27 Aug 2026, 18:03 | 4,701 | -17 |
| 24 Aug 2026, 08:16 | 4,718 | -16 |
| 21 Aug 2026, 01:16 | 4,734 | -14 |
| 18 Aug 2026, 03:02 | 4,748 | -25 |
| 15 Aug 2026, 00:34 | 4,773 | -24 |
| 11 Aug 2026, 06:52 | 4,797 | -13 |
| 7 Aug 2026, 22:31 | 4,810 | -1 |
| 7 Aug 2026, 18:48 | 4,811 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Софт CaseBattle” (@casebt), 4,665 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/casebt.
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.