Channel
مكتبه فوركساوي
@ForexawyPdf
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,019subscribers
-9 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001418435431 |
|---|---|
| Type | Channel |
| Username | @ForexawyPdf |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/ForexawyPdf |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 |
|---|---|---|
| 3 Nov 2026, 19:59 | 3,019 | -6 |
| 31 Oct 2026, 17:36 | 3,025 | -6 |
| 29 Oct 2026, 02:40 | 3,031 | -1 |
| 22 Oct 2026, 22:29 | 3,032 | -3 |
| 20 Oct 2026, 00:58 | 3,035 | +5 |
| 17 Oct 2026, 00:57 | 3,030 | -4 |
| 13 Oct 2026, 14:09 | 3,034 | -1 |
| 7 Oct 2026, 08:57 | 3,035 | -3 |
| 19 Sept 2026, 12:38 | 3,038 | +3 |
| 15 Sept 2026, 10:17 | 3,035 | +10 |
| 11 Sept 2026, 17:15 | 3,025 | +2 |
| 11 Sept 2026, 13:39 | 3,023 | no change |
| 6 Sept 2026, 20:00 | 3,023 | +9 |
| 2 Sept 2026, 11:44 | 3,014 | -6 |
| 30 Aug 2026, 14:49 | 3,020 | -1 |
| 27 Aug 2026, 16:13 | 3,021 | -3 |
| 24 Aug 2026, 17:12 | 3,024 | -5 |
| 20 Aug 2026, 19:53 | 3,029 | -1 |
| 18 Aug 2026, 04:42 | 3,030 | +5 |
| 14 Aug 2026, 20:06 | 3,025 | 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.
@fedniy · 244,278
Telegram ranks this channel #13 of 73 here — alongside 72 others — read 10 August 2026
@prccourses · 35,988
Telegram ranks this channel #17 of 54 here — alongside 53 others — read 1 September 2026
@hossamelmowafy · 18,987
Telegram ranks this channel #43 of 66 here — alongside 65 others — read 4 October 2026
@AlattarrTrading · 25,440
Telegram ranks this channel #68 of 76 here — alongside 75 others — read 17 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“مكتبه فوركساوي” (@ForexawyPdf), 3,019 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/ForexawyPdf.
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.