Channel
@sz_cc_info
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
238subscribers
+10 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003914541660 |
|---|---|
| Type | Channel |
| Username | @sz_cc_info |
| Created | 1 June 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/sz_cc_info |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 06:43 | 238 | +10 |
| 8 Aug 2026, 13:00 | 228 | first reading |
15 posts held, back to 1 June 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 pageof 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. It is computed over the 2 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 15 (1 June 2026 – 27 July 2026) |
| Views total | 3,994 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 13:00 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.
Measured directly from 10 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.
7 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 8 of the 15 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 1 June 2026 to 27 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.
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】匿名 【日 期】: 7月 27日 【美女昵称】：安安 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：园区 【上课花费】：999 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：10 【服务内容】：超大班 【服务过程】: 到门口客服下来接我上去。私密性非常ok，房间也非常舒适。等到安安进来，一身白色连衣包臀裙加上白皮肤看得直接血脉膨胀，先聊聊天得知她还有个男朋友，这让我觉得更加刺激直接来劲。之后就是一些常规操作，把她按在床上把玩，最后流连忘返。顶级无敌的体验。
❤1
全职 花名： 安安 身高：160cm 体重：40kg 年龄：19 胸围：B 属性：机灵小不点 纯欲千金风
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】白面 馒头 【日 期】: 7月 24日 【美女昵称】：邱酱 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：昆山 【上课花费】：599 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：10 【服务内容】：大班 【服务过程】: 首先做为我女仆之路的初体验，我抱着忐忑怀疑的心而来。我来女仆店就是为了🐍吻和情绪价值，如果这都没有的话我真要闹了，不过好在黄毛教官有两把刷子，让小白的我乘兴而来乘兴而归，流连忘返。说重点我体验的是邱酱，邱酱颜值深得我心，服务态度也是很好，大蟒蛇管饱，中间穿插着些许话题，但我的心思早已投入到和邱酱妹妹的🐍吻当中，一吻😘天荒，无法自拔，难以忘却。再多的细节我就不描述了，总结就是夯。下次有机会体验其他妹妹，人生胜在多体验！不过我现在有点担心初体验阈值就拉的如此之高…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】wang er gou 【日 期】: 7月 23日 【美女昵称】：甜甜 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：苏州 【上课花费】：999 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：10 【服务内容】：超大班 【服务过程】: 新人来第三天了，作为一个忠实的老粉第1、2天竟然没约到，约到了今天。到了房间里等了会，甜甜一进门身材惊艳，估计得170，非常主动的扑我怀里，直接来个大蟒蛇，小舌头是真的灵活，我一边舌吻一边抓着她的屁股。这大长腿能玩一天，身材匀称，奶子不算大，但很挺，手感还好，总之服务态度尺度都没问题，老粉们不用担心，放心冲，今天总体符合预期。
全职 花名： 甜甜 身高：168cm 体重：45kg 年龄：20 胸围：B 属性：机灵古怪 俏皮甜美（有点腼腆）
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】正宗 【日 期】: 7月 14日 【美女昵称】：娇娇 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：苏州 【上课花费】：999 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：10 【服务内容】：超大班 【服务过程】: 新店开了几天了，作为一个忠实的老粉为什么没有第一时间去呢，主要是心里没底啊，担心新人服务尺度上达不到我的要求，像我这种老色批尺度小了真降落不了，本来想着看一个月再说，今天突然热的要死，想着这种天气空调房里抱着嫩妹应该挺舒服，遂临时起意来店里看看，离家6分钟是真近啊。美女客服亲自下楼来接，上去一看今天刚到的娇娇，一说话果然是昨天群里的娃娃音，就选了她，进房衣服一脱，娇娇非常主动的扑我怀里，直接来个大蟒蛇，小舌头是真的灵活，我一边舌吻一边抓着她的小屁股，那种熟悉的感觉…
❤1
苏州橙C女仆档案 pinned a video
全职 花名： 娇娇 身高：163cm 体重：45kg 年龄：21 胸围：B 属性：可御可甜 反差萌妹
全职 花名： 夏夏 身高：161cm 体重：55kg 年龄：22 胸围：F 属性：逗比可爱 童颜巨乳大胸妹
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】qwer 【日 期】: 7月 13日 【美女昵称】：夏夏 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：苏州 【上课花费】：999 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：10 【服务内容】：超大班 【服务过程】: 群里潜水的时候发现了一个巨乳妹妹的ootd，一眼心动直接前往。小区很好到楼下客服小姐姐亲自下楼接人，插一句题外话客服小姐姐也挺好看。去房间等了5分钟左右，夏夏来了，巨乳，巨乳声音温柔好听，看着文文静静一上床直接反差。巨乳直接唔脸，一瞬间鸡儿梆硬。唔了一会儿开始🐍但是巨乳太大完全没心思🐍，然后衣服直接脱完一把把玩巨乳妹妹一边亲奶头一边✈️直接起飞，休息了一会儿再继续。妹妹基本上有求必应。我愿称他为苏州女仆天花板。兄弟们务必尝试。结束后正好看见一个妹子吃饭也是非常…
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分，一星差评)』 【体验人】洛青舟 【日 期】: 7月 11日 【美女昵称】：小桃 【联系方式】： @sz_cs_bot 【所属频道】：公开榜（公开榜/必品榜） 【地 区】：苏州 【上课花费】：1500 【口渴关怀】：矿泉水 （饮料/矿泉水/无） 【人照相似】：9.5 【服务内容】：超大班 【服务过程】: 桃子刚来的时候就一眼爱上，忍到周六果断约头课。一见面一身红裙非常性感诱人，拉着小手摸着胸聊会天，感觉来了开始进入正题。小桃还算比较敏感，身体反映给的很足，让我很有满足感，后面弟弟在小桃的把玩下也是缴械投降。
花名: #邱酱 身高:165 体重:96 年龄:19 职业:女仆 三围：B➕ 兴趣爱好（可聊话题）： 游戏，喝酒，情感
❤1
Showing the 12 most recent of 15 posts we hold for @sz_cc_info. 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 — 611,666 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“苏州橙C女仆档案” (@sz_cc_info), 238 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/sz_cc_info.
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.