
Channel
Dark world Mql4 coding
@DarkworldMql4coding
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,871subscribers
-72 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 | -1001816878752 |
|---|---|
| Type | Channel |
| Username | @DarkworldMql4coding |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/DarkworldMql4coding |
Topic
Technology — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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:02 | 1,871 | -2 |
| 2 Nov 2026, 18:17 | 1,873 | -1 |
| 31 Oct 2026, 00:19 | 1,874 | -3 |
| 28 Oct 2026, 00:01 | 1,877 | -2 |
| 24 Oct 2026, 22:27 | 1,879 | -3 |
| 18 Oct 2026, 16:56 | 1,882 | -2 |
| 16 Oct 2026, 03:37 | 1,884 | -1 |
| 13 Oct 2026, 07:51 | 1,885 | -13 |
| 6 Oct 2026, 20:16 | 1,898 | -3 |
| 29 Sept 2026, 18:38 | 1,901 | -12 |
| 22 Sept 2026, 01:24 | 1,913 | no change |
| 19 Sept 2026, 07:58 | 1,913 | -2 |
| 15 Sept 2026, 04:38 | 1,915 | -5 |
| 11 Sept 2026, 21:20 | 1,920 | -10 |
| 7 Sept 2026, 17:36 | 1,930 | -3 |
| 2 Sept 2026, 10:07 | 1,933 | -2 |
| 30 Aug 2026, 12:54 | 1,935 | -7 |
| 27 Aug 2026, 16:36 | 1,942 | -1 |
| 26 Aug 2026, 21:30 | 1,943 | 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.
@forexsignals · 172,107
Telegram ranks this channel #51 of 56 here — alongside 55 others — read 26 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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.
“Dark world Mql4 coding” (@DarkworldMql4coding), 1,871 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/DarkworldMql4coding.
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.