Channel
@chnsz3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,282subscribers
+196 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002822322904 |
|---|---|
| Type | Channel |
| Usernames | @chnsz3 @SZzw3 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/chnsz3 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 16 Sept 2026, 16:37 | 1,282 | +4 |
| 15 Sept 2026, 21:58 | 1,278 | +6 |
| 12 Sept 2026, 15:19 | 1,272 | +3 |
| 12 Sept 2026, 01:01 | 1,269 | +4 |
| 8 Sept 2026, 17:59 | 1,265 | +6 |
| 7 Sept 2026, 07:37 | 1,259 | +30 |
| 3 Sept 2026, 02:12 | 1,229 | +1 |
| 2 Sept 2026, 16:09 | 1,228 | +19 |
| 30 Aug 2026, 20:24 | 1,209 | +2 |
| 30 Aug 2026, 06:36 | 1,207 | +11 |
| 28 Aug 2026, 02:34 | 1,196 | +4 |
| 27 Aug 2026, 09:37 | 1,192 | +13 |
| 24 Aug 2026, 16:56 | 1,179 | +4 |
| 24 Aug 2026, 07:34 | 1,175 | +37 |
| 20 Aug 2026, 22:52 | 1,138 | +8 |
| 20 Aug 2026, 08:22 | 1,130 | +7 |
| 18 Aug 2026, 00:42 | 1,123 | +5 |
| 17 Aug 2026, 11:33 | 1,118 | +14 |
| 14 Aug 2026, 18:27 | 1,104 | -1 |
| 14 Aug 2026, 04:18 | 1,105 | first reading |
5 posts held, back to 1 July 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 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
12 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 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 4 of the 5 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 1 July 2026 to 31 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.
深港传奇，#宝安 —— 宝安大仟里 Baiyinhui——热情不寂寞，场子有温度，不冷场，整体氛围比较热闹，主营啤酒系列。 • 阵容： 60+优质佳丽驻场，风格多样，满足您的不同审美与陪伴需求。 • 消费透明：小时场 • 低消： 1796 酒水三打 • 演员：300-400/小时 • 管家：300 • 经理：300 • 服务： 百分之十服务费 • 保障：#小澜全程保驾护航 定最顶的房，抱最美的姑娘，做最野的狼，吻最喜欢的姑娘。
Telegram必备的搜索引擎，极搜JISOU帮你精准找到，想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7700028844
#深圳商k #制服诱惑 #商K #黑丝大长腿 #商务ktv #深圳摸摸唱 😀😀😀有些大哥问夜场演员跟技师又有什么区别？话真的不能这么说呀，一般商K上班的女生比较年轻，颜值、身材等综合素质还可以，通常文化程度普遍不高， 😀😀😀😀父母常年不在身边，很小就出来打工，但是攀比心大，基本上没有真正的好朋友。每次没有被挑选上的演员会极度的缺乏安全感。 🙃😀😀😀如果哪天在商K，你看着很漂亮的女生，等下班的时候，你看她的穿着样貌以及素颜时候的模样，就知道她心中的柔弱了。 🦋电报：@SZ9492 🦄机器人：@szsz01_bot 📞电话：13467824985
❤3
深港传奇，#龙华 —— 金皇大酒店 金皇 ——做氛围夜场。年轻局、颜值局、情绪局，玩的就是感觉 • 阵容： 150+优质佳丽驻场，风格多样，满足您的不同审美与陪伴需求。 • 消费透明：小时场—片场 • 低消：1488 • 妹妹：300/小时 • 片场：1200 陪到课离 • 公主：300 • 打碟：400/小时 ·备注：抵消指果盘小吃加任意酒水，小费另算 保障：#深圳小澜 做高质量安排，包厢有氛围，姑娘有颜值，体验有感觉。
❤7
深港传奇，#福田 —— 红树湾壹号 好乐迪 ——主打夜生活氛围的嗨场，不是传统唱K场，氛围感拉满，年轻颜值局，玩的就是感觉 • 阵容： 200+优质佳丽驻场，风格多样，满足您的不同审美与陪伴需求。 • 消费透明：小时场 • 低消：1680 • 妹妹：400 /小时 • 管家：500 • 经理：400 • 服务：10% ·备注：抵消指果盘小吃加任意酒水，小费另算 保障：#深圳小澜 做高质量安排，包厢有氛围，姑娘有颜值，体验有感觉。
❤2
Showing the 5 most recent of 5 posts we hold for @chnsz3. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳商K/摸摸唱/小时场/商务场🅥” (@chnsz3), 1,282 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/chnsz3.
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.