📊 6条车评,综合评分9.48 👧:#宋婉儿 🌐:#雨花区 💦:#7p #12pp 🏷️:#御姐 #包夜 #服务系 #胸推 #制服诱惑 #毒龙 #口爆 📞:@songwaner 🤖:双向联系宋婉儿 ✍️:给宋婉儿写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
❤1

Channel
@CSxcfgkb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
42,166subscribers
+13,717 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001410735917 |
|---|---|
| Type | Channel |
| Username | @CSxcfgkb |
| Created | Between 1 March 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/CSxcfgkb |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 65% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 15:19 | 42,166 | +767 |
| 11 Nov 2026, 13:11 | 41,399 | +559 |
| 9 Nov 2026, 17:44 | 40,840 | +393 |
| 8 Nov 2026, 09:06 | 40,447 | +178 |
| 7 Nov 2026, 04:36 | 40,269 | +238 |
| 6 Nov 2026, 05:57 | 40,031 | +238 |
| 5 Nov 2026, 06:01 | 39,793 | +246 |
| 4 Nov 2026, 05:27 | 39,547 | +243 |
| 3 Nov 2026, 06:36 | 39,304 | +313 |
| 2 Nov 2026, 03:01 | 38,991 | +349 |
| 1 Nov 2026, 04:59 | 38,642 | +284 |
| 31 Oct 2026, 04:56 | 38,358 | +320 |
| 30 Oct 2026, 03:34 | 38,038 | +320 |
| 29 Oct 2026, 02:31 | 37,718 | +312 |
| 27 Oct 2026, 21:18 | 37,406 | +270 |
| 26 Oct 2026, 20:45 | 37,136 | +180 |
| 25 Oct 2026, 20:31 | 36,956 | +369 |
| 24 Oct 2026, 17:30 | 36,587 | +219 |
| 23 Oct 2026, 19:31 | 36,368 | +284 |
| 22 Oct 2026, 22:54 | 36,084 | first reading |
247 posts held, back to 8 August 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 169 pages 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. It is computed over the 39 of 110 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 247 (8 August 2026 – 14 November 2026) |
| Views total | 69,138 |
| Reactions total | 54 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 14:45 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 163 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.
131 reactions across 80 posts, in 12 distinct kinds. The most used accounts for 80.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 105 | 80.2% | |
| 👍 | 7 | 5.34% | |
| 🤣 | 7 | 5.34% | |
| 💯 | 3 | 2.29% | |
| 😁 | 2 | 1.53% | |
| 🌚 | 1 | 0.763% | |
| 🌭 | 1 | 0.763% | |
| 🎉 | 1 | 0.763% | |
| 👏 | 1 | 0.763% | |
| 🔥 | 1 | 0.763% | |
| 🗿 | 1 | 0.763% | |
| 🥴 | 1 | 0.763% |
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 106 of the 247 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 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 247 most recent posts we hold, published 8 August 2026 to 14 November 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.
Telegram’s own ‘edited’ marker: 7 of 110 posts held from the last 30 days (6.36%) 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).
📊 6条车评,综合评分9.48 👧:#宋婉儿 🌐:#雨花区 💦:#7p #12pp 🏷️:#御姐 #包夜 #服务系 #胸推 #制服诱惑 #毒龙 #口爆 📞:@songwaner 🤖:双向联系宋婉儿 ✍️:给宋婉儿写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
❤1
重要通知: 💕💕因机器人功能bug,车评报告无法通过榜单快捷链接提交,可通过手动输入老师花名的方式进行评价,具体操作指南如上视频所示,此外附近功能可暂时通过我们的小程序进行实时查看! 11月出击五次及以上的狼友可凭借【📋我的车评】截图进行报告返现100元,限领一次,五份报告需不同老师(工兵报告除外)!
😘😘😘欢迎狼友亲身体验😘😘😘 长沙各区92店 #手推94 【店 名】:长沙92-94丝足会所🤬 【营业时间】:中午12点—凌晨四点 【位 置】:德思勤、雨花、开福、星沙、望城、天心、芙蓉、岳麓、五一长沙全区都可安排 会所公开频道:https://t.me/spa0000000 会所交流群:https://t.me/spa0000001 😀🙄😯😧😮🤮🤮 联系方式: ⚡️📱微信 : A1199809 ⚡️📱QQ :1704784994 ⚡️😃电报:客服贝贝 ⚡️😀双向机器人:客服贝贝 【技师人数】:12~20 【价 格】:🥰半裸369 🥰全裸399💰 【安 全 性】:安全 【年 龄】:有00后妹子18-26 【服务内容】:水床服务😀洗澡性感DJ舞曲搭配艳舞诱惑😀环游全身摩擦🐜十指弹琴🎹360度调情😀激情娇喘叫床😇神油滚蛋妙手回春快乐旋转✈️可手可丝足出💦足推💦胸…
📊 0条车评,综合评分 👧:#婉婉 🌐:#雨花区 💦:#6p #12pp 🏷️:#嫩妹 #BBW #六九 #舌吻 #69 📞:@wanwan1029 🤖:双向联系婉婉 ✍️:给婉婉写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
❤1
📊 3条车评,综合评分8.46 👧:#小景甜 🌐:#雨花区 💦:#7p #pp 🏷️:#御姐 #六九 #制服诱惑 #舌吻 #69 #口爆 📞:@Rb888k 🤖:双向联系小景甜 ✍️:给小景甜写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
📊 9条车评,综合评分9.21 👧:#珑宝 🌐:#雨花区 💦:#6p #12pp 🏷️:#嫩妹 #六九 #制服诱惑 #69 #接吻 #上门 📞:@xibao246 🤖:双向联系珑宝 ✍️:给珑宝写报告 🐺狼友印象:#玲珑如泉,宝若星辰 🔍查看报告 | 🐺添加印象
👧🏻岳麓区老师导航 梦梦500 小涵500 夏夏500 顾里500 小诺500 小意600 小姿600 婉婷600 小小600 晗晗600 偲偲600 芭比600 吱吱700 白鹿700 甜豆豆600 李汪洋700 👧🏻芙蓉区老师导航 小梅600 娇娇600 晶晶700 👧🏻天心区区老师导航 福宝600 洛水600 木子800 糖果儿800 👧🏻开福区老师导航 小兔 伊伊600 小莹600 小怡600 困困600 果冻600 娜娜800 小绵神600 小奶猫600 姜艺蒽700 李冰冰700 萌小岚1400 奶糕BB700 👧🏻望城区老师导航 溜溜600 👧🏻星沙老师导航 椰子400 …
❤1
👧🏻雨花区老师导航 瑶瑶500 满满500 叮叮500 奶柚500 婉若500 思思500 心儿600 优优600 允瑛600 菜菜600 慕斯600 兔兔600 诺浠600 小欣600 妍妍600 牙牙600 卿卿600 木冉600 思颖600 安宁600 云酥600 诗瑶600 懒懒600 湫湫600 奶昔600 思语700 诗诗700 小渝700 妮妮700 姗姗700 雪王700 小云700 杏子700 糖霜700 小可700 诗诗700 洲洲800 尧尧1800 小嘉嘉 小西贝 小丸子500 小冰棍500 蛋…
📊 0条车评,综合评分 👧:#娇娇 🌐:#芙蓉区 💦:#6p #11pp 🏷️:#嫩妹 #制服诱惑 #上门 📞:@Jiao9888 🤖:双向联系娇娇 ✍️:给娇娇写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
📊 0条车评,综合评分 👧:#小诺 🌐:#岳麓区 💦:#5p #9pp 🏷️:#包夜 #嫩妹 #胸推 #制服诱惑 📞:@xiaonuoxixi188 🤖:双向联系小诺 ✍️:给小诺写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
📊 0条车评,综合评分 👧:#牙牙 🌐:#雨花区 💦:#6p #11pp 🏷️:#嫩妹 #接吻 #上门 📞:@csyaya09 🤖:双向联系牙牙 ✍️:给牙牙写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
📊 18条车评,综合评分9.11 👧:#果冻 🌐:#开福区 💦:#6p #10pp 🏷️:#包夜 #嫩妹 #六九 #舌吻 #69 #上门 📞:@an415415 🤖:双向联系果冻 ✍️:给果冻写报告 🐺狼友印象: 🔍查看报告 | 🐺添加印象
Showing the 12 most recent of 247 posts we hold for @CSxcfgkb. 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.
@CSxcfgkb edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 6 posts on @CSxcfgkb as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Named by 4 registered channels — 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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“长沙寻春坊上榜认证” (@CSxcfgkb), 42,166 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/CSxcfgkb.
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.