Channel
@jingxueaixiaofei
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5,326subscribers
-925 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003577263159 |
|---|---|
| Type | Channel |
| Username | @jingxueaixiaofei |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/jingxueaixiaofei |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 19 Sept 2026, 14:58 | 5,326 | -157 |
| 14 Sept 2026, 21:01 | 5,483 | -122 |
| 11 Sept 2026, 09:38 | 5,605 | -277 |
| 6 Sept 2026, 11:55 | 5,882 | -111 |
| 2 Sept 2026, 13:23 | 5,993 | -89 |
| 30 Aug 2026, 15:16 | 6,082 | +449 |
| 27 Aug 2026, 20:34 | 5,633 | -38 |
| 25 Aug 2026, 03:42 | 5,671 | -61 |
| 22 Aug 2026, 06:47 | 5,732 | -178 |
| 19 Aug 2026, 07:13 | 5,910 | -104 |
| 16 Aug 2026, 17:16 | 6,014 | -87 |
| 13 Aug 2026, 05:23 | 6,101 | -71 |
| 10 Aug 2026, 13:12 | 6,172 | -73 |
| 7 Aug 2026, 21:07 | 6,245 | -6 |
| 7 Aug 2026, 18:16 | 6,251 | first reading |
14 posts held, back to 17 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 8 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 14 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 2 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.
12 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 66.7% | |
| 🍓 | 2 | 16.7% | |
| 🤡 | 2 | 16.7% |
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 8 of the 14 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 17 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.
深圳会所按摩体验宽敞雅致，环境静谧放松。专业技师技艺精湛，手法细腻，为身体带来极致放松。设施设备先进，按摩区域私密舒适，氛围温馨怡人。体验过程中，感受到身心的松弛与愉悦，缓解疲劳，提升精神状态。整体服务周到细致，是放松身心的理想选择，让人忘却都市喧嚣，享受片刻宁静与奢华 在线客服：@kef827 双向客服：@xuesiym_bot 95油客服 @luchangxiao_bot #深圳会所 #南山会所 #福田会所 #宝安会所 #罗湖会所
福田新洲夏日酒店好评🛡 感谢老板的支持与信任 推荐安排靠谱，少走弯路不踩雷，体验请提前联系预约😊😊 在线客服➡️➡️ @kef827 双向客服➡️ @luchangxiao_bot
龙华清湖今日新人入场 可有需要体验的联系下方客服 在线客服➡️@kef827
🕺🕺罗湖区95油好评 推荐安排靠谱，少走弯路不踩雷，体验请提前联系预约😊😊 在线客服➡️➡️ @kef827 双向客服➡️ @luchangxiao_bot
周六到~~快乐也到 老师任你选!丝足?臀推?胸推?口爆?（都可选） 技师专业，价格实在，绝不踩坑! 每日坚持在线，为您主动传递我们的优势信息， 您只需专注于选择，我全力确保您的满意体验。 客服预约✈️ @kef827 双向请联系 @xuesiym_bot 罗湖95客服➡️ @luchangxiao_bot #深圳会所 #深圳94 #罗湖94 #宝安94 #福田94 #南山94 #深圳95
罗湖95海选会所 基础保健，摸鲍、舔鲍、舔棍、波推，真胸调情，丝足诱惑，毛扫毛推，美女划船，指尖调情，360 度胸推臀推，刮痧过水，舌尖漫游，69 式，真舌毒龙，倒挂金钩，穿孔桥，温水回笼、海底捞🈷️、高山流水💦最后🐍嘴里 服务时间60分钟价格639 现场选妃：（海选） 😀😀😀😀 （仅限周一到周四海选） 任挑任选，不满意下一批，换到满意为止，或者喜欢什么类型告知 帮君挑选喜欢类型😀😀😀😀 客服预约✈️ @kef827 双向请联系 @xuesiym_bot 📴🉐㊗️📳㊙️㊙️🆘🆑 ‼️无定金、无任何套路、没有预约店里不接待！！避免跑空、过来请提前预约！‼️不合适可直接离店 #罗湖会所
❤2🍓2
龙华区 清湖附近红牌04年小妹88号 早班12点到晚上8点 需要白天出来玩的可以试试 客服预约🥵@kef827
龙华民治好评 银沙月色制服换装 感谢信任与支持😍 点击预约➡️ @kef827
福田区➡️（丽都）华强北 店内技师照片点击观看 9️⃣4️⃣预约价🥵😀😀😀 项目介绍：丝足 足交👋🦶🐻 😀😀😀😀😀😀😀😀😀 十指弹琴😼比翼双飞😼柔情似水 高山流水😼丝足诱惑😼贴身抚摸 舔蛋吸蛋😼⑥⑨互舔😼猴子偷桃 粉鲍可摸😼奸式胸推😼鼻息环绕 波推全身😼舌尖环游😼可摸可亲 果冻毒龙💥舌尖三角区💥 最后出2次 （默认一次需2提前交代） 😀😀😀😀😀😀😀😀😀😀 🔎🔎🔎🔎 🔞未成年不接待 ✈️电报 🥵 @kef827 🤗点击预约 📱微信 🥵 Ll07183x 点击复制粘贴 🤖双向 🥵@xuesiym_bot
❤1
别再忍了！今晚，让身体做主。在这里，放纵不是错，而是一种刚需。 😁特别的爱给特别的你 😁特别的妹妹安排给你 客服预约🥵 @kef827 🤖双向 🥵@xuesiym_bot #深圳会所 #深圳94 #罗湖94 #宝安94 #福田94 #南山94 #深圳95
罗湖区➡️ （嘉晨公馆）文锦 店内环境点击观看 店内部分老师照片点击观看 9️⃣4️⃣预约价😀😀😀（全脱服务） 项目介绍：丝足 足交👋🦶🐻 😀😀😀😀😀😀😀😀😀 十指弹琴😼比翼双飞😼柔情似水 高山流水😼丝足诱惑😼贴身抚摸 舔蛋吸蛋😼⑥⑨互舔😼猴子偷桃 粉鲍可摸😼奸式胸推😼鼻息环绕 波推全身😼舌尖环游😼可摸可亲 果冻毒龙💥舌尖三角区💥 （默认一次出水需2提前交代） 😀😀😀😀😀😀😀😀😀😀 免费留宿🤩免费停车🤩免费小吃🤩免费饮品🤩免费自助餐，三人同行免费k歌，24小时营业！ 🌟送按头、按肩、按脚、修脚、按手、修手（选二项） 🔎🔎🔎🔎 🔞未成年不接待 ✈️电报 🥵 @kef827 🤗点击预约 📱微信 🥵 Ll07183x 点击复制 🤖双向 🥵@xuesiym_bot🤗点击预约
罗湖区新到00后四姐妹 想体验的，私信联系，随时安排 😀😀😀 客服预约🥵 @kef827 🤖双向机器人🥵@xuesiym_bot #罗湖94
🤡2❤1
Showing the 12 most recent of 14 posts we hold for @jingxueaixiaofei. 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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳会所水会出击资源区” (@jingxueaixiaofei), 5,326 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/jingxueaixiaofei.
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.