Telegram RegisterThe public register of Telegram
Telegram profile photo for 城外

Channel

城外

@CWTYCD

On this record: Growth · Engagement · Posts · Citations · Cite this entry

607subscribers

-6 since we began measuring on 9 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002088079992
TypeChannel
Username@CWTYCD
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 November 2026
Last confirmed live18 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/CWTYCD

Growth

6076136109 November 2026 — 613 subscribers10 November 2026 — 613 subscribers18 November 2026 — 607 subscribers9 November 202618 November 2026
3 measurements spanning 9 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 606–614 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 12:20607-6
10 Nov 2026, 10:20613no change
9 Nov 2026, 18:22613first reading

Engagement

18 posts held, back to 14 April 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.

ERR · 30 days
8.32%
avg views ÷ 607 subscribers
Avg views / post
50.5
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held18 (14 April 2025 – 30 October 2026)
Views total101
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 18: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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 2 posts 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).

30 Oct 2026, 11:31 UTC46 viewsread 9 November 2026

公网户籍地址 2.5U 19:00-8:00 读就秒 公网真地址 3U 19:00-19:30 读就秒 公网真地址 4U 全天开放 读就秒 有量有价!欢迎律师盘口老板合作! 客服: 联系 双向: 联系

28 Oct 2026, 17:57 UTC55 viewsread 9 November 2026

名下三网手机号 1️⃣5️⃣💰 无遗漏移动联通+库版电信 客服: 联系 双向: 联系

19 Oct 2026, 12:33 UTC104 viewsread 9 November 2026

个人户籍类 公网户籍 个户/盖章/正反 4️⃣💰 地区户籍 北京个户 3️⃣💰 天津神父 3️⃣💰 上海神父 3️⃣💰 江苏神父 1️⃣💰 安徽个户 3️⃣💰 江西神父 3️⃣💰 山东神父 3️⃣💰 湖北神父 3️⃣💰 湖南个户 3️⃣💰 湖南神父 1️⃣💰 广东个户 3️⃣💰 广西神父 1️⃣💰 海南神父 1️⃣💰 重庆个户 3️⃣💰 陕西个户 3️⃣💰 贵州神父 3️⃣💰 甘肃神父 3️⃣💰 新疆神父 2️⃣💰 有量有价!欢迎律所盘口老板合作! 客服:联系 双向:联系

18 Oct 2026, 08:27 UTC80 viewsread 9 November 2026

全家户籍 文字全户 1️⃣2️⃣💰 单头全户 1️⃣5️⃣💰 全头全户 1️⃣7️⃣💰 刑侦全户 6️⃣0️⃣💰 有量有价!欢迎律所盘口老板合作! 客服:联系 双向:联系

18 Oct 2026, 08:24 UTC81 viewsread 9 November 2026

车类业务 破解车小档 1️⃣5️⃣💰 慢线车大档 4️⃣0️⃣💰 秒线车大档 4️⃣5️⃣💰 交强险名下车 8️⃣💰 12123名下车 4️⃣5️⃣💰 车管所名下车 7️⃣0️⃣💰 有量有价!欢迎律所盘口老板合作! 客服:联系 双向:联系

18 Oct 2026, 08:08 UTC83 viewsread 9 November 2026

移百机主 移动名字1️⃣8️⃣💰 移动生日1️⃣8️⃣💰 破解移百3️⃣5️⃣💰 现任移百4️⃣0️⃣💰 电信机主 电信名字 1️⃣8️⃣💰 电信生日 1️⃣8️⃣💰 破解电百 4️⃣0️⃣💰 联通机主 6️⃣💰 有量有价!欢迎律所盘口老板合作! 客服:联系 双向:联系

29 May 2026, 00:14 UTC260 viewsread 9 November 2026

破解类业务 支机 3️⃣💰 机主 3️⃣💰 法人 3️⃣💰 股东 5️⃣💰 卡反 7️⃣💰 邮箱反8️⃣💰 破解电信 3️⃣0️⃣💰 破解移动3️⃣5️⃣💰 破解码反 5️⃣💰全国1️⃣0️⃣💰 三件套+ 3️⃣💰 有量有价 代理可来拿优势! 客服: 联系 双向: 联系

8 Mar 2026, 15:03 UTC466 viewsread 9 November 2026

业务列表: 😀支机 😀机主 😀法人 😀股东 😀卡反 😀加工 😀电百 😀支百 😀码反 😀邮箱反 😀假地址 😀真地址 😀常用号 😀有效期 😀户籍地址 😀快递地址 😀名下三网 😀破解人脸 😀公网补齐 😀文字全户 😀单头全户 😀全头全户 😀柜台卡反 😀社保缴费 😀民政婚姻 😀名下车辆 😀名下房产 😀名下企业 😀对公账户 😀工商法人/股东 😀以上业务均在线! 😀回单效率拉满! 😀欢迎律所催收前来合作! 客服: 联系 双向: 联系

4 Nov 2025, 10:33 UTCviews —

城外 pinned «长期收各类接口/思路 人脸核验 三要素核验 二要素接口 各种机主思路 价格可谈»

24 Oct 2025, 07:23 UTC802 viewsread 9 November 2026

公网补齐 1️⃣0️⃣💰 (专治脱库 任意17位) 公网猎魔 1️⃣0️⃣💰 (脱库可出 可带排除) 文字全户 1️⃣2️⃣💰 有量有价 代理选手可以来拿优势! [点击联系]

Showing the 12 most recent of 18 posts we hold for @CWTYCD. 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.

Mentions

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.

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 18 November 2026 — this entry's latest reading, not the date you are reading this.

“城外” (@CWTYCD), 607 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/CWTYCD.

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.