Channel
سَوَّاح .
@sooo_0099
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,907subscribers
+15 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001292021506 |
|---|---|
| Type | Channel |
| Username | @sooo_0099 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/sooo_0099 |
Topic
Religion — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 6 Nov 2026, 23:40 | 1,907 | -1 |
| 3 Nov 2026, 23:00 | 1,908 | -3 |
| 31 Oct 2026, 22:16 | 1,911 | +1 |
| 28 Oct 2026, 17:49 | 1,910 | -1 |
| 26 Oct 2026, 03:47 | 1,911 | +5 |
| 23 Oct 2026, 12:57 | 1,906 | +9 |
| 20 Oct 2026, 03:05 | 1,897 | +3 |
| 17 Oct 2026, 10:36 | 1,894 | +1 |
| 14 Oct 2026, 10:21 | 1,893 | -3 |
| 10 Oct 2026, 23:36 | 1,896 | +2 |
| 5 Oct 2026, 01:36 | 1,894 | -9 |
| 25 Sept 2026, 19:56 | 1,903 | -4 |
| 22 Sept 2026, 01:41 | 1,907 | no change |
| 17 Sept 2026, 01:21 | 1,907 | +2 |
| 12 Sept 2026, 17:36 | 1,905 | +5 |
| 8 Sept 2026, 15:16 | 1,900 | +3 |
| 3 Sept 2026, 17:00 | 1,897 | -1 |
| 31 Aug 2026, 10:27 | 1,898 | +3 |
| 28 Aug 2026, 10:48 | 1,895 | +3 |
| 25 Aug 2026, 04:18 | 1,892 | 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.
@ikjzc · 84,760
Telegram ranks this channel #17 of 89 here — alongside 88 others — read 18 August 2026
@mm12a1 · 26,393
Telegram ranks this channel #28 of 77 here — alongside 76 others — read 11 September 2026
@lm_IlI · 21,580
Telegram ranks this channel #41 of 86 here — alongside 85 others — read 21 September 2026
@iisuii · 26,989
Telegram ranks this channel #61 of 86 here — alongside 85 others — read 10 September 2026
@WD_27 · 61,918
Telegram ranks this channel #66 of 88 here — alongside 87 others — read 21 August 2026
This channel appears in 5 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“سَوَّاح .” (@sooo_0099), 1,907 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/sooo_0099.
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.