Posted without readable text
❤6

Channel
@CSLiu3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
75,206subscribers
+19,879 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002442214952 |
|---|---|
| Type | Channel |
| Username | @CSLiu3 |
| Description | 本频道:出击报告&长沙电报吃瓜 交流群: @Xunhua0731 地下说唱: @CSLiuSan 联系柳三: @LiuSMBot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/CSLiu3 |
Other / unclassifiable — 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 64% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:59 | 75,206 | +1,255 |
| 16 Sept 2026, 16:38 | 73,951 | +1,159 |
| 14 Sept 2026, 16:55 | 72,792 | +731 |
| 13 Sept 2026, 04:36 | 72,061 | +688 |
| 11 Sept 2026, 04:59 | 71,373 | +2,108 |
| 8 Sept 2026, 08:20 | 69,265 | +1,867 |
| 5 Sept 2026, 02:36 | 67,398 | +900 |
| 3 Sept 2026, 09:52 | 66,498 | +602 |
| 2 Sept 2026, 01:43 | 65,896 | +419 |
| 1 Sept 2026, 03:36 | 65,477 | +443 |
| 31 Aug 2026, 05:13 | 65,034 | +564 |
| 30 Aug 2026, 01:43 | 64,470 | +334 |
| 29 Aug 2026, 03:38 | 64,136 | +546 |
| 28 Aug 2026, 01:53 | 63,590 | +439 |
| 27 Aug 2026, 00:07 | 63,151 | +483 |
| 25 Aug 2026, 22:34 | 62,668 | +289 |
| 24 Aug 2026, 23:07 | 62,379 | +467 |
| 23 Aug 2026, 12:38 | 61,912 | +561 |
| 21 Aug 2026, 22:14 | 61,351 | +882 |
| 20 Aug 2026, 18:24 | 60,469 | first reading |
78 posts held, back to 2 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 89 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.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 78 (2 August 2026 – 19 September 2026) |
| Views total | 333,870 |
| Reactions total | 910 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 00:04 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.
Lifetime counters from Telegram’s own channel header, read 20 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 23 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.
1,346 reactions across 78 posts, in 13 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 942 | 70.0% | |
| 👍 | 224 | 16.6% | |
| 😱 | 71 | 5.27% | |
| 😨 | 20 | 1.49% | |
| 👎 | 19 | 1.41% | |
| 🤡 | 16 | 1.19% | |
| 🤣 | 15 | 1.11% | |
| 👏 | 14 | 1.04% | |
| 🔥 | 10 | 0.743% | |
| 💩 | 7 | 0.52% | |
| 😁 | 3 | 0.223% | |
| 🥰 | 3 | 0.223% | |
| 🤓 | 2 | 0.149% |
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 78 of the 78 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 1,346 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 78 most recent posts we hold, published 2 August 2026 to 19 September 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.
Posted without readable text
❤6
全网🙁纠纷记录 见面面试期不满意,100%退介绍费 资源真实有效,全部附带和妹子本人视频录屏认证,见面先看视频验证 让你享受无套和内射感受 并且SM COS服装应有尽有! 见面面试不满意,%100退还介绍费! 包见面,包上床,货不对版包退换! 【夜色包养选妃频道全网资源: @yese7988 【夜色双向机器人: @yese988_bot 【夜色包养伴游联系方式】:@yese798
❤13👍1
关于苟馨文的采访: 1、基本上没问到什么刺激的问题,我以为至少会挖个坑啥的,结果也没有,害的柳三白提防了。 2、所以也没出现“无可奉告”的情况,基本上有啥说啥了。 3、感觉苟馨文有点紧张。 4、为什么不把截图这一段放出来,这才是观众想看的啊! 5、《美国丽人》很不错,大家有空也可以看看。
❤10
采访长沙柳三秒全过程: 一,入圈 22年入圈,23年底开始开始做自己的频道,前期频道不温不火,24年6月写小悦悦老师的事情开始火了,果然吃瓜看热闹才是刚需。小悦悦事件中舔狗表现出来扬言要报复的癫狂状态,让柳三知道到了保护自己身份隐私的重要性。一个是鱼龙混杂的嫖娼市场,一个是人云亦云的网络社区,两个结合起来简直就是奇异的冒险记,柳三可不愿冒险,他想当马克吐温,而不是汤姆索亚。 二,流量与权利 火了,有流量了,事情就开始变得复杂了。柳三前后跟一些新群合作过,帮助新群引流,合作也只是短期的互利关系而已,各取所需,没有永远的朋友,只有永远的利益。既然要竞争,那就斗争,看看谁的流量能盖过谁,物竞天择,适者生存,强势才是生存的基础,怯懦退缩只能任人宰割。柳三把出击市场的简单划分为三方:出钱的、挣钱的、既出钱又挣钱的。 柳三自己就是既出钱又挣钱的。当然出击市场远不如三分势力这么简单,人的立场一直在改变,蛊惑人心的妖言一直都有,谁带节奏带起…
❤17
炮炮:技师下海 炮炮这花名取得确实不太走心,我估摸着,是因为想叫“泡泡”但重名了吧——扶贫那边估计也是因为重名改成了“大泡泡”。 妹子光看上榜照卖相还是蛮好的,开5张有蛇有69,年龄也是柳三现在最喜欢的年龄范围,就是不知道人照能有几分了。 开课的位置在远洋,这楼里不是成年的妹子我是不太敢来的,不过炮炮这23岁的资料年龄还是没太多可担心的。 见到真人以后,还行吧,基本能对版,肯定没照片好看,但最大的问题还是体形。 估计是有些管不住嘴,妹子体形明显比照片看起来要大一圈,但也没到坦克的程度,只能说是丰腴。 虽然有点小肚子,但是这妹子绝对属于雌激素分泌旺盛的类型,整个细皮嫩肉的。 柳三估摸着,这干起来肯定舒服。 于是交了水费,稍微嘴甜调情了几句,就跟着妹子去洗澡去了。 妹子情商还是不错的,聊天的感觉有来有回的,后来一问知道她是在广东会所里上班的,因为那边查得严,就来长沙开课试试。 果然,这种进过会所的妹子都挺会聊天的。 洗完上床…
❤14
【昵称】:炮炮 【标签】:技师下海 【年龄】:25 【身高】:163 【身材】:B 【课表】:口 做 共浴 69 舌吻 【人照对版】:体形比较丰腴,但没到坦克的程度,照片基本对版,睡衣那张基本就是本人了 车牌: https://t.me/fk0731/14850
❤8
Posted without readable text
❤26👍6👏2
推荐一枚成都重庆“视频大网黄” 嫩妹 御姐 外围 会所 通吃 ✨ 喜欢拍老师的黄色小视频✨ 他的频道进去就出不来啦❗️ 点此查看部分实拍作品 🔴 点此关注云长唯一频道 🔴 成都重庆两地出击😂 实事求是 爱说真话 不尬吹🥳 云长出品必属精品🥇
❤11
妮妮酱:可爱的小迷糊 “你好高啊……”本来想凑上去亲一下她,哥布林柳三尴尬的发现不垫个脚尖还有点够不到。 “是这个鞋高,”妮妮酱马上贴心地光脚站在地上,“我其实也就166。” 但她资料其实写的是170,而且很明显的,即使她光脚,我穿鞋,她依然比哥布林柳三高了一截。 当时场面一度非常尴尬。 妮妮酱绝对是个迷糊鬼,我在她的指挥下足足绕了有20分钟,才终于找到了她的课室。 先不说我出发以后,一路上她全程失踪状态,直到我到了楼下等了10分钟,她才告诉我她“手机忘了充电关机了”。当时我只当是下头妹随口撒谎,见到真人以后我才意识到,这真是她干得出来的事。 她是临时在这里开课的,据她自己说,她当时找这个房间都找了足足半个小时,还是在小区里崩溃大哭引起了保安的注意,在保安的帮助下才找到的地方。 如果考虑到这一点,我能在20分钟之内到她课室(甚至没有迟到),简直可以说是一个了不得的奇迹了。 妮妮酱本人和照片几乎一样,但是气质上嘛…… “我今…
❤21🤡2🥰2
【昵称】:妮妮酱 【标签】:可爱的小迷糊 【年龄】:18 【身高】:10 【身材】:B 【课表】:口 做 共浴 69 【人照对版】:人照基本对版,第一张基本就是本人,真人是高高瘦瘦的 车牌: https://t.me/fk0731/15119
❤9
昨天这张截图就在几个群里传,当时没怎么当回事,现在看起来有点哈人啊😨😨😨
😨20❤5
有狼友自述在绿地空间出击 #馨馨 的时候遇到帽子哥突袭。 当时帽子哥可能是在抓隔壁的老师,弄得声音很大,老哥觉察不对劲所以刚刚进门就打算跑路(不到1分钟)。 因为时间太短了不好固定证据,便衣估计是嫌麻烦就直接给他放了(正常情况嫖娼未遂也一样是行政拘留的)。 馨馨应该是被帽子哥带走了(利用老师抓鸡头抓嫖客,常规操作了)。 最后,老哥表示馨馨颜值确实高(莫名其妙被种草了哈哈哈哈)
😱20❤10
Showing the 12 most recent of 78 posts we hold for @CSLiu3. 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.
@CSLiu3 edited 1 post 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“长沙寻花问柳三秒” (@CSLiu3), 75,206 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CSLiu3.
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.