🚀 嘿!想搭个社工库 API 机器人,滴滴我!📢 这可是引流界的“超级英雄”,数据海量,响应飞快,简直是你的流量加速器!🌟 需要的赶紧上车,别让你的营销计划还在原地踏步啦!✨ 联系客服: @ztosb

Channel
TG中通
@zhongtongyewu
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,984subscribers
+151 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002187599064 |
|---|---|
| Type | Channel |
| Username | @zhongtongyewu |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/zhongtongyewu |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 |
|---|---|---|
| 15 Sept 2026, 19:58 | 1,984 | +51 |
| 12 Sept 2026, 01:58 | 1,933 | +37 |
| 7 Sept 2026, 19:57 | 1,896 | +28 |
| 2 Sept 2026, 11:48 | 1,868 | +4 |
| 30 Aug 2026, 06:03 | 1,864 | -1 |
| 26 Aug 2026, 21:54 | 1,865 | +12 |
| 23 Aug 2026, 15:48 | 1,853 | +6 |
| 20 Aug 2026, 06:46 | 1,847 | +1 |
| 17 Aug 2026, 15:57 | 1,846 | -1 |
| 14 Aug 2026, 01:58 | 1,847 | +7 |
| 10 Aug 2026, 15:46 | 1,840 | +5 |
| 7 Aug 2026, 17:17 | 1,835 | +2 |
| 7 Aug 2026, 15:32 | 1,833 | no change |
| 7 Aug 2026, 13:42 | 1,833 | first reading |
Engagement
18 posts held, back to 27 August 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 18 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
6 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.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 18 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 27 August 2025 to 25 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
😚自动群发器,可采集任意群组任意时间内的发言,可根据关键词 TG会员等等进行采集,完成采集后一键群发私信,各行业营销必备工具。需要的老板请联系:@ztosb
没头脑频道搬运机器人 功能支持将任意频道的内容自动同步至指定子频道,并在搬运前通过人工智能技术进行内容优化,包括去除广告、移除外部链接及添加自定义后缀,确保内容整洁规范。 🚀 仅需三步即可高效完成配置: 1️⃣ 新建路由 进入「频道路由 → 新建路由」,依次选择来源频道与目标子频道,配置完成后即可启动。 2️⃣ 清洗设置 根据需求启用「AI 去广告」、「移除外链」或「添加小尾巴」等功能,灵活定制内容净化方案。 3️⃣ 确保在线工作账号 在「账号管理」中确认存在在线工作账号,系统将实现 7×24 小时自动化搬运,无需人工持续监控。 --- 🎯 适用对象 内容聚合者、社群运营人员及信息整理者。该工具可显著减少人工复制粘贴的时间成本,助力团队专注于高价值工作。 🤖 欢迎立即通过 @meitounao1bot 体验,让内容搬运变得如同呼吸般自然流畅。 请联系BOT客服开通免费使用
设置教程⚙️ 1⃣. 打开 @ZTOJZ888bot,点击「立即创建我的机器人」✔️ 2⃣. 按提示输入机器人名称和用户名。🔗 3⃣. 打开 @BotFather,发送 /mybots。🔜 4⃣. 选择刚创建的机器人。📎 5⃣. 点击「Bot Settings」→「Secretary Mode」→ 开启。👑 6⃣. 去设置 → 账号 → 聊天自动化,填入机器人用户名,添加并确认。ℹ️
@ZTOJZ888bot —— 你的专属财务管家,一键克隆,即刻拥有。🚩 这不是一个公用的记账软件,而是一个能让你几分钟内克隆出自己专属机器人的工具。克隆完成后,你拥有一个完全独立的、只为你服务的私人财务管家。✉️ 它能做什么?在聊天框里输入数字,自动记账,支持多国货币实时折算。发一个钱包地址,自动查询链上余额。随手输入算式,立刻出结果。内置实时汇率看板,数字和法币自由兑换。⌛ 更关键的是,它默默在后台保护你。所有被撤回的消息,自动留底,一条不漏。每天早上八点,准时推送财务简报,让你对资金状况一目了然。🔒 如果你有团队,它支持协同记账,老板和员工权限分离,各看各的账。数据随时可一键粉碎,不留痕迹。🛡 现在就去 @ZTOJZ888bot,点一下「立即创建我的机器人」,几分钟搞定,终身好用🆒
积分不够的用户可以三个群交替使用。 一群:点击此处 二群:点击此处 三群:点击此处 短信轰炸群:点击此处
❤2
社工库搭建联系: @ztosb
最新机器人,不消耗积分公测,欢迎大家体验并提供宝贵的建议。 1️⃣ 综合查询 直接发送关键词即可。 例:13800138000 或 张三 或 白云大道 2️⃣ 模糊补齐 (/bq) 需至少提供两个模糊参数。 例:/bq 周x伦 188xxxx8888 或者身份证号未知部分替代 3️⃣ 证件猎魔 (/lm1) 参数:姓名 地区 性别 年份 例:/lm1 周杰伦 台湾县 男 1980-1985 4️⃣ 手机猎魔 (/lm2) 参数:姓名 手机 归属地 例:/lm2 周x伦 广州 移动 188xxxx8888 点击此处使用
❤2
三年医疗缴费票据开秒 源头出 欢迎全网比价 提供:姓名+身份证号 结果:诊断名称,就医机构,就诊时间、类型等(如图) 出单时间:秒出 绿茶 揭露利器 什么打胎 生育 艾滋病 性病 各种逃不过 可以通过数据来衍射对方的行为(比如小姐的话会定期进行妇科检查 而且频次超过正常人很多很多) 目前医疗记录稳定版本
❤1
积分不够的用户可以三个群交替使用。 一群:点击此处 二群:点击此处 三群:点击此处
ZTO三群已开,现在可以免费参与抽会员活动。点击此处加入吧
免费五年医疗记录机器人 可出五年内医疗看病记录 @ztoylbot
Showing the 12 most recent of 18 posts we hold for @zhongtongyewu. 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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@zhongtongyewu named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 8 August 2026
named in 2 posts, 8 August 2026 – 8 August 2026
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“TG中通” (@zhongtongyewu), 1,984 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zhongtongyewu.
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.