Channel
SUURTAGAL JACEYL 26
@musalsalcusubsuurtagaljaceyl
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
94,334subscribers
+7,593 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002108689719 |
|---|---|
| Type | Channel |
| Username | @musalsalcusubsuurtagaljaceyl |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/musalsalcusubsuurtagaljaceyl |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 25 Sept 2026, 13:39 | 94,334 | +1,162 |
| 18 Sept 2026, 22:01 | 93,172 | +1,582 |
| 16 Sept 2026, 14:22 | 91,590 | +4 |
| 14 Sept 2026, 20:41 | 91,586 | -21 |
| 13 Sept 2026, 07:55 | 91,607 | -24 |
| 11 Sept 2026, 07:57 | 91,631 | -69 |
| 8 Sept 2026, 14:17 | 91,700 | +1,242 |
| 5 Sept 2026, 07:55 | 90,458 | -134 |
| 3 Sept 2026, 10:24 | 90,592 | +1,332 |
| 2 Sept 2026, 05:42 | 89,260 | -40 |
| 1 Sept 2026, 02:08 | 89,300 | -18 |
| 31 Aug 2026, 01:37 | 89,318 | -70 |
| 30 Aug 2026, 04:47 | 89,388 | -12 |
| 29 Aug 2026, 06:13 | 89,400 | -52 |
| 28 Aug 2026, 04:45 | 89,452 | -49 |
| 27 Aug 2026, 01:56 | 89,501 | -12 |
| 25 Aug 2026, 22:54 | 89,513 | -52 |
| 24 Aug 2026, 23:43 | 89,565 | +1,518 |
| 23 Aug 2026, 10:25 | 88,047 | -62 |
| 21 Aug 2026, 22:37 | 88,109 | first reading |
Engagement
No public post preview. We read this entry on 16 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
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.
@kurulus_orhan_afsoomali · 129,179
Telegram ranks this channel #3 of 23 here — alongside 22 others — read 16 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“SUURTAGAL JACEYL 26” (@musalsalcusubsuurtagaljaceyl), 94,334 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/musalsalcusubsuurtagaljaceyl.
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.