我的机器桩坏了,还没有修好,可以先找她,闺蜜来深圳开课了,朋友圈 https://t.me/ddfacaiy 双响 @kisskeds6bot 预约 @ysisi66

Channel
深圳瑶瑶个人频道蛇吻🔥
@xiaoqingqqq
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,569subscribers
+1,403 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002277979525 |
|---|---|
| Type | Channel |
| Username | @xiaoqingqqq |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/xiaoqingqqq |
Topic
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 16 Sept 2026, 02:20 | 3,569 | +70 |
| 12 Sept 2026, 03:59 | 3,499 | -170 |
| 8 Sept 2026, 05:01 | 3,669 | +924 |
| 2 Sept 2026, 20:26 | 2,745 | +761 |
| 31 Aug 2026, 04:06 | 1,984 | +43 |
| 28 Aug 2026, 11:06 | 1,941 | -7 |
| 25 Aug 2026, 14:48 | 1,948 | -31 |
| 22 Aug 2026, 11:43 | 1,979 | -124 |
| 18 Aug 2026, 23:18 | 2,103 | -37 |
| 16 Aug 2026, 08:05 | 2,140 | -9 |
| 13 Aug 2026, 02:14 | 2,149 | +10 |
| 10 Aug 2026, 02:12 | 2,139 | -19 |
| 7 Aug 2026, 11:57 | 2,158 | -8 |
| 6 Aug 2026, 20:01 | 2,166 | no change |
| 6 Aug 2026, 19:52 | 2,166 | first reading |
Engagement
20 posts held, back to 28 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 3 pages 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.
What this channel posts
- Video runtime
- 24s
- Average length
- 6s
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
3 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 4 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 3 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 28 July 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.
Recent posts
小姐姐:瑶瑶 地区:宝安 联系方式:@hhddk6 评分: A- 颜值: 8.5 人照: 8.5 身材:8 情绪价值: 7.5 服务: 7.5 课室环境:7 特点 : c胸 逼紧(毛多) 听话(适合操盘) 慢热型 小i 体验细节:到地方遥控上门,地方比较偏僻,但上去比较好找是公寓。进门简单唠嗑,老师传一身女仆装,粗略一扫身材匀称,真人偏黄皮,没什么赘肉,奶子隆起大概有C或B+,身材蛮好,随意唠嗑一会刚起床没多久,话不是很多感觉比较I人,才刚开课三天,时间差不多交学费一起洗澡,全程陪浴给洗的很干净,老弟被搓的有点微微梆硬,有点迫不及待完躺床上,宝宝也很主动贴上来,基本是嫩妹三件套,舌吻调情,舔咪咪然后奶子主动凑上来给吃,随意动一动妹妹很敏感低吟起来,然后游龙至根部开始嗦我龙根,但妹妹刚下海,口起来感觉差点意思,包裹感不强。那就让妹妹…
宝安瑶瑶🔥 个人频道💋 pinned Deleted message
🎉 宝安瑶瑶抽奖活动 📝 抽奖说明:8月3日前兑奖,逾期无效 ✅ 参与条件: 1. 加入 春朝频道 2. 加入 深港汇精选分享 3. 加入 朝花夕拾频道 4. 加入 朝花夕拾 5. 加入 宝安瑶瑶🔥 个人频道💋 6. 加入 免费抽奖导航 7. 在 朝花夕拾 发言满 5 条 🎁 奖品内容: • 300元现金,中奖直接联系瑶瑶 @hhddk6 × 1 • 200元现金,中奖直接联系瑶瑶 @hhddk6 × 1 ⏰ 开奖时间:2026-08-01 19:00 👇 点击下方按钮参与抽奖
宝宝们我今天被桩基桩到了,要休息几天,老公们记得等我哦
❤2
老公们开课了 双响 @gfv6fdvbot 预约 @hhddk6
老公们来个尾课下班哦 双响 @gfv6fdvbot 预约 @hhddk6
深圳800神教(工兵群) https://t.me/+mQSGRU3HNNw0MDU1 验证通过的老师请将群组转发到自己频道
老公们来个尾课下班哦 双响 @gfv6fdvbot 预约 @hhddk6
老公们来个尾课下班哦 双响 @gfv6fdvbot 预约 @hhddk6
现在🈳哦,宝宝们
现在🈳哦,宝宝们
Showing the 12 most recent of 20 posts we hold for @xiaoqingqqq. 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 2 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳瑶瑶个人频道蛇吻🔥” (@xiaoqingqqq), 3,569 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/xiaoqingqqq.
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.