Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳911(认证榜)

Channel

深圳911(认证榜)

@Yuoyoutan

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

103,533subscribers

+36,475 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001434489717
TypeChannel
Username@Yuoyoutan
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/Yuoyoutan

Topic

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 9 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.

Growth

67,058103,53385,295.57 August 2026 — 67,058 subscribers8 August 2026 — 67,375 subscribers9 August 2026 — 67,759 subscribers10 August 2026 — 68,227 subscribers11 August 2026 — 68,623 subscribers12 August 2026 — 68,983 subscribers13 August 2026 — 69,530 subscribers14 August 2026 — 70,511 subscribers16 August 2026 — 71,100 subscribers17 August 2026 — 71,670 subscribers18 August 2026 — 72,089 subscribers19 August 2026 — 72,516 subscribers20 August 2026 — 73,007 subscribers21 August 2026 — 73,699 subscribers22 August 2026 — 75,398 subscribers24 August 2026 — 76,819 subscribers25 August 2026 — 77,393 subscribers26 August 2026 — 77,534 subscribers27 August 2026 — 78,204 subscribers28 August 2026 — 78,980 subscribers29 August 2026 — 79,387 subscribers30 August 2026 — 79,645 subscribers31 August 2026 — 80,208 subscribers1 September 2026 — 80,330 subscribers2 September 2026 — 80,852 subscribers4 September 2026 — 81,163 subscribers6 September 2026 — 82,700 subscribers10 September 2026 — 84,612 subscribers12 September 2026 — 85,259 subscribers14 September 2026 — 85,601 subscribers15 September 2026 — 86,213 subscribers17 September 2026 — 87,346 subscribers29 September 2026 — 91,074 subscribers5 October 2026 — 93,778 subscribers9 October 2026 — 95,628 subscribers13 October 2026 — 98,335 subscribers14 October 2026 — 98,961 subscribers15 October 2026 — 99,166 subscribers17 October 2026 — 99,721 subscribers17 October 2026 — 100,502 subscribers18 October 2026 — 100,961 subscribers19 October 2026 — 101,277 subscribers20 October 2026 — 101,864 subscribers22 October 2026 — 102,240 subscribers23 October 2026 — 102,693 subscribers24 October 2026 — 102,988 subscribers25 October 2026 — 103,324 subscribers26 October 2026 — 103,533 subscribers7 August 202626 October 2026
48 measurements spanning 79 days, net +36,475. 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 61,587–109,004 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
26 Oct 2026, 02:26103,533+209
25 Oct 2026, 03:05103,324+336
24 Oct 2026, 05:00102,988+295
23 Oct 2026, 03:41102,693+453
22 Oct 2026, 00:48102,240+376
20 Oct 2026, 20:01101,864+587
19 Oct 2026, 18:10101,277+316
18 Oct 2026, 20:46100,961+459
17 Oct 2026, 22:50100,502+781
17 Oct 2026, 00:0699,721+555
15 Oct 2026, 23:2799,166+205
14 Oct 2026, 22:3898,961+626
13 Oct 2026, 13:5998,335+2,707
9 Oct 2026, 18:3895,628+1,850
5 Oct 2026, 09:2093,778+2,704
29 Sept 2026, 04:1791,074+3,728
17 Sept 2026, 23:2187,346+1,133
15 Sept 2026, 21:2186,213+612
14 Sept 2026, 03:3785,601+342
12 Sept 2026, 09:2285,259first reading

Engagement

143 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 189 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.45%
avg views ÷ 103,533 subscribers
Avg views / post
1,500
47 posts measured
Reaction rate
0.05%
reactions ÷ views · ER floor
Posts in window
47
of 143 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. It is computed over the 19 of 47 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 October 2026
Posts held143 (5 August 2026 – 25 October 2026)
Views total70,662
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Oct 2026, 21: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.

What this channel posts

Video runtime
9m 50s
Average length
10s

Measured directly from 58 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

65 reactions across 46 posts, in 7 distinct kinds. The most used accounts for 83.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5483.1%
👍46.15%
👏23.08%
🥰23.08%
⚡11.54%
🎃11.54%
🤣11.54%

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

Measured over the 143 most recent posts we hold, published 5 August 2026 to 25 October 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

25 Oct 2026, 03:05 UTC539 viewsread 25 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

24 Oct 2026, 06:18 UTC≈1,160 viewsread 25 October 2026
Photo

【艺名】: #沈佳宜 【地址】: #南山区 【联系】: @SZSjiayi123 [双向机器人]: @Sjiayibaby_bot 【频道】: https://t.me/SZSjiayi668

23 Oct 2026, 07:05 UTC546 viewsread 23 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

22 Oct 2026, 09:05 UTC189 viewsread 22 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

21 Oct 2026, 11:05 UTC538 viewsread 22 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

21 Oct 2026, 07:34 UTC≈2,560 viewsread 25 October 2026
Photo

