Channel
الشيخ شعبان الصياد
@Syyyadd
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,161subscribers
+140 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001730859294 |
|---|---|
| Type | Channel |
| Username | @Syyyadd |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Syyyadd |
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 14 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 15:29 | 3,161 | +2 |
| 2 Nov 2026, 20:17 | 3,159 | +9 |
| 30 Oct 2026, 23:05 | 3,150 | +3 |
| 27 Oct 2026, 19:27 | 3,147 | +2 |
| 24 Oct 2026, 21:00 | 3,145 | +16 |
| 21 Oct 2026, 19:01 | 3,129 | +9 |
| 18 Oct 2026, 22:00 | 3,120 | +4 |
| 15 Oct 2026, 18:46 | 3,116 | +5 |
| 12 Oct 2026, 09:02 | 3,111 | +8 |
| 6 Oct 2026, 01:18 | 3,103 | +18 |
| 28 Sept 2026, 22:21 | 3,085 | +15 |
| 18 Sept 2026, 19:18 | 3,070 | +2 |
| 14 Sept 2026, 01:20 | 3,068 | +10 |
| 11 Sept 2026, 00:14 | 3,058 | no change |
| 10 Sept 2026, 03:16 | 3,058 | +13 |
| 5 Sept 2026, 02:01 | 3,045 | +5 |
| 1 Sept 2026, 14:54 | 3,040 | -2 |
| 29 Aug 2026, 21:44 | 3,042 | +19 |
| 26 Aug 2026, 17:43 | 3,023 | +2 |
| 26 Aug 2026, 05:45 | 3,021 | 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.
@telawat_khasheaa · 22,748
Telegram ranks this channel #8 of 87 here — alongside 86 others — read 23 September 2026
@Elbahtimy · 19,504
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 4 October 2026
@tlawaaaaaat · 25,615
Telegram ranks this channel #40 of 91 here — alongside 90 others — read 15 September 2026
@ktab7 · 60,945
Telegram ranks this channel #61 of 68 here — alongside 67 others — read 26 August 2026
This channel appears in 4 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.
“الشيخ شعبان الصياد” (@Syyyadd), 3,161 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Syyyadd.
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.