Telegram RegisterThe public register of Telegram

Channel

椿光无限·私影女仆测评频道

@cgwxcp

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,242subscribers

+12 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002476034077
TypeChannel
Username@cgwxcp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/cgwxcp

Growth

1,2301,2421,2368 August 2026 — 1,230 subscribers8 August 2026 — 1,231 subscribers11 August 2026 — 1,237 subscribers14 August 2026 — 1,242 subscribers8 August 202614 August 2026
4 measurements spanning 7 days, net +12. 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 1,228–1,244 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:221,242+5
11 Aug 2026, 08:571,237+6
8 Aug 2026, 14:521,231+1
8 Aug 2026, 01:331,230first reading

Engagement

20 posts held, back to 22 July 2026the 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.

ERR · 30 days
75.2%
avg views ÷ 1,242 subscribers
Avg views / post
934
20 posts measured
Reaction rate
0.214%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 6 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (22 July 20267 August 2026)
Views total18,672
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:33 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.

What this channel posts

Video runtime
20s
Average length
10s

Measured directly from 2 videos 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.

Reaction mix

15 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 86.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1386.7%
👍16.67%
💘16.67%

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 6 of the 20 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 15reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 July 2026 to 7 August 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

7 Aug 2026, 06:31 UTC146 viewsread 8 August 2026
Forwarded from @kgjdddd

#空港基地 @3983号飞行员 #小秋 #椿光无限 #西湖 #2026.8#2h 店铺: https://t.me/fujiang003/646377?single 颜值8 身材7 皮肤8 敏感度7 性格10 综合体验8.6 优点:颜值高,全身敏感 缺点:太瘦了很骨感 过程: 初见小秋,穿着jk扎着双马尾,白色腿袜,充满青春气息,立马拉上楼上钟。 房间里还放着上一钟的电影,小秋果断提出要换一部,她说我们两个要有专属的回忆。轻声细语的双唇十分软糯。开始还是浅吻,慢慢呼吸声便大了起来,虽然没什么侵略性但是配合度拉满了。双手向下拉开衣服,本以为骨干小萝莉是个飞机场,结果还是颇有规模的,大概a+。轻舔乳头,立马发出呜咽声,侧乳更是敏感,一舔就发抖。开始漫游全身,发现后腰更是小秋的红色敏感地区,不一会就开始求饶。卸甲十分顺利,伸手探去,小秋便配合地张开双腿,还主动提出卸下最后一甲。轻拂豆豆一会便引出潺潺流水,戴上指套后慢慢进入,小

5 Aug 2026, 15:21 UTC343 viewsread 8 August 2026
Photo

#No1681 店铺:#椿光无限 女仆:#小怪 💯评分标准 店铺链接: t.me/fujiang003 类型:#素人 #服务型 #活虾 价格:1200/2h 出击人:#用户虾名 出击时间:2026.08 环境: A 人照相似度:人照6 罩杯:胸A+ 身材:人瘦 身高:160 体重:90 皮肤:白度正常,弹性正常,平滑度正常 态度:S 聊天交流:聊天顺畅,有情绪价值 敏感处: 全身,轻触也会有反应 抽烟:未闻到 纹身:无 唇钉舌钉:无 吻技:正常 🌱初见 本想在出击当日就完成测评,结果两个小时的对战实在是酣畅淋漓几乎没休息,人的精力完全被耗尽,根本没办法集中精力。上个月慕名去拜访过小怪,服务精神非常到位,当时就决定周末二刷,结果没两天客服就告诉我妹妹退役了。心有不甘的我每天都要打开群聊检查,居然真的在两周后蹲到了复出,当即推掉所有事情约了两个小时。 🔥过程 复出的小怪感觉比上次更从容,准备也更充分,光是衣服就有好

29 Jul 2026, 11:24 UTC≈1,200 views5 reactionsread 8 August 2026
Photo

