早,有空位

Channel
兔女郎的后宫
@tutunld
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
374subscribers
+353 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004491947789 |
|---|---|
| Type | Channel |
| Username | @tutunld |
| Created | Between 1 June 2026 and 7 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 20 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 20 October 2026 |
| On Telegram | t.me/tutunld |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 96% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Oct 2026, 13:16 | 374 | +9 |
| 13 Oct 2026, 15:56 | 365 | +27 |
| 2 Oct 2026, 19:37 | 338 | +62 |
| 18 Sept 2026, 23:17 | 276 | +73 |
| 10 Sept 2026, 05:22 | 203 | no change |
| 10 Sept 2026, 04:59 | 203 | +182 |
| 7 Sept 2026, 06:17 | 21 | first reading |
Engagement
15 posts held, back to 7 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 10 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 14m 23s
- Average length
- 3m 36s
Measured directly from 4 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.
Reaction mix
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👍 | 1 | 50.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 5 of the 15 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 15 most recent posts we hold, published 7 September 2026 to 10 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
闺蜜来了,今日双飞送小视频
开通晚上外出服务
看着好爽有没有哥哥来这样干我
👍1
早上好,每天有2名惊喜名额,定金预约
晚安,有事请留言,
━━━━━━━━━━━━━━ 🌟 老师评价 🌟 ━━━━━━━━━━━━━━ 🏷️ #汉阳 #高端 #11p #大胸 #空姐 👤 老师:兔女郎 (@xiaoke66678) 🔗 主页:https://t.me/wuhanhua1/21596?single ⭐ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 📝 评价内容: 看到兄弟们的报告,让我好奇心拉满了,果断预约了兔女郎老师,到了老师的房间,一眼就让我沦陷了,笔直的大长腿,性感的身材,情趣衣服一穿,鸡儿立马硬邦邦,表示对美色的尊重,快速的洗澡之后,进入主题,先是传统的姿势,我在上她在下,大长腿抗在肩膀上,一下一下的插入,由浅到深,慢慢的探索骚逼的滋味,一番交战之后,来到站立式后入,那种臀部的撞击声不绝于耳,对小弟弟的刺激非常到位,一直坚挺着,持续抽插,不止腿…
❤1
━━━━━━━━━━━━━━ 🌟 老师评价 🌟 ━━━━━━━━━━━━━━ 🏷️ #汉阳 #高端 #11p #大胸 #空姐 👤 老师:兔女郎 (@xiaoke66678) 🔗 主页:https://t.me/wuhanhua1/21596?single ⭐ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★☆ 4/5 ├ 💗 情绪:★★★★☆ 4/5 ├ 🏡 环境:★★★★☆ 4/5 └ 📷 人照:★★★★★ 5/5 📝 评价内容: 已经有段时间没出击了,看到榜上新老师,还是个空姐,心动!有空了马上约时间,定金留课后出发。有点小紧张,毕竟第一次约空姐老师。课室位置安全隐蔽,进门先看脸,怕有亚洲换脸p图巫术。果然人照差距不大,眼睛马上被老师的大长腿和大D奶吸引,紧张的心情被老师的热情消去一半,交课费后洗澡。老师陪洗,过程中忍不住抱着老师就🐍吻起来,两只手抓着大奶,真爽啊!帮擦后上床,老师👄得很用心,无齿感,👄一会就受不了戴帽…
从光里走来,只为遇见你
━━━━━━━━━━━━━━ 🌟 老师评价 🌟 ━━━━━━━━━━━━━━ 🏷️ #汉阳 #高端 #11p #大胸 #空姐 👤 老师:兔女郎 (@xiaoke66678) 🔗 主页:https://t.me/wuhanhua1/21596?single ⭐ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 📝 评价内容: 今天看到妹妹是才到的新人,直接约了一个,位置是在一个小区,环境不错,打开门,第一眼就看到了妹妹老师,不得不说身材真的不错,那个大长腿和胸看到就忍不住想狠狠的揉捏一番,脑子里已经脑补到接下来的画面了。迅速脱衣一起洗澡,配合的非常好。进到房间我一把抓住老师的大胸,感觉都要抓不过来,妹妹老师的服务也非常好,舌头很灵活,口得我差点缴械,立马戴上套狠狠地输出一番,这次的体验感一样好,实在是让我欲死欲仙。…
痒痒痒,来个活好的哥哥,我想流水
今天还有空位
Showing the 12 most recent of 15 posts we hold for @tutunld. 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.
Forward network
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.
Mentions
Named by 1 registered channel — 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.
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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“兔女郎的后宫” (@tutunld), 374 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/tutunld.
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.