Channel
@zhaowu001
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
61subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002660377714 |
|---|---|
| Type | Channel |
| Username | @zhaowu001 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zhaowu001 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 14:30 | 61 | no change |
| 11 Aug 2026, 14:17 | 61 | first reading |
6 posts held, back to 14 October 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 pageof 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 6 posts for this entry, the most recent from 18 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
垃圾代投公司 破坏市场环境 给多少预算就去消耗多少 对乙方广告不负责 讲好的要求 做不到 拒绝赔付 骗子ID @winning_1Q84 @areuevil @a111tta 骗子地址 TUVqrfS12teeJoWow79VHC3PtHyrCaCcaP 200U当喂狗 希望各位甲方引以为鉴！别和这种垃圾公司合作 在此期间也奉劝各位代投公司 抵制这种不良行为 如果这种垃圾代投越来越多 离你们倒闭也不远了！
骗子昵称：Redpay 客服、Redpay 甜心、妍妍、大振、瑞德支付 胖虎、阿乐、Koi、瑞德支付 老三、权杰、肖战 骗子用户名: @Redpay006 、@Red2553 、@HH5282 、@hali518518 、@joy68868 、@lege85858 、@Redpay8888 、@lin125684 、@jiexika886 、@xiamo0088 骗子数字id: 8179667450 、 7900125647 、 7533382237 、 7847783041 、 7654437116 、 7040489524 、 7460038486 、 7988933555 、 7825960448 、 6447834012 骗子频道：https://t.me/Redpay88 被骗金额：500000INR 被骗说明: Red3Pay 唤醒 只收不付款 联系不上人了 。已经携款跑路 500000INR
骗子昵称：邋遢 雄起 tian shi 仿XPAY（非公群XPAY） 骗子ID: @wolf1213498 @tianshi54 被骗金额：8200U 骗子地址：TBA6CypYJizwA9XdC7Ubgc5F1bxrQ7SqPt（交易所转账） 被骗说明: 盘口经介绍找他接了两个线上盘，一个巴基斯坦一个印度，他自己也不是公司，只是有个台子，自己原本做技术的，接的其他公司的系统，到8月份盘口提出结算，以各种理由卡结算，说15天结算，盘口等了将近1个月，最后拉黑客户，群信息不回，不在线了。
Channel name was changed to «婷婷直通车🖤»
Channel photo updated
与名为“越越-BC代投”的用户进行沟通，对方在合作过程中多次以“保护它方隐私”等理由推诿延迟，拒绝按照约定配合核对信息。在多次沟通中，对方态度反复、前后矛盾，甚至企图将问题责任转嫁给他人，造成时间与经济上的损失。这个人的行为明显就是改了假消耗，做假账，一点诚信都没有，还一直狡辩，试图蒙混过关 我将这些聊天记录截图保存，仅为提醒他人：在进行类似线上业务时，请务必提高警惕，核实对方身份与交易方式，避免上当受骗或遭遇不诚信合作。
Showing the 6 most recent of 6 posts we hold for @zhaowu001. 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 — 1,398,906 of 1,550,220entries 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 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.
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.
@zhaowu001 named 4 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“婷婷直通车🖤” (@zhaowu001), 61 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/zhaowu001.
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.