Channel
@xiaotiantian1456
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,829subscribers
-97 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002319064529 |
|---|---|
| Type | Channel |
| Username | @xiaotiantian1456 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/xiaotiantian1456 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 15 Sept 2026, 22:01 | 3,829 | +94 |
| 12 Sept 2026, 13:59 | 3,735 | +124 |
| 8 Sept 2026, 04:41 | 3,611 | -14 |
| 2 Sept 2026, 17:27 | 3,625 | -2 |
| 30 Aug 2026, 16:34 | 3,627 | -5 |
| 27 Aug 2026, 19:04 | 3,632 | -3 |
| 24 Aug 2026, 13:03 | 3,635 | -13 |
| 20 Aug 2026, 18:18 | 3,648 | -16 |
| 18 Aug 2026, 00:52 | 3,664 | -289 |
| 14 Aug 2026, 22:26 | 3,953 | +3 |
| 11 Aug 2026, 15:04 | 3,950 | +10 |
| 8 Aug 2026, 08:46 | 3,940 | +14 |
| 8 Aug 2026, 02:31 | 3,926 | first reading |
20 posts held, back to 24 May 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
17 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 100.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 9 of the 20 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 May 2026 to 7 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.
#杭州肯德基 https://t.me/kdjqjt #好评 91 【出击时间】：8.6 【出击老师】：小甜甜 【联系方式】：@tian6616888 【出击留名】：再见 【开课位置】：拱墅万达附近 【修车水费】：工兵P 【人照评分满分10】：9（人照相似度/妆容） 【颜值评分满分20】：18（耐看/高颜值/一般） 【身材评分满分10】：10（皮肤白黄/身材非常不错B+/罩杯B+） 【吊感评分满分20】：18（户型不错/紧度OK/水量还行/包裹感不错） 【服务评分满分10】：10（流程化/女友感比较好，常规服务） 【态度评分满分20】：19（主动询问/自觉服务） 【环境评分满分10】：7（公寓） 【综合评分满分100】：91（以上相加） 情绪价值描述: 挺不错的，女友感觉到 【过程描述】：有的打 舌吻 no 有kiss 口活 ok 69舔穴 ok 毒龙 no 【过程描述】：过程小黄文（200字以上） …
❤1
小甜甜（净身高175）开课中 pinned a photo
🎰 她一直都是小甜甜 @tian6616888 ！ 📮 抽奖条件: 🎫 加入-杭州日报 🎫 加入-杭州日报榜单 🎫 加入-杭州日报新人实习频道 🎫 加入-小甜甜（净身高175）开课中 🎟️ 要求活动期间群内发言数 10 🍀 每5分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: 半价券-限P × 1 💡 活动说明: 本次活动由小甜甜 @tian6616888 独家赞助！ 本次活动最终解释权归杭州日报所有！ 📅 开奖日期:(UTC+8) 2026年08月10日 12时46分00秒
号被限制了换号了，联系我另一个 @tian6616888
秋天的第一杯奶茶没有，秋天的第一炮可以有哦🥰🥰
开课中
❤2
杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】：‼️下面只留一个 #超级好评 ✅ #好评 #中好评 #中评 #差评 【妹子花名】：#小甜甜 【联系方式】：@tian66168 【妹子年龄】：22 【验证留名】：阿斯巴足球 【验证时间】：8月5日 【大概位置】：拱墅 【修车水费】：工兵 【高端服务】：有的打✅ ① 舌吻 浅吻 ② 69舔逼 ✓ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】：人照相似8成 【身材皮肤】：身高175左右大腿长，无纹身，皮肤白 【凶器罩杯】：b罩杯 【湿度紧度】：水量多，紧度正常 【环境细节】：公寓 【个人卫生】：事前事后有清洗 【时间管理】：开课准时，排课宽松，课时做完 【服务总结】：服务到位，无少做，过程无机车 【流程小文】： 前一天约完工兵，准备出击，结果老师号炸了，联系不上。等到第二天，终于联系上了，果断出击。课室在一个公…
❤1
我在杭州御女阁免费上榜啦，群内氛围轻松，不强制做活动，永久上榜！ 👑👑认准Telegram官方认证防伪标志 👑 超多好看的小姐姐都在这里上榜！💖💖💖 https://t.me/hangzhou_777
账号有问题了，双向给我发消息我回不了，只能麻烦你们自己私信我了
今天因为号的问题，很多信息都回不了 各位工兵宝宝们不好意思，明天通通回复
起来晚了，现在开课中
Channel name was changed to «小甜甜（净身高175）开课中»
Showing the 12 most recent of 20 posts we hold for @xiaotiantian1456. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“小甜甜（净身高175）开课中” (@xiaotiantian1456), 3,829 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/xiaotiantian1456.
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.