Telegram RegisterThe public register of Telegram

Channel

深圳会所92/94资源🅥

@chnsz6

2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,835subscribers

+56 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002828607540
TypeChannel
Usernames@chnsz6 @szzw6
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/chnsz6

Growth

3,7793,8353,8077 August 2026 — 3,779 subscribers8 August 2026 — 3,780 subscribers8 August 2026 — 3,792 subscribers10 August 2026 — 3,799 subscribers11 August 2026 — 3,810 subscribers13 August 2026 — 3,825 subscribers14 August 2026 — 3,835 subscribers7 August 202614 August 2026
7 measurements spanning 7 days, net +56. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,771–3,843 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 20:383,835+10
13 Aug 2026, 08:143,825+15
11 Aug 2026, 12:583,810+11
10 Aug 2026, 16:413,799+7
8 Aug 2026, 17:383,792+12
8 Aug 2026, 00:523,780+1
7 Aug 2026, 17:473,779first reading

Engagement

17 posts held, back to 27 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.2%
avg views ÷ 3,835 subscribers
Avg views / post
1,430
2 posts measured
Reaction rate
0.21%
reactions ÷ views · ER floor
Posts in window
2
of 17 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held17 (27 May 20263 August 2026)
Views total2,853
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:13 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.

What this channel posts

Video runtime
37s
Average length
9s

Measured directly from 4 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.

Reaction mix

66 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 84.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5684.8%
👍1015.2%

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 14 of the 17 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 66reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 27 May 2026 to 3 August 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.

Recent posts

3 Aug 2026, 14:31 UTC783 views2 reactionsread 8 August 2026
Video

🤥《君子之道》 为少女立心·为少妇立命 为人妻继绝学·为寡妇开太平 喜萝莉,不以其身体娇小而嫌之为·仁 喜少女、不以其青春懵懂而弃之为·义 喜少妇、不以其嫁他人而厌之方为·诚 喜熟女、不以其年长成熟而鄙之为·恒 喜花女、不以其无法相伴而毁之是·智 🔴君子五德:仁、义、诚、恒、智 预约联系小澜TG:@SZ9492 电话☎️:13467824985 深圳娱乐反馈频道:https://t.me/chnsz4

👍2

19 Jul 2026, 14:22 UTC≈2,070 views4 reactionsread 8 August 2026
Video

😀😀😀😀白天拼命搞钱,晚上认真享受;赚钱是为了生活,放松也是生活。 😀😀😀😀如果生活给了你苦,那就来小澜找点甜。吃爱情的糖,做海底的王,以 SPA 的名义,邂逅有趣的灵魂,治愈一天的疲惫。 🔴我们的宗旨:帅哥别动,美女全自动。您只负责开心“在这”😔😒😏😖😩😣😫😖 预约联系小澜TG:@SZ9492 电话☎️:13467824985

4

10 Jul 2026, 19:44 UTC≈2,620 views7 reactionsread 8 August 2026
Photo

🤓今天小澜刚好过来了深圳北这边顺便体验一下,随机找了个合作比较久的店铺进行考察,确实没让人失望,状态在线,氛围也到位,就是环境差了点,也跟老板讲过几次 把环境还是要做好一点,让客户有更好的体验,说实话,已经有几个月没出来感受了,这次一来,确实能明显感觉到深圳现在的整体体验感越来越好了。今天玩的111号是零零后,真人对版 杯罩C 摸起来软绵绵的 在侧躺吃奶的过程中 稍微扣了几下B 那水流的 哗啦啦就出来了,这种触感体验还是不错,就是还是不是很放的开。 身材微胖,摸起来的时候还是蛮舒服的,喜欢这种类型的可以试试 😛花同样的预算,能拿到的体验明显 扎实。玩法互动,都比之前更成熟。兄弟们如果最近想放松一下,可以提前联系#小澜 😛资源情况、场地安排、适合什么类型,都可以提前沟通清楚,避免白跑一趟。 📱深圳娱乐体验找小澜,安排稳,少走弯路。 联系方式: 电报:@SZ9492 QQ:3422914751 (单点复制) 电话:1346

7

17 Jun 2026, 17:05 UTC≈3,930 views16 reactionsread 8 August 2026
Video

😀😂深圳会所营业中,部分店有情趣变装,床前艳舞,“69式鲍汁奶香宴 ”😀😀😀 😀😀要预约的赶紧联系 #小澜 来体验,只推荐精品店铺,颜值优质妹妹,不踩坑,帮您避雷,有比我贵比我便宜的,但是一定没有我靠谱预约联系点击下方联系方式!😍😍 😍😍😍😛TG:@SZ9492 😎😛😛😛电话 13467824985

16

6 Jun 2026, 05:25 UTC≈4,650 views16 reactionsread 8 August 2026
Photo

