Channel
@sztiantian0_0
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
403subscribers
-394 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001306920453 |
|---|---|
| Type | Channel |
| Username | @sztiantian0_0 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/sztiantian0_0 |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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, 17:39 | 403 | -96 |
| 6 Sept 2026, 11:57 | 499 | -119 |
| 29 Aug 2026, 07:06 | 618 | -122 |
| 23 Aug 2026, 02:25 | 740 | -22 |
| 15 Aug 2026, 15:05 | 762 | -35 |
| 8 Aug 2026, 01:36 | 797 | no change |
| 7 Aug 2026, 19:31 | 797 | first reading |
17 posts held, back to 25 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
📢 开奖结果公布 🎁 活动： 深圳南山甜甜抓龙筋口令红包¥500元：@taitime 当前参与人数：762人 🏆 中奖名单: 1. ufcb 奖品：口令红包¥500元 2. Matsu 奖品：优惠100元 3. 凉 奖品：优惠100元 4. log 奖品：优惠100元 5. 微醺 奖品：优惠100元 6. 好想谈 奖品：优惠100元 ⏰ 开奖时间：2026年08月05日 16时00分
Signed 深圳福利抽奖机器人
休假模式开启了，这几天太忙了，中奖还没约上哥哥们不要急，休假回来继续可以预约，没有时间限制的哦
Signed 深圳南山甜甜抓龙筋
体验过的都说好，欢迎预约哦，中奖的哥哥们欢迎预约
Signed 深圳南山甜甜抓龙筋
中奖的宝子们，赶快抓紧时间过来体验哦，马上要开启外出学习模式了，晚点来的，只能等外出学习归来再约了。
Signed 深圳南山甜甜抓龙筋
📢 开奖结果公布 🎁 活动：深圳南山甜甜抓龙筋口令红包¥500元：@taitime 当前参与人数：654人 🏆 中奖名单: 1. shevsjsj 奖品：口令红包¥500元 2. S 奖品：优惠100元 3. James 奖品：优惠100元 4. 5769 奖品：优惠100元 5. 晚霞 奖品：优惠100元 6. 0755 奖品：优惠100元 7. 肥 奖品：优惠100元 8. Stimulate 奖品：优惠100元 9. 前海 奖品：优惠100元 10. Potahs 奖品：优惠100元 11. 钟意细腿 奖品：优惠100元 ⏰ 开奖时间：2026年07月31日 12时30分
Signed 深圳福利抽奖机器人
🎁 深圳南山甜甜抓龙筋口令红包¥500元：@taitime 📦 奖品内容: 💰 口令红包¥500元 ×1 💰 优惠100元 ×10 👥 参与条件: 🔗 加入-深圳天猫修车大队 └ 💬 发言数大于 8 条 🔗 加入-深圳天猫修车榜 🔗 加入-天猫报告好评 🔗 加入-深圳 南山 蜜桃私享の半裸 龙筋 SPA ⏰ 开奖方式: 定时开奖: 2026年07月31日 12时30分00秒 ⚠️ 抽奖说明： 中奖者找当前管理员领取口令红包 优惠券找当前老师消费抵扣
Signed 深圳福利抽奖机器人
特别感恩一路相伴的老顾客，从光明搬迁到了南山，距离远了，依然有人特意奔赴，被长久惦记的感觉格外暖心，用心对待每一份信任，不负相遇。
Signed 深圳南山甜甜抓龙筋
忙完收获暖心好评，疲惫瞬间清零，中奖的小哥哥们，抓紧时间来体验哦
Signed 深圳南山甜甜抓龙筋
🎁 深圳南山甜甜抓龙筋口令红包¥500元：@taitime 📦 奖品内容: 💰 口令红包¥500元 ×1 💰 优惠100元 ×5 👥 参与条件: 🔗 加入-🏪深圳同城出击大队🏪 └ 💬 发言数大于 8 条 🔗 加入-🏪深圳同城优选榜🏪 🔗 加入-🏪同城报告发布🏪 🔗 加入-深圳 南山 蜜桃私享の半裸 龙筋 SPA ⏰ 开奖方式: 定时开奖: 2026年08月14日 12时00分00秒 ⚠️ 抽奖说明： 中奖者找当前管理员领取口令红包 优惠券找当前老师消费抵扣
Signed 深圳福利抽奖机器人
温馨小提醒 半个月后开启外出学习模式 有中奖名额的宝子们速速约时间来体验哦 中奖的宝子们没有时间限制噢
Signed 深圳南山甜甜抓龙筋
📢 开奖结果公布 🎁 活动：深圳南山甜甜抓龙筋口令红包¥500元：@taitime 当前参与人数：6人 🏆 中奖名单: 1. Jonewa 奖品：口令红包¥500元 2. 乐呵呵 奖品：优惠100元 3. 空空老弟（心如死灰版） 奖品：优惠100元 4. C 奖品：优惠100元 5. 黑丝终结者 奖品：优惠100元 6. Beaufort 奖品：优惠100元 ⏰ 开奖时间：2026年07月27日 12时01分
Signed 深圳福利抽奖机器人
南山蜜桃半裸泰式抓龙筋 高端情趣半裸➕精油SPA➕酥麻销指尖鼻吸调情➕零距离女友水晶之恋➕延迟边缘控➕前列腺高潮➕规则恋足多重激情释放 胸足手多重无限释放 A套餐 499/60分钟 B套餐 699/80分钟 私聊：@taitime 频道：https://t.me/sztiantian0_0 ➕V：taishiguang68
Signed 深圳南山甜甜抓龙筋
Showing the 12 most recent of 17 posts we hold for @sztiantian0_0. 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 4 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.
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.
“深圳 南山 蜜桃私享の半裸 龙筋 SPA” (@sztiantian0_0), 403 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/sztiantian0_0.
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.