【老师艺名】:姗姗 【所在位置】:柳州 #城中区 【身高体重】:163cm,48kg 【凶器罩杯】:B+ 【水费时间】:p600-pp1100 【服务项目】:🐍💋 69 👄爆 【自我介绍】:会莞式,服务好! 【联系方式】: @niu18k
👍1

Channel
@LZXCGKB
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
21,459subscribers
+895 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002118584691 |
|---|---|
| Type | Channel |
| Username | @LZXCGKB |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/LZXCGKB |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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, 16:22 | 21,459 | +62 |
| 16 Sept 2026, 10:18 | 21,397 | +62 |
| 13 Sept 2026, 22:42 | 21,335 | +33 |
| 12 Sept 2026, 08:58 | 21,302 | -18 |
| 10 Sept 2026, 03:59 | 21,320 | +78 |
| 6 Sept 2026, 21:55 | 21,242 | +54 |
| 4 Sept 2026, 09:57 | 21,188 | +48 |
| 2 Sept 2026, 20:25 | 21,140 | +22 |
| 1 Sept 2026, 20:27 | 21,118 | +25 |
| 31 Aug 2026, 22:05 | 21,093 | +12 |
| 30 Aug 2026, 23:27 | 21,081 | +20 |
| 29 Aug 2026, 20:04 | 21,061 | +35 |
| 28 Aug 2026, 22:44 | 21,026 | +20 |
| 28 Aug 2026, 01:13 | 21,006 | +24 |
| 27 Aug 2026, 02:18 | 20,982 | +9 |
| 25 Aug 2026, 23:32 | 20,973 | +30 |
| 24 Aug 2026, 21:05 | 20,943 | +27 |
| 23 Aug 2026, 05:43 | 20,916 | +6 |
| 21 Aug 2026, 18:28 | 20,910 | +50 |
| 20 Aug 2026, 12:25 | 20,860 | first reading |
41 posts held, back to 5 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 56 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 3 September 2026 |
|---|---|
| Posts held | 41 (5 August 2026 – 3 September 2026) |
| Views total | 26,379 |
| Reactions total | 34 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 17:11 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 19 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.
144 reactions across 36 posts, in 9 distinct kinds. The most used accounts for 69.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 100 | 69.4% | |
| 🤮 | 22 | 15.3% | |
| 💩 | 7 | 4.86% | |
| 👍 | 5 | 3.47% | |
| 🤡 | 4 | 2.78% | |
| 👎 | 2 | 1.39% | |
| 🔥 | 2 | 1.39% | |
| 🎉 | 1 | 0.694% | |
| 🥰 | 1 | 0.694% |
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 39 of the 41 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 41 most recent posts we hold, published 5 August 2026 to 3 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.
【老师艺名】:姗姗 【所在位置】:柳州 #城中区 【身高体重】:163cm,48kg 【凶器罩杯】:B+ 【水费时间】:p600-pp1100 【服务项目】:🐍💋 69 👄爆 【自我介绍】:会莞式,服务好! 【联系方式】: @niu18k
👍1
【老师艺名】:花花 【所在位置】:柳州 #鱼峰区 【身高体重】:高156重82 【凶器罩杯】:C+ 【水费时间】:500P(45分钟) 【服务项目】:洗吹做,按摩,胸推,制服,各种姿势爱爱 【自我介绍】:热情不催钟 【联系方式】:@huahuayn
❤1
玉林1.6万人的群都没老师入驻? https://t.me/YL_XCDD
🤡4💩2❤1
北海1.6万人的群都没老师入驻? https://t.me/BH_XCDD
💩5
【老师艺名】:小丸子 【所在位置】:柳州 #城中区 【身高体重】:163 92斤 【凶器罩杯】:C+ 【水费时间】:600p45分钟 1200pp90分钟 【服务项目】:陪🛀 kisi 无套口 浴室口 深🐒 情趣 【自我介绍】:哥哥好呀 本人皮肤白皙 光滑细腻 待哥哥如男友哦 希望哥哥温柔对待 【联系方式】:@xiaowanzi1230
【老师艺名】:乐安 【所在位置】:柳州 #城中区 【身高体重】:165–90 【凶器罩杯】:B➕ 【水费时间】:p60040分钟 pp120080分钟 【服务项目】:亲💋 无套口 69 调情 亲咪咪 鸳鸯浴 丝袜诱惑 情趣内衣 制服 主动热情 【自我介绍】:刚下海 【联系方式】:@xlaxlan
❤1
【老师艺名】:可乐妹妹 【所在位置】:柳州 #鱼峰区 【身高体重】:161 92 【凶器罩杯】:B 【水费时间】:6/1 【服务项目】:全 【自我介绍】:服务好 健谈人照对版 【联系方式】:@AZzz5688
❤2
【老师艺名】:UU 【所在位置】:柳州 #城中区 【身高体重】:体重:83 身高:168 【凶器罩杯】:B 【水费时间】:700p 1400pp 夜3800 【服务项目】:鸳鸯浴,无🍑口,蛇纹,69,情趣丝袜,各种姿势 【自我介绍】:大长腿,女友体验,不冷场 【联系方式】:@uuaa987
❤6
【老师艺名】:小乖 【所在位置】:柳州 #城中区 【身高体重】:165 【凶器罩杯】:B+ 【水费时间】:p600(40分钟) pp1200(80分钟) 【服务项目】:kiss 舌吻(需要先刷牙谢谢) 无🍑口 鸳鸯浴💦 激情❤️爱爱 丝袜诱惑...... 【自我介绍】:初次下海 不抽烟 不喝酒 温柔体贴 可御可甜 女友感十足 望哥哥们喜欢💕 【联系方式】:@xg11ee
❤2
【老师艺名】:贝贝 【所在位置】:柳州 #鱼峰区 【身高体重】:164 85 【凶器罩杯】:b 【水费时间】:600p 1200pp 【服务项目】:69 🈚套口 鸳鸯浴 【自我介绍】:希望有个温柔的邂逅 【联系方式】:@beibeibaobao827
❤1
【老师艺名】:尹夏沫 【所在位置】:#城中区 【身高体重】:158 【凶器罩杯】:b 【水费时间】:650p 1200pp 【服务项目】:舌吻 69 鸳鸯浴 高跟 丝袜 jk 【自我介绍】:一个爱笑的女孩 努力成为柳州萝莉王 【联系方式】:@yinxiamo
❤7🥰1
【老师艺名】:七七 【所在位置】:柳州 #城中区 【身高体重】:160cm 【凶器罩杯】:B 【水费时间】:p600一课40分钟 pp1200二课80分钟 【服务项目】:🐍💋 无套口 69 调情 亲咪咪 鸳鸯浴 丝袜诱惑 情趣内衣 制服 主动热情 【自我介绍】:川妹子 【联系方式】:@Qinsey51066
❤1
Showing the 12 most recent of 41 posts we hold for @LZXCGKB. 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.
@LZXCGKB 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.
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.
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.
“柳州公开榜” (@LZXCGKB), 21,459 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/LZXCGKB.
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.