深圳92/94会所 周末了各位大哥们,又到周末了,忙了一周也该放松一下。 😎😎🤓😛😎😝😎😋🤓😛 深圳92/94会所资源在线,年轻会玩双飞更刺激 同时点两个骚货是什么感觉?一个互相舔奶头,一个胸推指划大腿。让您射一米高到起飞联系小澜预约即可,主打一个配合度高,体验感足,让你从进门到结束都爽死人! 😀😂😀😀😀😀😀😀😀 想安排的兄弟提前预约小澜给你稳稳安排。 联系方式:😀😀😀 电报:@SZ9492 QQ:3422914751 (单点复制) 电话:13467824985 机器人:@szsz01_bot

11👍5

27 May 2026, 18:03 UTC≈6,940 views5 reactionsread 8 August 2026
Photo

📱📱📱📱【深圳会所导航 · 小澜频道】 📱本人深耕深圳会所行业多年,拥有六年真实带玩经验,坚持实地筛选店面,只做口碑与体验兼顾的优质资源。 拒绝键盘推荐,拒绝随意乱推,不辜负每一位远道而来的朋友。 感谢各位老板一路以来的信任与支持📱 ⛔️ 避免走丢加入合集 ⛔️ 流程风俗词讲解

👍32

27 May 2026, 17:58 UTC≈3,430 views2 reactionsread 8 August 2026
Photo

📍光明区 公明/金仪轩 点击进入 公明上村/浩轩 点击进入 田寮/源点 点击进入 📍坪山区 上坝/金福湾 点击进入 📍盐田区 沙头角/康城养生 点击进入 【预约联系方式👇·不跑空不排队】 ❤️电报:@SZ9492 😀QQ:3422914751 【单点复制】 ☎️电话直通:13467824985 🤖机器人:@szsz01_bot 【电话未接优先电报QQ留言】

2

27 May 2026, 17:54 UTC≈2,820 views2 reactionsread 8 August 2026
Photo

【店 名】:#金福湾 【营业时间】:午12点-凌晨5点 【位 置】:#坪山区 #龙田竹坑 【联系方式】:电报:@SZ9492【建议直接✈️联系】 QQ:3422914751 【单点复制】 【价 格】:468 注:📱店内有 免费过夜、饮品🧃、桌球🎱 【服务类型】:#92/94 【特 色】:美女多位 可挑可选 不满意就换。 📱📱📱📱📱📱📱📱不预约,不接待!打车前来可报销20元车费 🔖報告投稿 【反馈报告】: 技师照片在下方评论区😳

2

27 May 2026, 17:43 UTC≈2,390 views0 reactionsread 8 August 2026
Photo

【店 名】:#康城·养生 【营业时间】:午12点-凌晨5点 【位 置】:#盐田区 #山海地铁附近 【联系方式】:电报:@SZ9492【建议直接✈️联系】 QQ:3422914751 【单点复制】 【价 格】:468 注:📱店内有 免费过夜、饮品🧃 【服务类型】:#92/93 【特 色】:多位美女,环境优雅, 轻松氛围更有感觉 📱📱📱📱📱📱📱📱不预约,不接待!打车前来可报销20元车费 🔖報告投稿 【反馈报告】: 技师照片在下方评论区😳

27 May 2026, 17:35 UTC≈2,270 views1 reactionsread 8 August 2026
Photo

【店 名】:#源点·影视 【营业时间】:午12点-凌晨5点 【位 置】:#光明区 #田寮 【联系方式】:电报:@SZ9492【建议直接✈️联系】 QQ:3422914751 【单点复制】 【价 格】:468 注:📱店内有 免费过夜、提供零食,水果🍉,饮品,有影视沐足。 【服务类型】:#92/94 【特 色】:年轻的多位,氛围感强、可挑可选。 📱📱📱📱📱📱📱📱不预约,不接待!打车前来可报销20元车费 🔖報告投稿 【反馈报告】: 技师照片在下方评论区😳

1

27 May 2026, 17:17 UTC≈2,040 viewsread 8 August 2026
Photo

【店 名】:#浩轩·养生 【营业时间】:午12点-凌晨5点 【位 置】:#光明区 #公明上村 【联系方式】:电报:@SZ9492【建议直接✈️联系】 QQ:3422914751 【单点复制】 【价 格】:468 注:📱店内有 免费过夜、独立淋浴、可免费泡澡、特饮🧃 【服务类型】:#92/94 【特 色】:泡澡技师帮搓、美女多多,任君挑选。 📱📱📱📱📱📱📱📱不预约,不接待!打车前来可报销20元车费 🔖報告投稿 【反馈报告】: 技师照片在下方评论区😳

Showing the 12 most recent of 17 posts we hold for @chnsz6. 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

Citation-graph rank — 11,571 of 1,350,102entries 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.

Mentions

Named by 5 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.

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“深圳会所92/94资源🅥” (@chnsz6), 3,835 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/chnsz6.

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.