Channel
@sz8362
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
807subscribers
-83 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002697348048 |
|---|---|
| Type | Channel |
| Username | @sz8362 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/sz8362 |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 13 Sept 2026, 02:16 | 807 | -40 |
| 4 Sept 2026, 07:18 | 847 | -43 |
| 28 Aug 2026, 16:45 | 890 | no change |
| 28 Aug 2026, 16:30 | 890 | first reading |
16 posts held, back to 17 June 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 1 page 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 28 August 2026 |
|---|---|
| Posts held | 16 (17 June 2026 – 28 August 2026) |
| Views total | 901 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 16: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 8 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.
24 reactions across 9 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 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 9 of the 16 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 24 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 17 June 2026 to 28 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.
深圳9️⃣5️⃣➖9️⃣6️⃣💀☠️ 营业区域⚡️⚡️⚡️⚡️ 营业时间：下午14点-凌晨4点 （罗湖区24小时营业） 宝安区😅 福永公寓：可以安排零零后 固戍公寓：质量好颜值高 龙岗区😅 平湖会所：可安排零零后 坂田会所：质量很好 南联会所：环境很好，质量高 罗湖区😅 罗湖区，十多家门店，可安排附近门店，可安排海选，环境好质量好颜值高 深圳全区9️⃣4️⃣正常营业😀😀😀😀 😢:@sz7998 频道: https://t.me/sz8362 群组: https://t.me/sz6489 QQ😀: 3238847663
龙岗区 中心城9️⃣5️⃣ 9️⃣6️⃣ 会所 营业中 滴滴我 客服：@sz7998
今日9️⃣5️⃣ 9️⃣6️⃣ 营业中 安安 区 固戍 西乡 福永 95 96 龙岗区 坂田 南联中心城 95 96 罗湖区🉑️海选 需要安排咨询下方 客服：@sz7998
😝😜😝😜😜 现在95营业区域 宝安区😀南山区😀罗湖区😀龙岗区😀龙华区 😵罗湖区可安排海选🫤 😢：@sz7998 🤖：@sdf667bot
❤1
👍深圳全区👍优质门店👍 😢客服：@sz7998 🤖双向：@sdf667bot 😀预约：3238847663 QQ只预约和发位置 全区价格3️⃣9️⃣8️⃣—5️⃣9️⃣8️⃣位置不同价格不同 没预约按正常按摩接带待 ➡️ 宝安区⬅️ 松岗😀聚豪国际 悦达影视足道 花舟浴SPA 沙井😀嘉盛国际会所 爱思尼 福永😀星悦湾足道 机场😀希尔曼 石岩😀逸时光会所 西乡😀玫瑰会馆 ➡️南山区⬅️ 西丽😀涵梦健康会 青禾源空间 南头😀清池会所 青木会所 南油😀壹水汇 梵希秘境 蛇口😀玺悦沐足 ➡️ 福田区⬅️ 梅林😀金色阳光会馆 沙尾😀御足印象 岗夏😀文蔚水会 华强😀丽都城水会 ➡️罗湖区⬅️ 国贸😀沐晨水会 翠竹😀嘉晨公馆 ➡️…
❤5
深圳会所全区 94-95-96 🔥94服务流程：🐻推，👋推，🦶推，果冻漫游，吸皮过水，👅漫，鼻吸，海底捞月，等等项目流程，小妹🉑亲，🉑揉，🉑摸下路，👋🦶🐻出，价格：488 🔥95水会、会所：无套👄爆，花式毒龙，吃舔🥚🥚，玉指柔情，丝袜诱惑，无限挑逗，👅漫全身，🐻推全身，深🐒👄爆，等等项目内容，价格588 🔥96会所、公寓：梦幻联动，艳舞挑逗，吸🥚👅🥚，👄罐拔痧，美式、日式、英式毒🐉，倒挂金钩，🧊🔥吐珠，👅扫禁区，爱的魔力转圈圈，6️⃣9️⃣吃鲍，操盘花式👄爆出💦，价格788 选择佳丽：到现场选，不满意可以换，换到满意为止 客服：@sz7998 频道: https://t.me/sz8362 群组: https://t.me/sz6489 QQ: 3238847663
❤3
#深圳会所 #深圳丝足 #深圳94 🖤 深圳高端会所每日出勤人数45+ 新开高端场 00后10位在店 足控 口爆 兄弟福利来了！ 会所丝足做得特别到位，新妹子腿长脚嫩，丝袜控必备。 亮点： • 丝足全套（穿脱丝、足交、足踩、足吻） • 爆乳胸推（真奶大推、夹击、乳炮） 高档环境，安全私密，妹子配合度高。 想玩得舒服又尽兴的，直接私我。 私信我 直接发你最新小姐照片和价位。🚗🚕🚙所有分店“加钟双飞”提前报备给预约部长都可享受优惠，否则原价不动。💥 ✈️客服：@sz7998 🤖双向：@sdf667bot 24小时在线QQ: 3238847663 私密频道：https://t.me/+kuNgp2ywm20zNWVh #深圳会所 #深圳 #深圳会所00后 #深圳水会 没有预约按正常按摩接待 📱📱📱📱
❤1
深圳最顶娱乐 pinned a video
深圳最顶娱乐 pinned a photo
深圳最顶娱乐 pinned a video
♥️深圳 9️⃣5️⃣水疗会自营店 🥰⑨⑤全裸服务:💋 无套深喉口爆-冰火两重天-玉女缠身-毒龙舔蛋-伺浴-舌吻-颜射-69-跪式吹箫-倒立操口-胸推漫游-舌推漫游-扣B舔B-臀推磨棒-风情按摩-高跟制服丝袜诱惑丝足 保证⑨⑤口爆，杜绝骗子 【店长全程现场质保，如不是口爆，全额退款】 9️⃣5️⃣餐价 588元 ①个技师60分钟【服务时间内深喉口爆①次，送胸或臀①次】 9️⃣6️⃣ 餐价 788元 ①个技师80分钟 【服务时间内深喉口爆②次送胸或臀①次】👍 9️⃣7️⃣餐价 1100元 ①个技师140分钟 【服务时间内不限次数】👍 9️⃣7️⃣餐价 1100元 ②个技师一起服务70分钟(双飞双倍快乐)【服务时间内不限次数】👍 门店地址【深圳每个区域都有分店，详情请咨询客服】 门店直约前台经理 : @sz7998 双向机器人 : @sdf667bot 24小时在线QQ: 3238847663 私密频道：https:/…
❤5
🍎🍎🍎🍎🍎 🎖深圳顶级天花板SPA 95会所 😝🤩😜🤪📱📱📱📱 🎖深圳顶级天花板SPA 94会所 😅😇😢 #深圳全区 🥰请提前预约🥰 📱📱📱📱😀😃😀😃 大哥们，您要的丝袜、私密会所、胸推、口爆、毒龙、鲍鱼、服务都有！🔥先选人后消费 📱📱📱📱 好赌的爸，生病的妈，上学的弟，养家的她，需要您来帮忙！ 【免费停车 免费过夜】 深圳顶级95-94会所营业中，30多位年轻佳丽等待您挑选，00后坐镇，主打颜值技师。 各种类型，选择性多，服务、技术一流！ 「线下接待非中介资源充足约起来」 🚓🚑🚒🚐🛻 ✈️客服：@sz7998 🤖双向：@sdf667bot 私密频道：https://t.me/+kuNgp2ywm20zNWVh
❤1
Showing the 12 most recent of 16 posts we hold for @sz8362. 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 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳最顶娱乐” (@sz8362), 807 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/sz8362.
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.