#空港基地 @99号飞行员 #小林 #椿光无限 #西湖 #2026.7#1h 店铺:https://t.me/fujiang003/634067 颜值8.0 身材8.0 皮肤8.0敏感度 8.0 性格 8.8 综合体验:8.16 优点:知心姐姐 缺点:无 过程:自打进了女仆圈就听说了小林老师大名。今天上个小姐姐吃了一肚子气。就想找小林老师学习下。刚好她和我的时间也对的上,就就约了一钟,翩然而至。 进门是一身白纱,感觉老师好高,问了170,模卡写168,穿上黑色小高跟,感觉比我还高,哈哈,破冰几分钟,听她说女仆圈现状,不愧是有自己tg频道的,对现况非常了解。然后对视一下就吻到了一起了,她不抽烟,接吻时甚至感觉有点甘甜,这是抽烟妹子无法带给我的(哪怕用了漱口水)。同时接吻是我不停她不停,是最近吻感最好的一位。舔任何部位都可以接受,而且均有回应。说只要不留下痕迹就行。(本人非汪汪党,也不喜舔脚,所以这两个部位没有尝试)。卸甲也

5

28 Jul 2026, 07:30 UTC≈1,250 views2 reactionsread 8 August 2026
Photo

【推荐指数】:⭐⭐⭐⭐⭐ 【妹子花名】:#小林 【妹子年龄】:01 【所属店铺】:#椿光无限 【验证留名】:@木子 【验证时间】:2026.7.28 【大概位置】:#揽翠大厦 【课程费用】: 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 【人照相似】:10 【身高身材】:168 瘦长条美女 【凶器罩杯】:A+ 【个人标签】:杭州最严厉的妈妈 【服务特色】:尺度给满 【环境细节】:10 【个人卫生】:10 【时间管理】:10 【推荐程度】:10 评分标准:6分﹣差 7分﹣及格 8分﹣良好 9分﹣优秀 10分﹣极品 【流程小文】:久闻小林女仆必吃榜大名,在群里潜水多月,终于在今天前往杭州出击小林老师,心中还是非常紧张激动的,小林酱迟到了一会会,在房间等待了一会儿,小林老师便敲门进来,今天身穿一身白色短裙搭配白色大腿丝袜,本人比模卡上更加好看。两人并排躺下来,

2

28 Jul 2026, 02:37 UTC≈1,170 viewsread 8 August 2026
Photo

【推荐指数】:⭐⭐⭐⭐⭐ 【妹子花名】:#花花 【所属店铺】:#椿光 【验证留名】:@二狗子 【验证时间】:2025.7.24 【大概位置】:#揽翠大厦 【课程费用】:测评价 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 【人照相似】:9 【身高身材】:9 【凶器罩杯】:c 【环境细节】:8 【推荐程度】:9 评分标准:6分﹣差 7分﹣及格 8分﹣良好 9分﹣优秀 10分﹣极品 【流程小文】: 进门初见lolita,笑容甜美看得我心痒痒。说话声也甜得厉害,且很主动。皮肤白嫩光滑,还是在上学的妹子。平时喜欢打洲,可惜我不会。配合度极高,因为是素人,所以目前还只有标大。但是可以达到标大+。可惜那天太晚了,妹妹跟闺蜜约了饭,不然高低再续一个

28 Jul 2026, 02:37 UTC≈1,070 viewsread 8 August 2026
Photo

【推荐指数】:⭐⭐⭐⭐⭐ 【妹子花名】:#哈哈 【妹子年龄】:18,真18 【所属店铺】:#椿光无限 【验证留名】:@chali 【验证时间】:2026.7.27 【大概位置】:#揽翠大厦 【课程费用】: 500测评 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 【人照相似】:10,好妹妹照片很真实 【身高身材】:高 【凶器罩杯】:这个确实A,没办法 【个人标签】: 很年轻很阳光,很“哈哈” 【服务特色】: 主要还是很让人心情愉悦吧,妹妹化妆化的也是柳叶眉,笑起来有弧线,很治愈 【环境细节】: 揽翠公寓 【个人卫生】: 10 【时间管理】: 10 【推荐程度】: 9 评分标准:6分﹣差 7分﹣及格 8分﹣良好 9分﹣优秀 10分﹣极品 【流程小文】: 刷手机看到揽翠又来了好妹妹,正好出差回来去看看。到了发现房间没准备好,一个笑嘻嘻的白衣哈哈妹妹正在整理床

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

Citation-graph rank — 402,970 of 1,478,351entries 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.

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

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.

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.

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

“椿光无限·私影女仆测评频道” (@cgwxcp), 1,242 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/cgwxcp.

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.