Channel
🌨 | 𝐃𝐱𝐜𝐤 𝐂𝐥𝐨𝐮𝐝™
@dxck_cloud
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
987subscribers
-46 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002004967065 |
|---|---|
| Type | Channel |
| Username | @dxck_cloud |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 October 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/dxck_cloud |
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 9 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 23 Oct 2026, 03:11 | 987 | -9 |
| 15 Oct 2026, 06:28 | 996 | -1 |
| 9 Oct 2026, 04:17 | 997 | no change |
| 8 Oct 2026, 11:37 | 997 | -2 |
| 27 Sept 2026, 13:17 | 999 | -14 |
| 15 Sept 2026, 13:19 | 1,013 | -3 |
| 11 Sept 2026, 21:56 | 1,016 | -4 |
| 7 Sept 2026, 18:59 | 1,020 | -4 |
| 2 Sept 2026, 09:03 | 1,024 | -3 |
| 30 Aug 2026, 09:46 | 1,027 | -4 |
| 24 Aug 2026, 11:34 | 1,031 | -3 |
| 20 Aug 2026, 12:06 | 1,034 | +1 |
| 17 Aug 2026, 19:39 | 1,033 | +2 |
| 15 Aug 2026, 00:38 | 1,031 | -2 |
| 11 Aug 2026, 11:45 | 1,033 | 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.
@Faravahr_phonk · 65,672
Telegram ranks this channel #10 of 73 here — alongside 72 others — read 21 August 2026
@D_aYVpN · 36,300
Telegram ranks this channel #34 of 62 here — alongside 61 others — read 31 August 2026
@Tusan_Vpn · 26,161
Telegram ranks this channel #37 of 61 here — alongside 60 others — read 12 September 2026
@SAVTeaM · 249,937
Telegram ranks this channel #49 of 69 here — alongside 68 others — read 11 August 2026
@AuschwitzMeme · 19,046
Telegram ranks this channel #58 of 63 here — alongside 62 others — read 1 October 2026
@mehti_yahyavi · 93,651
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 18 August 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“🌨 | 𝐃𝐱𝐜𝐤 𝐂𝐥𝐨𝐮𝐝™” (@dxck_cloud), 987 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/dxck_cloud.
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.