别催了
👍34❤3🕊1
Signed iokhd

Channel
@RTdrivers
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
112,098subscribers
+11,167 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002399412728 |
|---|---|
| Type | Channel |
| Username | @RTdrivers |
| Description | RT完美驱动发布交流群@RTdriverschat 驱动仅供开发测试使用 严禁用于违法用途 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/RTdrivers |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 08:17 | 112,098 | +1,639 |
| 17 Sept 2026, 13:57 | 110,459 | +398 |
| 15 Sept 2026, 11:41 | 110,061 | +336 |
| 13 Sept 2026, 22:59 | 109,725 | +586 |
| 12 Sept 2026, 05:54 | 109,139 | +332 |
| 9 Sept 2026, 22:20 | 108,807 | +281 |
| 6 Sept 2026, 15:19 | 108,526 | +427 |
| 4 Sept 2026, 03:56 | 108,099 | +175 |
| 2 Sept 2026, 18:54 | 107,924 | +249 |
| 1 Sept 2026, 14:58 | 107,675 | +92 |
| 31 Aug 2026, 15:25 | 107,583 | +193 |
| 30 Aug 2026, 16:04 | 107,390 | +311 |
| 29 Aug 2026, 14:17 | 107,079 | +316 |
| 28 Aug 2026, 12:22 | 106,763 | +98 |
| 27 Aug 2026, 14:58 | 106,665 | +334 |
| 26 Aug 2026, 12:03 | 106,331 | +206 |
| 25 Aug 2026, 12:06 | 106,125 | +194 |
| 24 Aug 2026, 14:25 | 105,931 | +496 |
| 22 Aug 2026, 19:16 | 105,435 | +441 |
| 21 Aug 2026, 07:53 | 104,994 | first reading |
225 posts held, back to 13 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 108 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 225 (13 July 2026 – 26 September 2026) |
| Views total | 767,446 |
| Reactions total | 6,476 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 10:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 21 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.
11,445 reactions across 225 posts, in 38 distinct kinds. The most used accounts for 83.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9,565 | 83.6% | |
| ❤ | 731 | 6.39% | |
| 🤣 | 348 | 3.04% | |
| 🤡 | 109 | 0.952% | |
| 💩 | 96 | 0.839% | |
| 🖕 | 80 | 0.699% | |
| 👎 | 75 | 0.655% | |
| 🍌 | 51 | 0.446% | |
| 🤩 | 39 | 0.341% | |
| 🔥 | 38 | 0.332% | |
| 🤔 | 36 | 0.315% | |
| 🌭 | 27 | 0.236% | |
| 😍 | 27 | 0.236% | |
| 😱 | 25 | 0.218% | |
| 🕊 | 23 | 0.201% | |
| 🤓 | 23 | 0.201% | |
| 🤮 | 23 | 0.201% | |
| 😡 | 21 | 0.183% | |
| 🥰 | 19 | 0.166% | |
| 👏 | 17 | 0.149% | |
| 18 further kinds | 72 | 0.629% |
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 225 of the 225 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 11,445 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 225 most recent posts we hold, published 13 July 2026 to 26 September 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.
别催了
👍34❤3🕊1
Signed iokhd
你离叔叔说了最晚国庆当天更新
👍45❤2🤔1
Signed iokhd
RT完美驱动导航-[最新更新内容] 🥰 RT-QX11.4promax无缓/有缓+硬断+陀螺仪最新版本 https://pan.quark.cn/s/e639b6845c9a RT_hook有缓/无缓新版本 https://pan.quark.cn/s/e639b6845c9a 过RT频道验证 https://t.me/RTdrivers/1685 编译定制驱动查看此信息 https://t.me/RTdrivers/2321
👍62❤8🔥2
Signed iokhd
推荐一款朋友的和平落叶🎮三角洲🎮公益项目 三角洲拥有最先进的解密 大家可以去支持一下 https://t.me/luoyenb521 入住就送广告免费发我有管的频道 luoye.yjsfk.cn 流水1000
👍60❤3
Signed iokhd
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ 🏆Ai-CodeV瓦手裸奔追踪+漏打+内透🏆 采用硬件Hook技术达到追踪效果 无内防,无内存读写,纯硬件Hook 算法级内透,硬件Hook游戏图层 实时计算图层数据,做到人物覆盖掩体 🔡支持自定义追踪大小 🔡支持实时读取配置,运行时可实时修改大小 🎮瓦手独家裸奔内透,稳定1000h+ ✅Ai-CodeV提卡点击我 ✅Ai-CodeV备用提卡点击我 📱官方频道: https://t.me/XB1103 https://t.me/XB1103 https://t.me/XB1103 🔵频道内可通过签到免费获得卡密 🔵频道内有稳定公益瓦美化 🔗反馈4张质量图可加时24H 内部交流群点我进入
👍62❤4
Signed iokhd
🚀王者极光解密内核拯救拉闸市场 🥇价格便宜1元即可测试好用再买天周月 只做长期项目不会跑路 😙算法解密 不客户端 不外挂180 不卡屏 不吃环境 无视强标闪框等问题 最多行为封号 任何手机任何账号不管你号多黑多毒都不会闪框卡头 算法解密不动内存独家方案和谐只会卡头 月末不追180 ⚡流畅绘制 独家写法 丝滑流畅不掉帧 老爷机也能流畅运行 稳定144hz 🕠自瞄为su7同款自瞄 无敌准度不空枪 算法自瞄 指哪打哪 😀支持全系机型 功耗低 玩起来不发热掉帧卡顿等 🌈操作简单适合新手小白还有专门超详细视频教程 💗apk和sh双版本运行 选择你喜欢的方式 都有教程 👑欢迎各大代理批卡开端对接长期项目不会跑路 项目无任何引流 放心倒卖 稳定性🔥 卡网对接码mmnb 不禁言交流群 https://t.me/xqnh666
👍60❤2
Signed iokhd
❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️ 不限制机型,华为,IQ,vivo,只要你的设备可以正常联网即可,不需root权限,不需要电脑,不需要解bl,手机联网即可绘制 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据!支持设备型号不限安卓鸿蒙都可以,不限制系统版本,手游都通用 支持3d模型显示人物位置,把游戏整个地图的模型都会加载在雷达上,可以看清楚别人具体在哪个楼层具体位置 新增三节点 自动负载均衡 三台服务器都是三线BGP 国内直连50ms 😀 星辰三角洲裸奔漏打解密内核 ⚫️算法解密 无视游戏最新坐标加密 😀精美UI ➡️可选图像/文字绘制样式 ⚙全功能齐全:漏打/雷达/自瞄/物资/容器 ✅不闪框 ✅不聚框 ✅不漏人 ❤️ 加入频道获取公益内核 ❤️ 获取免Root网…
👍61❤1
Signed iokhd
🎮 星辰三角洲 - 公益解密内核 读取算法解密 无视游戏最新坐标加密 全功能支持 漏打/雷达/自瞄/物资/容器 精美绘制界面 可选图像/文字绘制样式 强大的作者团队 出现问题第一时间更新 ❤️ 加入频道获取官方APK ⭐️ 公益卡密:@astradfm ✅人物绘制✅内核自瞄✅漏哪打哪 ✅物资绘制✅容器绘制✅地图雷达 ✅模型漏打✅算法解密✅安全可靠
👍63❤1
Signed iokhd
😂东东全防台湾服国际服三角洲支持xzz所有内存功能😂 挑战全世界2倍速3分钟完成清图 😂防子追,注入等等全部😂 无视所有检测‼️‼️‼️ 枪械据点✅ 枪械范围✅ 枪械无后座✅ 枪械瞄准✅ 😃😀😃注意这次更新是台湾服 国际服 国服暂时和谐没有更新 购买卡网: http://shop.918fk.cn/shop/dondon 台湾服使用教程点我❤️ 台湾服全防下载点我 国际服使用教程点我❤️ 国际服全防下载点我 可搭配的注入科技点我 😇🙃😉👉点我加入频道看更多反馈 官方客服:@aaayiyiyy
👍62❤2
Signed iokhd
💗只推荐免费公益,专注三角洲解密项目推荐,多方严选,行业一手信息,对接全网所有渠道,加入频道了解科技圈最新一手消息。💗 ✅9.24最新三角洲目前公益解密项目如下(纯算法解密)👍👍 👉 T1三角洲公益算法解密 👉 护航仔公益解密 👉 lsenna公益解密 👉 LGB公益解密项目合集 👉 arrogance纯算法解密
👍62❤1
Signed iokhd
🔥 9.25反馈| 国服貂蝉 |算法解密|在线定制|独家驱动 |一机一包 | 在线定制中 方案说明 ❌ 不改内存 ❌ 无特征码 ❌ 不用端口 ✅ 一机一包 ✅ 在线适配 ✅ 算法解密 ✅ 内置驱动 ✅一键启动 ✅ 持续更新维护 ✅ 多英雄自瞄适配 ━━━━━━━━━━━━━ 💰 定制价格:500 / 月 📩 在线定制 @cf4548 @GOUDANNBYAYA 📢 内部频道 @zijiePro @zijiePro @zijiePro 📢 交流群 @zijiechat @zijiechat @zijiechat ━━━━━━━━━━━━━ 为什么要一机一包,不能一套通杀? 老王现在不同机型、系统环境甚至是账号算法都可能存在差异,版本更新后协议参数也会变化。所以每个机型的加密算法都不同。而且定制版本没有特征码,每个人都是独一无二的包。 至于有些宣传所谓“无视版本更新、无视算法变化、全机型永久通用、无视大小版…
👍61❤1
Signed iokhd
三角洲嘉豪单解密❤️ 我们的优势: 1️⃣利用修改游戏漏洞实现不进行坐标加密,并非端口 拦截等低手段,且不会令玩家头疼的网络波动🀄️ 2️⃣解密无视所有加密,包括不限于云端下发加密/本地maps加密/常量加密和数组加密等等,无论你的号有多黑 你的环境有多差 通通无视遁地 🔄 3️⃣辅助自搭配,我们仅解密,辅助你需要自己搭配,好处就是你想用哪个辅助就用哪个,你觉得哪个辅助自瞄舒服你就用哪个⭕ 巨多反馈 稳定性毋庸置疑 临近中秋与国庆,所以我们嘉豪单解密打算开启中秋与国庆共同的公益活动,日期为9月25日到10月4日,活动期间你可以输入任意卡密登录嘉豪单解密 点击下面频道链接 进入频道详细了解该项目 https://t.me/NSNB2 https://t.me/NSNB2 https://t.me/NSNB2
👍62❤2
Signed iokhd
Showing the 12 most recent of 225 posts we hold for @RTdrivers. 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.
@RTdrivers edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
@RTdrivers named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“RT完美驱动发布频道” (@RTdrivers), 112,098 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/RTdrivers.
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.