Telegram RegisterThe public register of Telegram
Telegram profile photo for 蘇心Sexy Garden

Channel

蘇心Sexy Garden

@suxinsexy

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

188subscribers

+178 since we began measuring on 31 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003853361053
TypeChannel
Username@suxinsexy
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 September 2026
Last confirmed live3 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/suxinsexy

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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

101889931 August 2026 — 10 subscribers1 September 2026 — 52 subscribers10 September 2026 — 180 subscribers19 September 2026 — 161 subscribers30 September 2026 — 161 subscribers3 October 2026 — 188 subscribers31 August 20263 October 2026
6 measurements spanning 33 days, net +178. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 13:57188+27
30 Sept 2026, 20:22161no change
19 Sept 2026, 06:19161-19
10 Sept 2026, 18:39180+128
1 Sept 2026, 10:1352+42
31 Aug 2026, 19:4510first reading

Engagement

17 posts held, back to 2 September 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 · 30 days
84.0%
avg views ÷ 188 subscribers
Avg views / post
158
6 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
7
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. It is computed over the 1 of 6 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 28 September 2026
Posts held17 (2 September 2026 – 28 September 2026)
Views total948
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 20: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.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 3 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 2 reactions 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 2 September 2026 to 28 September 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

28 Sept 2026, 09:14 UTC111 views0 reactionsread 30 September 2026
Photo

🎉 深圳茶馆-蘇心半价券 🎁 奖品清单 • p半价券(必须写报告) × 1 🛡️ 参与条件 • 加入 深圳茶馆 • 加入 蘇心Sexy Garden • 加入 深圳茶馆甄选轮播群 • 加入 深圳茶馆-在榜老师 • 参加抽奖后需在 深圳茶馆 内发言19次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 🔮 祝福加持 • 祝福消耗:20圣晶石 • 祝福上限:60次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-10-02 22:12:00 📜 抽奖说明 1:刷屏、灌水、纯表情、复制粘贴、无意义对话、删除消息等,一律视为无效发言,取消中奖资格!请用心交流! 2:中奖后7天内出击,完成必须写报告!没出报告的拉黑抽奖!写报告:@szcg6bot ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。

28 Sept 2026, 04:38 UTC111 viewsread 30 September 2026

全深圳半价活动最多,群友最活跃的群!!! https://t.me/szcg9

27 Sept 2026, 10:28 UTC131 viewsread 30 September 2026

今晚十点可约,福民路水围二街附近,头课还在哦

8 Sept 2026, 04:30 UTC380 viewsread 30 September 2026
Photo

✨ 命运揭晓时刻 ✨ 福田蘇心优惠卷活动 开奖了 抽奖人数:23,发言达标人数:18,抽奖号数:22 1. hanime 中得:蘇心p半价卷 抽奖说明: 中奖24小时内预约,5天内使用 需写报告,过时自动作废 炸号无效作废,放回群内奖池 中奖优惠卷不得转让 活动最终解释权:深圳欢乐谷 兑奖联系:@suxin9898 🔍 杜绝黑幕,点击查看本次开奖全程验证

5 Sept 2026, 09:24 UTC413 viewsread 30 September 2026

哥哥们,万分抱歉,我可能是阳了也不知道怎么回事,一开口就嗓子疼,浑身无力,跟哥哥们小小请两天假,身体恢复了马上开课,我闺蜜kiki服务也很好的哦:@kikisexy1314 频道 @kikisexygarden2025

4 Sept 2026, 06:30 UTC448 viewsread 30 September 2026
Photo

✨ 命运揭晓时刻 ✨ 深圳蟹堡王活动福田蘇心 开奖了 抽奖人数:94,发言达标人数:35,抽奖号数:48 1. 寺北亭【祝福1次】 中得:p课半价卷 2. dmdnhkgl【祝福1次】 中得:贝壳币200 抽奖说明: 中奖请在24小时内联系老师 使用期限:五天内有效 (使用活动优惠卷需写报告) 所有解释权为蟹堡王所有权 兑奖联系:@suxin9898 🔍 杜绝黑幕,点击查看本次开奖全程验证

4 Sept 2026, 05:00 UTC359 viewsread 30 September 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178823125181 🎰 福田蘇心女仆半价抽奖 ⚠️ 抽奖说明: 1.各位兄弟请遵守群规,严禁非正常断句,严禁刷屏,严禁复制粘贴,严禁无意义对话,严禁撤回消息,有以上行为者取消中奖资格,为创造良好的出击交流平台,请大家用心交流! 2.炸号者、退群者、注销账号者中奖无效! 3.活动最终解释权归本群管理团队所有! 💁 参与情况:32达标 / 36报名 🔋 人品加成:5票 ⚡️× 9 🎅 联系领奖:@suxin9898 1. DianXin 奖品:单P半价券 祝大家心想事成好运连连!

4 Sept 2026, 03:51 UTC297 viewsread 30 September 2026

哥哥们,万分抱歉,我可能是阳了也不知道怎么回事,一开口就嗓子疼,浑身无力,跟哥哥们小小请两天假,身体恢复了马上开课,我闺蜜kiki服务也很好的哦:@kikisexy1314 频道 @kikisexygarden2026

Showing the 12 most recent of 17 posts we hold for @suxinsexy. 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 9 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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“蘇心Sexy Garden” (@suxinsexy), 188 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/suxinsexy.

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.