客服新号 @TTxiaqi5
🤡19

Channel
@TTxiaqi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7,002subscribers
-27 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002660148014 |
|---|---|
| Type | Channel |
| Username | @TTxiaqi |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/TTxiaqi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 08:44 | 7,002 | -21 |
| 9 Aug 2026, 15:11 | 7,023 | -6 |
| 8 Aug 2026, 18:31 | 7,029 | first reading |
16 posts held, back to 9 February 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 4 pagesof 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 16 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
178 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 77.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 138 | 77.5% | |
| 🤡 | 28 | 15.7% | |
| 🆒 | 3 | 1.69% | |
| 🤔 | 3 | 1.69% | |
| 🔥 | 2 | 1.12% | |
| 🥰 | 2 | 1.12% | |
| 🤓 | 1 | 0.562% | |
| 🤯 | 1 | 0.562% |
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 13 of the 16 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 178reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 9 February 2026 to 6 May 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.
客服新号 @TTxiaqi5
🤡19
更新日志 1.新增应用保活机制 2.新增权限检查 3.修复部分机型 libc++_shared.so 缺失导致注入失败 4.新增远程更新 后续更新直接远程推送 5.优化部分UI 6.优化部分使用体验 7.修复多形态显示异常问题
❤14🤡9🤔1
更新内容: 1.适配新赛季-星神 2.新增牌库头像大小调节 3.修复竖屏开启偶显分辨率错误 4.修复部分机型对手站位闪烁 5.修复等级金币中等级的错误显示为人口
❤7🤔1🤯1🥰1
1.0.8 更新公告: 更新内容: 1.修复悬浮窗显示不全 现在会根据分辨率自适应大小 2.增加手机状态下的开启商店自动隐藏对手站位功能 3.增加开启选择阵容自动隐藏对手站位功能 4.增加转区 5.修复对手站位头像可能变大变小的问题 6.适配模拟器注入 全功能可正常使用(只测试过mumu模拟器) 1.1.1 更新公告: 1.修复按钮大小异常 2.修复对手站位异常 3.新增悬浮窗尺寸调节 手机尺寸太小 4.新增海克斯预测 尺寸调节 同上 5.适配去其他人棋盘不显示对手站位 6.修复了头像相关问题 现在会正常使用本赛季头像 1.1.8 更新公告: 更新内容: 1.修复对手预测图标偶然失效 2.牌库增加简介模式 直接显示全部英雄 3.三星预警增加简介模式 不显示名称 对手机用户更友好 4.对手站位隐藏按钮现在也会同步隐藏三星预警 5.金币等级大小调节分离 不和三星预警同步 使用提示: 1.美化默认的小小英雄不能是蓝袍河灵 2.美…
❤12
File, posted without a caption
【金铲铲之战-天天下棋】 ✨ 完美适配当前及返场赛季 【核心功能详解】 实战类 •对手预测 •对手站位显示 •三星预警 •自动拿牌 •牌堆显示 •商店信息 •转区 •强制投降 •玩家信息 •海克斯预测 美化类(所有美化都支持自定义,美化功能请大厅开启) •小小英雄美化 •棋盘美化 •攻击特效美化 •淘汰特效美化(可能导致掉线暂时别开启) 温馨提示:美化请大厅开启,悬浮窗贴边可隐藏 【设备支持】 ✅ 已全面支持所有已Root设备 【获取方式】 👉 购买地址:https://jcc.wlx.cc 📢 通知频道:https://t.me/TTxiaqi 👥 用户交流群:https://t.me/TTxiaqiGroup 客服 @TTxiaqi4
❤8
🔥【极限脉冲】专业DDoS压力测试平台 – 百G级真实攻击模拟,助您验证网络防御极限 💡 我们做什么? 极限脉冲(Extreme Pulse)为网络安全工程师、系统管理员、技术团队提供高效、稳定、安全的网络压力测试服务。无论是网站高并发压测、API接口稳定性摸底,还是防火墙/DDoS防护系统有效性验证,我们都能帮您提前发现瓶颈,筑牢安全防线。 --- 💥 核心能力一览 • 攻击火力 – 支持从几十G到数百G的真实攻击模拟,按需调节强度 • 全球节点 – 多地域分布,真实模拟不同区域的流量并发 • 智能队列 – 多任务自动排队调度,高效利用测试资源 • 实时监控 – 测试进度与状态全程可视化,结果随时掌握 --- 🎯 适用场景 ✅ 网站/APP上线前的高并发承载测试 ✅ API接口极限响应速度与稳定性验证 ✅ 现有防火墙及DDoS防护系统的有效性检验 ✅ 服务器性能基准测试与调优依据 --- 📢 立即体验 🔗 …
❤2
接王者荣耀亲密度升级,五块钱一级,无需任何亲密道具,升级无上限,需要上号,升级的两个号都要上且必须同区,都是QQ或者都是微信不能一个QQ一个微信,目前全国14名可查,需要联系 @TTxiaqi4
❤5🤓1
零号协议_1.2.apk
❤3
【零号协议 • 终末地全能辅助】 全网首发免root辅助(非直装非虚拟机非框架,真正意义上的免root,安装即可使用) 完美适配终末地官服以及B服。全方位提升战斗、探索、资源获取效率,让您轻松主宰世界! 【核心功能详解】 •杀戮光环 •必定暴击 •不败金身 •无限体力 •无视冷却 •无限跳跃 •速度倍率 •跳跃高度 •瞬移功能 •自动拼图 •自动破坏 •自动拾取 •自动侵蚀 •物资绘制 •自定义坐标传送 【设备支持】 ✅ 已全面支持所有安卓设备,无需root即可使用 【获取方式】 👉 购买地址:https://jcc.wlx.cc 📢 通知频道:https://t.me/TTxiaqi 👥 用户交流群:https://t.me/TTxiaqiGroup 客服 @TTxiaqi4
❤4🔥1
【零号协议 • 终末地全能辅助】预告 全网首发免root辅助(非直装非虚拟机非框架,真正意义上的免root,安装即可使用) 完美适配终末地官服以及B服。全方位提升战斗、探索、资源获取效率,让您轻松主宰世界! 【核心功能详解】 •杀戮光环 •必定暴击 •不败金身 •无限体力 •无视冷却 •无限跳跃 •速度倍率 •跳跃高度 •瞬移功能 •自动拼图 •自动破坏 •自动拾取 •自动侵蚀 •物资绘制 •自定义坐标传送 【设备支持】 ✅ 已全面支持所有安卓设备,无需root即可使用 即将上线 尽请期待!!!
❤5🆒3
终末地手游辅助测试联系 @TTxiaqi4 支持免root,支持所有安卓设备
Showing the 12 most recent of 16 posts we hold for @TTxiaqi. 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.
Citation-graph rank — 311,945 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
@TTxiaqi named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“金铲铲记牌器-天天下棋” (@TTxiaqi), 7,002 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TTxiaqi.
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.