Dragon Web Panel 完全远程访问 完全旁路且自动 📞Dragon Support. @Mr2x8 https://t.me/+fnwedix-e80wODQ0

Channel
CraxsRAT v7.7
@CraxsRAT2021
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
413subscribers
+37 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002422542623 |
|---|---|
| Type | Channel |
| Username | @CraxsRAT2021 |
| Created | 28 May 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/CraxsRAT2021 |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 27 Oct 2026, 19:46 | 413 | +1 |
| 20 Oct 2026, 14:39 | 412 | +2 |
| 13 Oct 2026, 03:19 | 410 | +3 |
| 2 Oct 2026, 14:01 | 407 | +18 |
| 4 Sept 2026, 07:20 | 389 | -1 |
| 28 Aug 2026, 11:34 | 390 | +8 |
| 21 Aug 2026, 09:36 | 382 | -3 |
| 15 Aug 2026, 10:04 | 385 | +9 |
| 8 Aug 2026, 06:17 | 376 | no change |
| 7 Aug 2026, 19:02 | 376 | first reading |
Engagement
13 posts held, back to 28 May 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 1 page 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 13 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 19s
- Average length
- 46s
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
12 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍾 | 9 | 75.0% | |
| ❤ | 3 | 25.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 5 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 28 May 2025 to 24 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
DragonRAT update 7.4.1 🇬🇧Dragon update 7.4.1 has been released Press the update button from the settings section People who buy the source code can contact us for updates 📞夏延 Шайенн 🇨🇳龙更新7.4.1已发布 按设置部分的更新按钮 购买源码的朋友可以联系我们获取更新 📞 夏延 Шайенн --------------------------------------------- 🇨🇳🇬🇧🇫🇷🇧🇷🇸🇦🇹🇷🇮🇳 Can be used in all countries, all languages are completely bypassed and accesses are activated automatically
🍾1
新 DragonRAT v7.4 2026 更新 远程访问手机 APK被完全绕过 Google Play 病毒检测天线 兼容所有手机 🇨🇳🇺🇸🇧🇷🇵🇰🇮🇶🇲🇾🇰🇷🇿🇦🇷🇺🇸🇬🇯🇵🇮🇳🏴☠ DragonRAT v7.4 New Update 2026 Remote mobile access Completely bypassed APK Google Play virus detection antenna Compatible with all mobile phones More information👇
Dragon RAT v7.3. 🇺🇸🇬🇧 Can be used on Windows and Android The most complete Android remote Update 2026 includes pine options Adding all languages to the tool - from now on you can change the tool to your desired language Update - Bypass the security shield of Google Play and the security shield of banking apps completely bypassed Update - now by injecting your payload, it becomes undetectable by the virus an…
🍾4
https://t.me/+D9vjzEqeYQxiYTg0 👆最新版本 2026 兼容所有手机 无需人工干预即可自动远程启动 🟢 online t.me/Error403x
原始源代码 BTMOB /我们为您提供个性化服务 更改图标 更改姓名 颜色变化 添加语言 我会为您修改原始源代码 📞Contact us @Error403x
🍾1
Source code BTMOB RAT 3.6.3 Original source code 📞Contact us @Error403x
Join http://t.me/Spy2025robot Technology lovers, become a member.👆
DragonRAT 🐉 远程安卓黑客工具 Android Hack. Remote
Dragon远悾功能特点 Android Hack
🇬🇧Trouble-free remote mobile phone service 🇨🇳无故障远程手机服务 Dragon rat CraxsـRAT IMRAT 安卓APP管理系统 tremendous botnet Eagle spy G700 Octopus rat RhinoRAT ------------------ t.me/spyCraxsRAT ---------------- Bypass Google Play Inject your virus into any app Bypass banking apps 联系我📞 Contact me t.me/Error403x
❤3
https://t.me/+bKer1AjxzQ9hOGU0 Join to craxsrat
🍾3
Showing the 12 most recent of 13 posts we hold for @CraxsRAT2021. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“CraxsRAT v7.7” (@CraxsRAT2021), 413 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/CraxsRAT2021.
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.