Channel
Emad Al-Haffar System
@CEmadAlHaffar
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,040subscribers
-62 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001791069628 |
|---|---|
| Type | Channel |
| Username | @CEmadAlHaffar |
| Created | Between 1 January 2022 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/CEmadAlHaffar |
Topic
Crypto & trading — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 4 Nov 2026, 06:56 | 2,040 | -1 |
| 1 Nov 2026, 11:29 | 2,041 | +1 |
| 29 Oct 2026, 21:57 | 2,040 | -2 |
| 26 Oct 2026, 17:17 | 2,042 | -7 |
| 23 Oct 2026, 11:27 | 2,049 | -2 |
| 17 Oct 2026, 17:29 | 2,051 | -8 |
| 14 Oct 2026, 21:47 | 2,059 | -5 |
| 11 Oct 2026, 09:42 | 2,064 | -8 |
| 4 Oct 2026, 20:40 | 2,072 | -15 |
| 25 Sept 2026, 17:57 | 2,087 | -4 |
| 20 Sept 2026, 00:58 | 2,091 | no change |
| 16 Sept 2026, 19:59 | 2,091 | -5 |
| 12 Sept 2026, 16:19 | 2,096 | -2 |
| 8 Sept 2026, 20:55 | 2,098 | -5 |
| 3 Sept 2026, 23:20 | 2,103 | +1 |
| 3 Sept 2026, 03:30 | 2,102 | 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.
@moh_enshassi1 · 19,192
Telegram ranks this channel #18 of 52 here — alongside 51 others — read 1 October 2026
@wazefa2022 · 25,561
Telegram ranks this channel #31 of 76 here — alongside 75 others — read 13 September 2026
@forex_ab99 · 33,445
Telegram ranks this channel #49 of 80 here — alongside 79 others — read 3 September 2026
@scarehoome · 45,959
Telegram ranks this channel #55 of 55 here — alongside 54 others — read 6 September 2026
@naserbarqawe94 · 30,988
Telegram ranks this channel #61 of 73 here — alongside 72 others — read 13 September 2026
@SUPREMETRADINGSIGNALS · 19,514
Telegram ranks this channel #76 of 82 here — alongside 81 others — read 26 September 2026
This channel appears in 6 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Emad Al-Haffar System” (@CEmadAlHaffar), 2,040 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/CEmadAlHaffar.
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.