Channel
FuturesDASH
@FuturesDASH1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,263subscribers
-113 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001572610555 |
|---|---|
| Type | Channel |
| Username | @FuturesDASH1 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/FuturesDASH1 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 06:55 | 3,263 | -10 |
| 12 Sept 2026, 11:41 | 3,273 | -16 |
| 9 Sept 2026, 20:06 | 3,289 | no change |
| 8 Sept 2026, 09:01 | 3,289 | -14 |
| 3 Sept 2026, 13:16 | 3,303 | -11 |
| 31 Aug 2026, 09:28 | 3,314 | -4 |
| 28 Aug 2026, 11:34 | 3,318 | -1 |
| 25 Aug 2026, 18:52 | 3,319 | -25 |
| 22 Aug 2026, 15:18 | 3,344 | -5 |
| 19 Aug 2026, 15:32 | 3,349 | -12 |
| 16 Aug 2026, 07:12 | 3,361 | -15 |
| 15 Aug 2026, 05:45 | 3,376 | 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.
@wo_future · 59,087
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 19 August 2026
@Gulf_Pump · 38,044
Telegram ranks this channel #16 of 78 here — alongside 77 others — read 31 August 2026
@cryptochat22 · 104,722
Telegram ranks this channel #19 of 80 here — alongside 79 others — read 31 August 2026
@Abushahincrypto · 139,864
Telegram ranks this channel #34 of 81 here — alongside 80 others — read 15 August 2026
@m2zealaa · 32,798
Telegram ranks this channel #50 of 72 here — alongside 71 others — read 3 September 2026
@Cryptocurrencyy9 · 70,292
Telegram ranks this channel #66 of 83 here — alongside 82 others — read 20 August 2026
@the_future_111 · 42,179
Telegram ranks this channel #71 of 93 here — alongside 92 others — read 29 August 2026
This channel appears in 7 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“FuturesDASH” (@FuturesDASH1), 3,263 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/FuturesDASH1.
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.