bot 使用教程导航 1️⃣社工库查询方法 点我查看 查询结果之 名字检索教程 点我查看 2️⃣TG探针使用方法 点我查看 3️⃣ 短信轰炸使用方法 点我查看 4️⃣ 照妖镜使用方法 点我查看 5️⃣ 克隆功能及介绍 点我查看 bot→ @doro
❤51👍8

Channel
@KHQZB
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
43,480subscribers
+875 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002832693813 |
|---|---|
| Type | Channel |
| Username | @KHQZB |
| Description | 此频道用于“ 使用教程 ” 不掺杂任何广告 引流 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/KHQZB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:35 | 43,480 | +180 |
| 12 Aug 2026, 03:23 | 43,300 | +139 |
| 11 Aug 2026, 02:51 | 43,161 | +133 |
| 10 Aug 2026, 01:28 | 43,028 | +147 |
| 9 Aug 2026, 02:52 | 42,881 | +177 |
| 8 Aug 2026, 05:00 | 42,704 | +99 |
| 7 Aug 2026, 11:45 | 42,605 | no change |
| 7 Aug 2026, 11:33 | 42,605 | first reading |
8 posts held, back to 17 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 18 pagesof 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 18 July 2026 |
|---|---|
| Posts held | 8 (17 December 2025 – 18 July 2026) |
| Views total | 70,900 |
| Reactions total | 366 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 00:14 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 14 August 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 1 video 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.
3,210 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 39.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,255 | 39.1% | |
| 👍 | 621 | 19.3% | |
| 😁 | 436 | 13.6% | |
| 🎉 | 410 | 12.8% | |
| 🔥 | 399 | 12.4% | |
| 👎 | 23 | 0.717% | |
| 👏 | 17 | 0.53% | |
| 👌 | 16 | 0.498% | |
| 🤣 | 14 | 0.436% | |
| 🤬 | 8 | 0.249% | |
| 🥰 | 6 | 0.187% | |
| 💔 | 5 | 0.156% |
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 8 of the 8 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 3,210reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 17 December 2025 to 18 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.
bot 使用教程导航 1️⃣社工库查询方法 点我查看 查询结果之 名字检索教程 点我查看 2️⃣TG探针使用方法 点我查看 3️⃣ 短信轰炸使用方法 点我查看 4️⃣ 照妖镜使用方法 点我查看 5️⃣ 克隆功能及介绍 点我查看 bot→ @doro
❤51👍8
🤖 机器人克隆功能 · 三种模式介绍 1⃣ 免费克隆 - 克隆出来的机器人查询时会带有官方平台广告。 - 广告内容不涉及查档类推广,不抢流量,无任何引流方式。 - ⚠️ 防滥用机制:为减轻服务器负担,每月检查一次活跃度。若出现以下情况,机器人将被强制停止: - 零查询、零使用 - 恶意刷量(如一个账号刷数万次调用) - 被停止后,用户可手动重启,重新运行。 2⃣ 商家版本 - 可自定义一条查询广告按钮。 - 每月可向用户推送10条消息。 - 可设置强制用户加入指定的群/频道后才可使用。 - ✅ 适用于:个人接单、低成本引流获客。 3⃣ 企业版 - 可自定义10条查询轮播广告。 - 可指定强制加入4个频道或群。 - 每月可向用户推送50条消息。 - 旗下所有克隆的免费机器人查询时,都会带上你的轮播广告(可手动开关)。 - ✅ 适用于:团队运营、品牌曝…
❤56👍10🤬7🥰3😁3
照妖镜的使用方法 点击照妖镜 他会给你一个网址 把网址复制发给其他人 (这边建议用手机浏览器打开) 打开之后会申请相机权限 同意了之后会立马自拍一张照反回到机器人上 两积分一次 链接有效期30分钟 每天向机器人发送签到可获得4~8积分 一积分使用一次
❤187👍20👏16👎5
🔰电话调用 (短信轰炸) 电话随机 使用方法: 发送 签到 给机器人 机器人会随机给 3~6 积分 一积分等于1分钟轰炸时间 😐使用方法 ──────────── 用法:轰炸 手机号 分钟数 文字指令:轰炸 13800138000 1 bot指令 :/call 13800138000 1 意思: 轰炸 13800138000 1 分钟 范围:1-60 分钟 扣费:1 积分 = 1 分钟 每天发送签到随机获得4~8积分 注: 用的人太多 接口死的快 从一开始的七十多条 四天内死的就只有十条了 为了保证轰炸质量 每个星期 星期一会更新一次接口
❤182👌16👎16
TG探针使用教程 生成TG探针 你会得到一个这样的蓝色字体提示 点此打开链接 长按蓝色文字 就可以看到链接 然后点击复制 发送给TG 需要探测的用户 用户点击链接 连接代理之后 即可探测出他所在的城市 例:中国 广东 深圳 注意事项:一个链接只可探测一次 需要重探测的 请重新生成链接 VPN会影响探测准确性 每天向机器人发送 签到 可获得4~8积分 一积分使用一次
❤104👍7💔5🤣4😁2🔥1
名字检索视频教程
❤46👍9🔥6
信息安全查询工具 本bot机器人 为综合查询机器人 注意!!😐查询方法:请直接发送 单一的 “姓名” “手机号” “身份证号” 禁止带有空格 标点符号和其他字符 (错误查询方法 机器人不会输出结果) -单一手机号或身份证号: 最为精确的查询方式,确保您能获得准确的泄露信息结果。 - 单一姓名查询: 由于重名情况较多,结果可能不够精准,可导出TXT 用MT管理器检索 姓名检索教程→ https://t.me/KHQZB/50 ⚡️ 机器人消息只会保留10分钟 10分钟后自动除删所有查询结果 ps:总有一群傻逼不看 或者不识字 机器人不回他 就来问 眼睛瞎就别要了 6月2日更新 新加接口二查询 接口一查不到的 或者频繁的 可以点接口二 TG探测器 短信轰炸 照妖镜 为积分功能 每天发送 签到 免费送4~8积分
❤92👍17😁4🥰3
In light of growing concerns over personal data breaches, our bot is designed to help Chinese users verify if their personal information has been compromised. This bot aggregates data that is freely accessible on the internet to provide you with insights about your privacy status. The primary objective of this bot is to empower Chinese users by informing them if their data has been leaked, rather than allowing malic…
👍550❤537😁427🎉410🔥392🤣10👎2👏1
Showing the 8 most recent of 8 posts we hold for @KHQZB. 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 — 240,447 of 1,183,361entries 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.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“[bot] 教程🫥” (@KHQZB), 43,480 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/KHQZB.
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.