Channel
Elwalid ICT
@Elwalid_ict
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,191subscribers
-61 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001539019804 |
|---|---|
| Type | Channel |
| Username | @Elwalid_ict |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Elwalid_ict |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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, 01:16 | 2,191 | -3 |
| 1 Nov 2026, 14:31 | 2,194 | -5 |
| 29 Oct 2026, 19:50 | 2,199 | -2 |
| 26 Oct 2026, 20:27 | 2,201 | -4 |
| 23 Oct 2026, 14:56 | 2,205 | -3 |
| 21 Oct 2026, 01:10 | 2,208 | -4 |
| 17 Oct 2026, 19:08 | 2,212 | -4 |
| 14 Oct 2026, 09:56 | 2,216 | -1 |
| 11 Oct 2026, 04:37 | 2,217 | -10 |
| 5 Oct 2026, 08:19 | 2,227 | -5 |
| 27 Sept 2026, 08:56 | 2,232 | +6 |
| 18 Sept 2026, 14:47 | 2,226 | no change |
| 18 Sept 2026, 00:00 | 2,226 | -2 |
| 13 Sept 2026, 18:15 | 2,228 | -1 |
| 10 Sept 2026, 03:41 | 2,229 | -6 |
| 5 Sept 2026, 00:39 | 2,235 | -1 |
| 1 Sept 2026, 04:14 | 2,236 | -7 |
| 29 Aug 2026, 11:38 | 2,243 | -1 |
| 26 Aug 2026, 20:43 | 2,244 | -3 |
| 24 Aug 2026, 01:25 | 2,247 | 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.
@corses0 · 73,326
Telegram ranks this channel #59 of 84 here — alongside 83 others — read 19 August 2026
@tradingxp1 · 22,902
Telegram ranks this channel #71 of 81 here — alongside 80 others — read 17 September 2026
@KO_R17 · 30,204
Telegram ranks this channel #73 of 77 here — alongside 76 others — read 8 September 2026
@fisal_alswadi · 36,760
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 1 September 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.
“Elwalid ICT” (@Elwalid_ict), 2,191 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Elwalid_ict.
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.