Channel
I Go FOREX2
@forexcousres
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,784subscribers
-58 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001677795363 |
|---|---|
| Type | Channel |
| Username | @forexcousres |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/forexcousres |
Topic
Education — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 7 Nov 2026, 05:31 | 1,784 | -4 |
| 4 Nov 2026, 15:16 | 1,788 | -1 |
| 2 Nov 2026, 01:08 | 1,789 | -2 |
| 29 Oct 2026, 15:49 | 1,791 | -2 |
| 26 Oct 2026, 23:25 | 1,793 | -1 |
| 23 Oct 2026, 22:16 | 1,794 | -6 |
| 17 Oct 2026, 17:39 | 1,800 | -1 |
| 14 Oct 2026, 22:35 | 1,801 | -2 |
| 11 Oct 2026, 14:22 | 1,803 | -3 |
| 5 Oct 2026, 11:39 | 1,806 | -3 |
| 27 Sept 2026, 06:37 | 1,809 | +2 |
| 23 Sept 2026, 02:36 | 1,807 | no change |
| 15 Sept 2026, 14:02 | 1,807 | -5 |
| 12 Sept 2026, 05:21 | 1,812 | -3 |
| 8 Sept 2026, 04:16 | 1,815 | -2 |
| 2 Sept 2026, 20:57 | 1,817 | -4 |
| 30 Aug 2026, 14:05 | 1,821 | -6 |
| 27 Aug 2026, 19:57 | 1,827 | -6 |
| 24 Aug 2026, 14:27 | 1,833 | -11 |
| 20 Aug 2026, 20:37 | 1,844 | 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.
@zamerican0english · 100,081
Telegram ranks this channel #12 of 65 here — alongside 64 others — read 17 August 2026
@YourcoursesArabic · 25,324
Telegram ranks this channel #15 of 75 here — alongside 74 others — read 13 September 2026
@yourjop5 · 23,958
Telegram ranks this channel #31 of 60 here — alongside 59 others — read 17 September 2026
@EnglishCourses4Free · 21,048
Telegram ranks this channel #39 of 64 here — alongside 63 others — read 25 September 2026
@jobs233 · 83,709
Telegram ranks this channel #48 of 72 here — alongside 71 others — read 18 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“I Go FOREX2” (@forexcousres), 1,784 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/forexcousres.
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.