Channel
@xybangdan
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
661subscribers
+5 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002910004262 |
|---|---|
| Type | Channel |
| Username | @xybangdan |
| 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 | 8 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/xybangdan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 07:35 | 661 | +6 |
| 29 Aug 2026, 22:16 | 655 | -1 |
| 28 Aug 2026, 23:01 | 656 | first reading |
5 posts held, back to 26 June 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 5 (26 June 2026 – 21 August 2026) |
| Views total | 230 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 23:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 💩 | 1 | 33.3% |
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 3 of the 5 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 5 most recent posts we hold, published 26 June 2026 to 21 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.
🌟 顶美榜 MMK女仆私影 👍店铺地址：#天河 #白云 #越秀 #番禺 🔍营业时间： 💸价格项目： 🚫写评价价格: 358/399 SS热恋:摸🦵🏻，无障碍摸🐻，抱抱👩❤️👨，🐍吻，Kiss胸二选一，写报告价: 358/h SSS深恋:🐍吻，Kiss🐻，骑乘式，摇摇🚗，👯♀️换装👯♀️，写报告价: 399/h 最高级套餐: 699/h 可以🐍吻,亲🐻, 摇摇🚗 手打柠檬茶🍋,性价比拉🈵 🈚️95 98 🈲问 💗超多年轻小公主在店，等你来体验恋爱的感觉 💌聊天群组：@TCMMK1 💟出勤频道：https://t.me/lvle88 📊报告频道：https://t.me/aass99998 https://t.me/aaab1119 🛩客服预约：@TXMMK @momo111999 @XUES9 😀双向联系： 🫢微信联系：
💩1
#云朵少女 mmk sss，499/h，蛇吻亲胸摇摇车 ssss，699/h，详细课表请到店咨询 ssssm，799/h，部分妹妹可接受女s或m（捆绑，小鞭子，打屁股，口球，眼罩，乳夾，铃铛，腊烛等） tg客服 @ydsnkf 双向机器人 @ydsnkfbot vx联系：gzmmk520，加好友备注tg 交流群 https://t.me/ydsnmmkchat 每日出勤 https://t.me/ydsnmmk 报告馆 https://t.me/ydsnmmkbg 营业时间：下午2点-凌晨2点 地址：广州市番禺区大石地铁站附近 #广州 #番禺 #大石 #私影 #女仆
❤1
💕广州性价比私影女神恋爱俱乐部💕 👍可以出💦的MMK 🔈门店地址：广州天河岗顶A口 🚗停车方便，楼下就是停车场 😶营业时间：下午12:00-凌晨3:00 😄😄😄所以项目都有😄😄😄 🐍吻➕亲🐻➕摸⬇️➕👋🦶🐻出💦 💸价格： 💵599/60分钟 恋人观影🥰飞行棋🤩（🐍吻➕出💦） 💵799/90分钟 包含599内容➕🐍➕出💦更热烈的投怀送抱 💵799/60分钟 岛国电影般的剧情演绎，多种剧本选择配备有护士房/总裁房/教师房. ❤️1v1贴身陪伴观影🎄 预约客服📱 @ahua889527 双向机器人🤖 @Ahuadxiaohaocun_bot 联系电话📞1812208660 微信📱AAA0311888A 春风mmk报告群：https://t.me/ZLL92933 春风mmk交流群：https://t.me/FC9293 春风mmk频道：https://t.me/ZLL9293
#晴时屿琳琳 私影女仆广州俱乐部 ＃广州 #同和 #京溪 #三元里 全场优惠50，398起 营业时间：下午4:00-凌晨3点 下午三点前提前一天预约 凌晨三点之后提前预约即可 😖包厢～玩游戏～MMK～可接受kiss～玩的开不尬场，深入袭胸，激情舌吻，沉醉骑乘……刺激探索花园，主打服务一级棒👍 清一色十八、九岁学生妹…… 人照一比一，服务升级 同和店地址在白云同和D口附近，欢迎各位帅比，客服微信：CJS88888-8（或NML20230501备注来源） 🤑预约电报：@qingshiyudz 😵预约微信：CJS88888-8 😯营业时间：16:00-02：00 报告馆：https://t.me/GZqingshiyu_mmk2 出勤群: https://t.me/GZqingshiyu_mmk 交流群：https://t.me/qingshuyummk 地址京溪店、三元里店 TG预约总客服：https://t.me/linl…
🌈广州梦屿女仆恋爱馆🌈 🌛营业时间15:00-02:00 🥰每一位妹妹都是零四后，年轻漂亮青春活力. 主打恋爱女友体验，萝莉，御姐，甜美，纯欲风，清冷，温柔系，各色女仆，应有尽有。 ❤️梦屿女仆交流群: @mengyu_mmk_group 🌈今日出勤: @mengyu_today_temp ✏️女友报告: @mengyu_mmk_report_temp 🚩小店地址: 天河客运站世创智谷 咨询预约找我 📣联系客服: @mengyu_service_temp_3 📣客服机器人: @mengyu_1_bot 📣VX客服: MYKF3369 (添加时备注TG)
❤1
Showing the 5 most recent of 5 posts we hold for @xybangdan. 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“xy群狗推榜单” (@xybangdan), 661 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/xybangdan.
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.