深圳94-95-98 #深圳会所 #东莞会所 #海选模式 #全裸 全裸海选正中莞式服务,六十多位位靓女海选一批5选1⃣️ 零零后多,美女最多,质量最高,环境最好 免费停车、免费过夜 根据情况,可选各种姿势,怎么刺激怎么来 公司特色:主题服装、黑丝、学生装、制服诱惑、根据个人爱好挑选 🔥根据您的需求:需要水会,大型会所、特色服务等等安排 注意👉👉可到店任意挑选,不喜欢可以换 🚗深圳“李部长”亲自接待🚗绕开中介 94-95-98项目咨询 私信李部长 李部长电报:@jaio888 双向限制:@jaio888bot 聊天评价: t.me/qq33766 ✅频道 : t.me/bb99971 深圳、东莞珠三角全区一手资源 绕开中介骗子

20 Oct 2026, 16:13 UTC≈2,730 views0 reactionsread 25 October 2026
Photo

【艺名】: #郴郴 【地址】: #宝安区 【联系】: @ijngna77793333 [双向机器人]: @Diejevhdu_bot 【频道】:https://t.me/+jhS08RkAyNhhNDA1

20 Oct 2026, 05:29 UTC≈3,160 views1 reactionsread 25 October 2026
Photo

🎁更多抽奖 https://t.me/xiu8che 🎟️ 抽奖标题:龙岗区宝儿抓龙筋抽奖活动 📪抽奖说明:中奖者机器人会发送中奖信息 中奖者自行联系老师 @baoerzlj520 兑奖有效期七天 🎫 参与条件: 🎫 加入-深圳龙岗宝儿抓龙筋 丝足sm换装 前列腺高潮 🎫 加入-深圳修车911 🎫 加入-深圳911(认证榜) 🎫 加入-深圳911报告📮 🎁 奖品内容: 💰️ 16.88口令红包 × 2 💰️ 50优惠劵(B套餐以上) × 10 💰️ 100优惠卷(B套餐以上) × 5 📅 开奖时间:2026-10-23 18:00自动开奖 👉 参与抽奖链接: https://t.me/tgLotteryuw8bot?start=join-L179247397005

❤1

19 Oct 2026, 15:05 UTC86 viewsread 19 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

18 Oct 2026, 17:05 UTC514 viewsread 19 October 2026

🔎南山区 🔎宝安区 🔎福田区 🔎龙华区 🔎龙岗区 🔎罗湖区 🔎盐田区 🔎坪山区 🔎光明区 🔎大鹏新区 🔎外围上门~各类会所 🫂深圳交流群 📮修车报告 👇下面其它地方资源👇 ✅广州资源 ✅杭州资源 ✅上海资源 ✅长沙资源 ✅南京资源 ✅武汉资源

18 Oct 2026, 08:15 UTC≈3,620 views0 reactionsread 25 October 2026
Video

#深圳会所 #深圳水疗 #95口爆 🥰🥰🥰🥰🥰🥰 ———【 ·深圳全区 T94 -T95 】——— 诸多口味任君选择,嫩妹、御姐、少妇、反差等等 十八般武艺样样精通(部分不知名武艺,需要大哥开发) 让兄弟欢心而来,扶墙而归 无需任何定金,见面付款 👍 靠谱资源,真诚服务 🍈😅😇😢😍😗🙊🥰 #深圳 #深圳会所 #深圳95 深圳水会【口爆场专区】 A套餐1:预约价668-内部价550(全裸口一手一)60分钟 B套餐2:预约价888-内部价750(全裸魔棒口2次)80分钟 C套餐3:预约价 1180-内部价1050(双飞或加钟全裸口出2次) 只接待预约制,没有预约不接待 预约到店消费付款 本客服不收款 🥿🧤🌂🩴🎩🎩👛🩴👠🥾 选人模式:预约到店挑选,预约到店挑选!!! 不发照片,不发照片,不发照片~ ✅ 保护隐私—安全放心 😅😇😢😍😗🙊🥰 🤩在…

18 Oct 2026, 05:08 UTC≈3,520 views1 reactionsread 25 October 2026
Photo

#深圳会所 #深圳按摩SPA #深圳抓龙筋 深圳独家【全新体验】半裸♥️顶级SPA +热石私享沉浸式抓龙筋,“细腻深处直达云顶之上,余音袅袅身心共振享受非凡” 纯口碑,不偷一分钟,时间内无限次释放:胸推,臀疗,龟头责边缘控制,强制高潮,脱敏疗法,三起三落,体验不一样的爽感,头皮酥麻虐恋求饶的感觉,反复高潮,长达5-10分钟。 【私享A课】体验价700/80分钟 【私享B课】体验价900/90分钟 可胸、可手、可足多重释放 位置:#南山 #福田 #宝安 #龙华 #罗湖 ​私聊: @sznsmmspa 频道:@qypdb 🐧QQ:3760728326

❤1

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

Mentions

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

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

“深圳911(认证榜)” (@Yuoyoutan), 103,533 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/Yuoyoutan.

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.