
Channel
Shalmustbgone
@shalmustbgone
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,244subscribers
-90 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001414015487 |
|---|---|
| Type | Channel |
| Username | @shalmustbgone |
| Created | 25 May 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 17 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/shalmustbgone |
Topic
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 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 12:27 | 2,244 | -2 |
| 2 Nov 2026, 04:31 | 2,246 | -3 |
| 30 Oct 2026, 06:31 | 2,249 | -4 |
| 27 Oct 2026, 07:19 | 2,253 | -4 |
| 24 Oct 2026, 04:20 | 2,257 | -5 |
| 21 Oct 2026, 05:38 | 2,262 | -1 |
| 18 Oct 2026, 09:16 | 2,263 | -3 |
| 15 Oct 2026, 12:40 | 2,266 | -2 |
| 12 Oct 2026, 02:19 | 2,268 | -3 |
| 5 Oct 2026, 13:39 | 2,271 | -6 |
| 27 Sept 2026, 19:17 | 2,277 | -17 |
| 17 Sept 2026, 21:33 | 2,294 | no change |
| 15 Sept 2026, 23:59 | 2,294 | -5 |
| 12 Sept 2026, 12:20 | 2,299 | -6 |
| 8 Sept 2026, 15:54 | 2,305 | -1 |
| 3 Sept 2026, 15:41 | 2,306 | -2 |
| 31 Aug 2026, 13:13 | 2,308 | -5 |
| 28 Aug 2026, 08:28 | 2,313 | -5 |
| 25 Aug 2026, 04:37 | 2,318 | -2 |
| 22 Aug 2026, 11:05 | 2,320 | 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.
Appears in Telegram’s recommendations for other channels
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.
@YerzhanY · 31,765
Telegram ranks this channel #4 of 90 here — alongside 89 others — read 5 September 2026
@obozhau1 · 24,364
Telegram ranks this channel #21 of 91 here — alongside 90 others — read 15 September 2026
@protenge_kz · 20,990
Telegram ranks this channel #23 of 94 here — alongside 93 others — read 25 September 2026
@astanovka98 · 58,927
Telegram ranks this channel #23 of 90 here — alongside 89 others — read 22 August 2026
@qumash_kz · 121,411
Telegram ranks this channel #26 of 91 here — alongside 90 others — read 14 August 2026
@syrymitkulov · 41,822
Telegram ranks this channel #27 of 92 here — alongside 91 others — read 30 August 2026
@kriminal_kazakhstan · 22,942
Telegram ranks this channel #28 of 92 here — alongside 91 others — read 19 September 2026
@kazchuvash · 25,180
Telegram ranks this channel #43 of 94 here — alongside 93 others — read 15 September 2026
@nomadsoul · 54,237
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 24 August 2026
@almatykrispi · 18,732
Telegram ranks this channel #47 of 91 here — alongside 90 others — read 3 October 2026
@vlastkz · 25,533
Telegram ranks this channel #49 of 94 here — alongside 93 others — read 13 September 2026
@sportilinet · 31,530
Telegram ranks this channel #49 of 95 here — alongside 94 others — read 5 September 2026
@kozachkow · 120,954
Telegram ranks this channel #50 of 93 here — alongside 92 others — read 14 August 2026
@ztb_qaz · 174,022
Telegram ranks this channel #50 of 94 here — alongside 93 others — read 12 August 2026
@Zanamiviehali · 63,723
Telegram ranks this channel #52 of 95 here — alongside 94 others — read 21 August 2026
@orda_kz · 128,459
Telegram ranks this channel #53 of 94 here — alongside 93 others — read 13 August 2026
@qogamnews · 22,536
Telegram ranks this channel #54 of 92 here — alongside 91 others — read 20 September 2026
@myastanacity · 19,324
Telegram ranks this channel #57 of 93 here — alongside 92 others — read 2 October 2026
@kerekpv · 29,111
Telegram ranks this channel #57 of 94 here — alongside 93 others — read 8 September 2026
@egovpress · 67,581
Telegram ranks this channel #58 of 97 here — alongside 96 others — read 20 August 2026
@kazakh_inform · 42,745
Telegram ranks this channel #67 of 94 here — alongside 93 others — read 31 August 2026
@alibekovkz · 52,713
Telegram ranks this channel #72 of 91 here — alongside 90 others — read 23 August 2026
@FINANCEkaz · 70,109
Telegram ranks this channel #86 of 94 here — alongside 93 others — read 22 August 2026
This channel appears in 23 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Shalmustbgone” (@shalmustbgone), 2,244 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/shalmustbgone.
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.