Channel
@beijingliuxing66
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5,435subscribers
-546 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002978265262 |
|---|---|
| Type | Channel |
| Username | @beijingliuxing66 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/beijingliuxing66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 05:56 | 5,435 | -286 |
| 1 Sept 2026, 05:37 | 5,721 | -244 |
| 29 Aug 2026, 00:24 | 5,965 | -16 |
| 28 Aug 2026, 23:00 | 5,981 | first reading |
6 posts held, back to 19 March 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 6 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
8 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 87.5% | |
| 🔥 | 1 | 12.5% |
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 6 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 19 March 2026 to 4 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.
北京商k北京KTV摸摸唱情趣游戏场高端颜值商务场 每天签到100+，亲摸不躲，热情似火 帝王级享受 📱📱📱📱 📱 📱 📱 📱 📱 情绪价值拉满，从倒酒剥瓜子到贴身热舞 沙发秀，高山流水，冰火，九宫格，舌尖缠编全程零冷场，玩到你腿软关键不乱加价，做的口碑服务一流 价格透明 酒水不贵 主要经济实惠玩的开心 北京最好玩的KTV，情趣游戏场，游戏精彩刺激 ------------------------------- 联系客服：@BST899 双向机器人： @BST899_bot 客服电话（同微）：13127723272 频道展示：https://t.me/BST88999 （支持U支付） #北京商K #北京KTV #北京商务KTV #北京游戏场
❤1
🔥北京KTV天花板顶级真空游戏场 同等价位体验TOP1🔥 🌟全城最会玩 尺度与氛围双重保障🌟 🎤每日150+音乐老师驻场 专业气氛组带队狂欢 • 📱兄弟们，别再玩普通的局了来点真刺激的全程真空战袍的商K，尺度直接拉满，爽到停不下来！ • 📱开场即换装：佳丽进包厢立刻换上真空战袍，料子薄到透光，走两步就让人血脉喷张。 • 📱全程可撕：战袍就是为撕而生，手起布落，撕到只剩小内内，玩得够狠才算合格。 • ❌熄灯环节：全场一黑暧昧声此起彼伏，光靠想象就能冲击极限 • 📱📱📱200➕在岗：全成都人最多的真空游戏场、175+模特、学生兼职、制服御姐，每天都有不同面孔给你惊喜 • 💋游戏不断：吹瓶、换妻 互撕、换装、PK，边喝边撕边笑，氛围直接封神！ 飞机联系：@KTV1309 ☎️vx：15011272029 频道链接：https://t.me/az2134555 #北京商K #北京商务KTV #北京真…
🔥1
test
地区：朝阳区大屯路 艺名：程程 水费：1400p/2400pp 电报号：@cc2002yz 特点：#御姐 #服务控 流星大群：https://t.me/beijingliuxing01 男群：@bjlxn 联系管理：@LXQGL
❤1
地区：朝阳区百子湾 艺名：猫猫 水费：1600p/3000pp 电报号：@LXQGL 特点：#嫩妹 #萝莉 流星大群：https://t.me/beijingliuxing01 男群：@bjlxn 联系管理：@LXQGL
❤4
地区：朝阳区三元桥 艺名：七仔 水费：1400p/2600pp 电报号：@qizaizai777 特点：#嫩妹 流星大群：https://t.me/beijingliuxing01 男群：@bjlxn 联系管理：@LXQGL
❤1
Showing the 6 most recent of 6 posts we hold for @beijingliuxing66. 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.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“北京 流星群 榜单省流版” (@beijingliuxing66), 5,435 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/beijingliuxing66.
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.