🎉 小叶老师 抽奖福利🧧回馈活动 📝 抽奖说明:中奖主动联系老师 @Joy88888 ,兑奖必须写报告 中奖后三天内有效,预期失效并回收 ✅ 参与条件: 1. 加入 南山简悦 & 私享半裸抓龙筋高端SPA 2. 加入 深圳—美少女鉴赏 3. 加入 深圳—少女鉴赏指南 4. 加入 免费抽奖导航 🎁 奖品内容: • 100米BC可用优惠卷 × 5 • 16.8元口令红包🧧 × 3 ⏰ 开奖时间:手动开奖 👇 点击下方按钮参与抽奖
👍2🔥1🥰1

Channel
@Joy52088
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8,316subscribers
-301 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003345634089 |
|---|---|
| Type | Channel |
| Username | @Joy52088 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/Joy52088 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 13:00 | 8,316 | -153 |
| 1 Sept 2026, 03:39 | 8,469 | +281 |
| 29 Aug 2026, 12:56 | 8,188 | +167 |
| 26 Aug 2026, 19:42 | 8,021 | +13 |
| 24 Aug 2026, 00:53 | 8,008 | +14 |
| 20 Aug 2026, 08:02 | 7,994 | -34 |
| 17 Aug 2026, 14:58 | 8,028 | -107 |
| 14 Aug 2026, 06:19 | 8,135 | -498 |
| 10 Aug 2026, 15:46 | 8,633 | +27 |
| 7 Aug 2026, 22:58 | 8,606 | -11 |
| 7 Aug 2026, 16:01 | 8,617 | first reading |
32 posts held, back to 19 July 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 23 pages 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 | 32 (19 July 2026 – 28 August 2026) |
| Views total | 11,267 |
| Reactions total | 153 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:26 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 5 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.
344 reactions across 26 posts, in 12 distinct kinds. The most used accounts for 26.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 92 | 26.7% | |
| 👍 | 71 | 20.6% | |
| 🔥 | 55 | 16.0% | |
| 🥰 | 49 | 14.2% | |
| ❤🔥 | 25 | 7.27% | |
| 💯 | 18 | 5.23% | |
| 😍 | 13 | 3.78% | |
| 👏 | 10 | 2.91% | |
| 😘 | 6 | 1.74% | |
| 😁 | 2 | 0.581% | |
| 🤓 | 2 | 0.581% | |
| 💋 | 1 | 0.291% |
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 26 of the 32 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 344 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 19 July 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.
🎉 小叶老师 抽奖福利🧧回馈活动 📝 抽奖说明:中奖主动联系老师 @Joy88888 ,兑奖必须写报告 中奖后三天内有效,预期失效并回收 ✅ 参与条件: 1. 加入 南山简悦 & 私享半裸抓龙筋高端SPA 2. 加入 深圳—美少女鉴赏 3. 加入 深圳—少女鉴赏指南 4. 加入 免费抽奖导航 🎁 奖品内容: • 100米BC可用优惠卷 × 5 • 16.8元口令红包🧧 × 3 ⏰ 开奖时间:手动开奖 👇 点击下方按钮参与抽奖
👍2🔥1🥰1
♡ 南汐严选 ♡ ⌚️ 体验时间:2026-08-27 👩🏻🎓 服务老师:小叶 👨🏻💻 留名:匿名 颜值:7.5 环境:8 身材:8 态度:8.5 服务:8 人照:8 综合:8 💌 服务过程 : 推开公寓门 一个很年轻漂亮的小女生 穿着性感小裙子。推油抓筋手法都很专业,一开始第一次来还有点放不开,先让我洗白白。然后温柔帮我擦身体。按摩的手法也是一流,让人欲仙欲死,可惜没见识到丝袜调情环节。最后经历多轮手冲 结束了战斗。最后解读一下。抓龙筋主还是推背按摩和前列腺按摩。不光是92打飞机 🔗 老师资料 :https://t.me/chasesz_lsda/1892
🔥5❤4👍3🥰1
🎉 深圳茶馆-小叶老师半价券 🎁 奖品清单 • a套餐半价券 × 1 🛡️ 参与条件 • 加入 深圳茶馆 • 加入 深圳茶馆-在榜老师 • 加入 南山简悦 & 私享半裸抓龙筋高端SPA • 必须设置用户名 🔮 祝福加持 • 祝福消耗:20圣晶石 • 祝福上限:60次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-09-03 22:57:00 📜 抽奖说明 1:刷屏、灌水、纯表情、复制粘贴、无意义对话、删除消息等,一律视为无效发言,取消中奖资格!请用心交流! 2:中奖后7天内出击,完成必须写报告!没出报告的拉黑抽奖!写报告:@szcg6bot ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。
🔥4🥰4❤2👍2👏1
南山简悦 & 私享半裸抓龙筋高端SPA pinned Deleted message
前列腺高潮哥哥喷的太厉害,换床单都来不及,抓龙筋时床单都湿透的这种感觉你体验过吗?换哪种床单都成了我苦恼的事了😂😂天气一阴晾晒成问题,只能找干洗店清洗烘干了
❤6👍4🔥3👏1🥰1
如果你有一天觉得太累了 请不要责怪自己 你走到这一步 已经很努力了😘❤️ 开课啦,累了记得来找我放松呢
❤🔥4👍3🔥3🥰2😍1
修车不用到处跑 野寻维修没烦恼 人傻钱多 就喜欢撒钱 即日起 找老师上课可获得200加分+100元现金红包😀💰💰💰 更多活动进群了解 有抽奖 有红包⬇️ https://t.me/+4gA1OTuTOf05M2Yx
❤5👍3🔥3
南山简悦 & 私享半裸抓龙筋高端SPA pinned Deleted message
各位哥哥,本人个人工作室。 预约的哥哥不需要任何定金或者课费,都是满意面付❤️❤️❤️ 预约请认准名字:@Joy88888 无大小号之分哦,只有一个号 哥哥,被模仿者骗了后果自负哦😏哥哥注意不要先转钱哈 从今天小叶老师不会提前收任何费用,定金都不收。见面满意再付😄
💯5❤3👍3🥰1😍1
深圳南山疗愈抓🐉,妹妹颜值高,🏠环境优美温馨,专业手法,顶级服务🌹正常上班🎉可上门。预约请私聊
❤🔥2👍1🥰1
❤️love“牛郎织女一年一会”而我们何其幸运,可朝朝暮暮,都能看见彼此 七夕快乐🌹
❤5🔥3👏2🥰2👍1
看到哥哥的好评 心情美美哒 又过了一周,今晚忙不过来。让我的小姐妹帮忙接待了一个上门的哥哥, 上课时间12-2点哦🥰🥰 :@Joy88888
❤6🔥3👍2💯1🥰1😍1
Showing the 12 most recent of 32 posts we hold for @Joy52088. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“南山简悦 & 私享半裸抓龙筋高端SPA” (@Joy52088), 8,316 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/Joy52088.
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.