New link to projects: https://malwarecorp.com Private: @MalwarePrivateBot
![Telegram profile photo for Crack Cloud [link]](https://cdn.tgregister.com/av/a7/a7ce14dc44699c1342b5ab9ac14cec984c25f19a675f177df02b0ed39ad26350.jpg)
Channel
Crack Cloud [link]
@dark_cloud
On this record: Topic · Growth · Engagement · Posts · Cite this entry
139subscribers
+21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003411383599 |
|---|---|
| Type | Channel |
| Usernames | @crackcloud @dark_cloud |
| Created | 18 December 2025 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/dark_cloud |
Topic
Hacking & security — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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 |
|---|---|---|
| 11 Oct 2026, 12:00 | 139 | +1 |
| 7 Oct 2026, 20:17 | 138 | +5 |
| 1 Oct 2026, 17:41 | 133 | +2 |
| 27 Sept 2026, 07:41 | 131 | +1 |
| 14 Sept 2026, 15:56 | 130 | no change |
| 9 Sept 2026, 19:38 | 130 | +3 |
| 6 Sept 2026, 05:22 | 127 | +1 |
| 31 Aug 2026, 14:42 | 126 | no change |
| 29 Aug 2026, 05:05 | 126 | +1 |
| 25 Aug 2026, 02:04 | 125 | no change |
| 22 Aug 2026, 20:39 | 125 | +3 |
| 16 Aug 2026, 17:38 | 122 | +1 |
| 14 Aug 2026, 16:17 | 121 | +2 |
| 9 Aug 2026, 04:17 | 119 | no change |
| 7 Aug 2026, 12:59 | 119 | no change |
| 7 Aug 2026, 10:20 | 119 | +1 |
| 6 Aug 2026, 21:16 | 118 | first reading |
Engagement
3 posts held, back to 18 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 18 December 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
Link: https://t.me/+NIrQOeX3-yIwMjRi Shop: @MalwareShopRobot New link to projects: malwarecorp.com Groups: malwarecorp.com#groups Markets: malwarecorp.com#markets Private: @MalwarePrivateBot https://t.me/+TPaO72bPdZ1lY2Y0 Ads: malwarecorp.com#ads
Channel created
Showing the 3 most recent of 3 posts we hold for @dark_cloud. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Crack Cloud [link]” (@dark_cloud), 139 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/dark_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.