Channel
@wangzi66666666666
On this record: Growth · Engagement · Posts · Citations · Cite this entry
26subscribers
+3 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004443291646 |
|---|---|
| Type | Channel |
| Username | @wangzi66666666666 |
| Created | 4 July 2026 — measured — dated from the channel’s first post |
| First recorded | 10 November 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/wangzi66666666666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 00:05 | 26 | +3 |
| 10 Nov 2026, 01:22 | 23 | no change |
| 10 Nov 2026, 00:47 | 23 | first reading |
2 posts held, back to 4 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 1 page 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 2 November 2026 |
|---|---|
| Posts held | 2 (4 July 2026 – 2 November 2026) |
| Views total | 178 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 01: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.
Telegram’s own ‘edited’ marker: 1 of 1 post held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
要求：国内账号，半年账单以上，能加人，正常聊天，私人号最好，不经常上电脑的有时候会跳设备环境，找朋友验证一下就好，验证不了，解不开的，没好友辅助的别来 一.远程控制（需要有电脑） 底薪100（底薪）+200（提成） 把微信登录自己电脑上面，电脑下载uu远程软件，然后我们远程操控 具体流程： 1.截图年账单 好友数量 2.下载AntMessenger软件（飞机也可以） 3.发资料给你改包装（微信名 个性签名 地区 朋友圈 视频号等，不会乱修改的） 4.改完把微信登录电脑上面养一天，第二天早上开始工作 5.开始把微信登录电脑上面，客户会发数据给你，你在手机上面添加，添加了截图发对接群 6.通过了及时在对接群叫客服回复消息，你一天就负责看有没有通过，有没有客户回消息就可以了，不需要你回复 第一天工资押着，第二天开始正常结算，中途限制找不到人解开不退，做不满15天不退，有特殊原因情况不退，是我们这边问题正常退，因为我们只要长期的，…
Channel created
Showing the 2 most recent of 2 posts we hold for @wangzi66666666666. 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.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“王子的小屋” (@wangzi66666666666), 26 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/wangzi66666666666.
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.