Channel
@shanghaixxjx
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,047subscribers
+577 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002289432902 |
|---|---|
| Type | Channel |
| Username | @shanghaixxjx |
| 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 | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/shanghaixxjx |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 17 Sept 2026, 17:58 | 2,047 | +55 |
| 13 Sept 2026, 19:40 | 1,992 | +38 |
| 9 Sept 2026, 19:18 | 1,954 | +104 |
| 4 Sept 2026, 08:20 | 1,850 | +38 |
| 31 Aug 2026, 19:54 | 1,812 | +34 |
| 28 Aug 2026, 13:17 | 1,778 | +52 |
| 25 Aug 2026, 13:19 | 1,726 | +59 |
| 22 Aug 2026, 23:53 | 1,667 | +90 |
| 19 Aug 2026, 06:23 | 1,577 | +12 |
| 16 Aug 2026, 16:58 | 1,565 | +53 |
| 13 Aug 2026, 06:57 | 1,512 | +40 |
| 10 Aug 2026, 13:16 | 1,472 | -4 |
| 7 Aug 2026, 03:50 | 1,476 | +6 |
| 6 Aug 2026, 20:18 | 1,470 | first reading |
7 posts held, back to 4 August 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 2 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 7 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.
6 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 👍 | 1 | 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 4 of the 7 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 4 August 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.
🌸 真实好评更新｜上海松江区 木木老师 真实反馈合集 🌸 ☺️☺️☺️☺️☺️☺️☺️☺️☺️☺️☺️ 🍬 姓名：木木 📍 坐标：#松江 #泗泾 🎀 风格：身形匀称腿修长，肌肤细腻洁白 🪷 擅长手法：💆柔式/🐲抓龙筋 💬 客户真实反馈摘录： ·“老师手法很好，人很漂亮，身材很不错 ·“新老师抓龙筋手法一流💯，哪天再来 ·“10分。手法绝了，节奏把控的很好，准确满足了我所有需求 ·“10，给到夯 ·“可以，相当nice ·“必须满分，太牛了 ·“身材不错，9分 ·“10分 ·“已结束，非常满意 ·“10分哦，完全不一样的体验 🚩 综合评分：9.9/10 📊返回总榜 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #上海抓龙筋 #上海spa #松江 #泗泾
📍黄浦·广西南路 👩🏫 珊珊老师 好评 ➕ 9分 ✨珊珊老师，丝足女王👑，喜欢丝足的哥哥别犹豫，放心来！修长美腿，妩媚迷人。🍒 📊返回总榜 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #抓龙筋 #丝足 #黄浦
🌸 — 女神档案 — 🌸 🎆 格格｜杨浦五角场 03年｜163cm｜44kg｜c杯 脚长得真好看，腿白白的，风姿绰约，一举一动都透着一种说不出的魅力，让人印象很深。 🌷 风格特点：风姿摇曳、轻s型 💌 爱好：瑜伽🧘、舞蹈💃、羽毛球🏸 🪷 擅长手法：柔式spa💆，抓龙筋🐲 ⏰ 出勤时间：13:00——5:00 📊返回总榜 ♻️返回杨浦榜单 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #抓龙筋 #柔式 #spa #杨浦
📍嘉定·江桥镇 👩🏫 冰心老师 好评 ➕ 10分 💆 冰心老师口碑爆棚，至今保持满分💯好评，技术精湛，身材优越，前列腺高潮体验感拉满。 📊返回总榜 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #泰式古法抓龙筋 #嘉定 #前列腺高潮
❤2
📍浦东·陆家嘴 👩🏫 娜娜老师 好评 ➕ 这个娜娜老师夯爆了 ✨ 娜娜老师高挑御姐气质🌹 温柔中带着妩媚，好评不断，回头客超多🌸 📊返回总榜 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #上海抓龙筋 #浦东 #御姐
❤1
📍松江·泗泾 👩🏫 木木老师 好评 ➕ 已结束，非常满意 ✨ 木木老师抓龙筋手法娴熟，技术在线，注重体验，认真服务每一位哥哥🎆 📊返回总榜 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #上海抓龙筋 #松江 #柔式
❤1👍1
🌸 — 女神档案 — 🌸 🎆 香香｜徐汇宜山路 96年｜162cm｜49kg｜c杯 属与很有女人味的类型，皮肤白皙细腻，气质温柔大方。很有自己的魅力，属于越接触越容易心动 🌷 风格特点：白皙细腻、丰满妩媚 💌 爱好：健身狂热爱好者🏋️ 🪷 擅长手法：中泰式spa💆，抚触疗愈抓龙筋🐲 ⏰ 出勤时间：11:00——3:00 📊返回总榜 ♻️返回徐汇榜单 预约客服：@xinxinjingxuan 双向机器人：@xinxinjingxuan_bot #抓龙筋 #抚触疗愈 #spa #徐汇
❤1
Showing the 7 most recent of 7 posts we hold for @shanghaixxjx. 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 10 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“上海鑫鑫——抓龙筋精选” (@shanghaixxjx), 2,047 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/shanghaixxjx.
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.