Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳公开资源(认证)

Channel

深圳公开资源(认证)

@shenzhenso

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

21,430subscribers

-2,289 since we began measuring on 4 September 2026

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

Register entry

Telegram ID-1002762210231
TypeChannel
Username@shenzhenso
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/shenzhenso

Topic

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 67% 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

21,43023,71922,574.54 September 2026 — 23,719 subscribers4 September 2026 — 23,719 subscribers5 September 2026 — 23,636 subscribers8 September 2026 — 23,240 subscribers11 September 2026 — 22,815 subscribers13 September 2026 — 22,391 subscribers14 September 2026 — 22,176 subscribers16 September 2026 — 21,786 subscribers18 September 2026 — 21,430 subscribers4 September 202618 September 2026
9 measurements spanning 14 days, net -2,289. 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 21,087–24,062 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 11:5921,430-356
16 Sept 2026, 05:3621,786-390
14 Sept 2026, 13:1522,176-215
13 Sept 2026, 02:5622,391-424
11 Sept 2026, 01:5522,815-425
8 Sept 2026, 02:3923,240-396
5 Sept 2026, 01:3823,636-83
4 Sept 2026, 03:2223,719no change
4 Sept 2026, 02:4723,719first reading

Engagement

5 posts held, back to 8 August 2026the 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 · 30 days
4.56%
avg views ÷ 21,430 subscribers
Avg views / post
977
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 5 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 September 2026
Posts held5 (8 August 20263 September 2026)
Views total2,931
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Sept 2026, 03:22 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
11s
Average length
4s

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

Recent posts

3 Sept 2026, 16:48 UTC15 viewsread 4 September 2026
Photo

【艺名】: #淘气小咪 【地址】: #罗湖区 【联系】: @xiamo3618 【频道】:https://t.me/xiaomi336688 👇下面评论区留言👇

3 Sept 2026, 16:13 UTC16 viewsread 4 September 2026
Photo

【艺名】: #艾雪妖妖 【地址】: #罗湖区 【联系】:@aixue26 【频道】:https://t.me/yaoyaoax20 👇下面评论区留言👇

28 Aug 2026, 08:17 UTC≈2,900 viewsread 4 September 2026
Photo

🥺深圳会所😮😹😎😮🥳😎😮😞 深圳会所/口爆全裸/预约神探/安排稳妥 #深圳会所 #罗湖会所 #南山会所 #宝安会所 #福田会所 #龙岗会所 #龙华会所 #光明会所 📣宝安区 出击客服 ➡️宝安区94-95-96预约 📣罗湖区 出击客服 ➡️罗湖区94-95-96预约 📣福田区 出击客服 ➡️福田区94-95-96预约 📣龙华区 出击客服 ➡️龙华区94-95-96预约 📣龙岗区 出击客服 ➡️龙岗区94-95-96预约 📣南山区 出击客服 ➡️南山区94-95-96预约 📣光明区 出击客服 ➡️光明区94-95-96预约 🐱预约:@Shctcrxbckm 🐱双向机器人:@sz565899bot 📱: 2711683397

15 Aug 2026, 16:40 UTC≈4,000 views0 reactionsread 4 September 2026

✅全国低中高端外围✅ https://t.me/vuvvvvvvvvv

8 Aug 2026, 13:42 UTC≈5,950 views0 reactionsread 4 September 2026
Photo

💞樱花の湯·日式裸身风俗泡泡浴 独家传承日式泡泡浴技艺🪭,纯口啤服务,私密性很好,温柔细腻的手法带来极致放松体验。搭配日式传统按摩🎎,舒缓压力,唤醒身体的每一处感官。👍 🌸浪漫之旅A:798元/70分钟 感官抚触沉浸式精油SPA,全裸身火山热石抓龙筋释放 🌺深情花欲B:998元/100分钟 冰火酥麻脱敏训练,龟责&边缘控制三起三落,胸/手/足多重释放,*前列腺高潮(不同体质情欲探索) 📌店铺地址:深圳龙岗爱琴居,艺术与浪漫交织的秘境,交通便利,私密性极佳。 客服 @yhztppy 双向 @rslsppy520bot 频道 @szlsppy QQ 3833170615

Showing the 5 most recent of 5 posts we hold for @shenzhenso. 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

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

“深圳公开资源(认证)” (@shenzhenso), 21,430 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/shenzhenso.

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.