来自速搜推荐 @SSOU 📢利博代理 利博官网 利博... 📢大漠孤烟⛓️皇汉 📢长大以后 📢Best Interna... 📢露出-户外精选 📢皇冠官方 皇冠开户 欧博... 📢🏅速搜官方🏅|🔥福... 📢🏆速搜官方🆔@SSO... 📢珠海~高端外围兼职精选 📢皇冠体育|欧博包杀|亚星... 📢五件小事 📢环球国际-新盛赌场平台 📢皇冠招商 欧博招商 亚星... 📢经典三级片 📢利博代理 利博百家乐 万... 👉流量互推规则介绍💥 以下是广告推荐 📢 TeleTop 中文索引 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 📢专业Telegram账号交易平台🔥热门社交媒体账号交易 📢XX789🔞成人资源一站式导航 📢 Ton 中文索引 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员,即可在2000+频道进行互推曝光,实现订阅快速增长。

Channel
皇家娱乐/皇冠娱乐/v58国际/新盛国际
@xsyldc11
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
15subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003665136958 |
|---|---|
| Type | Channel |
| Username | @xsyldc11 |
| Description | 新盛博彩部总监:百家乐,龙虎,牛牛等!实体实况连线,信誉平台,大额无忧,视频可以验证现场 官方网址 xs10825.com |
| Created | 26 April 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xsyldc11 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:01 | 15 | no change |
| 6 Aug 2026, 19:47 | 15 | first reading |
Engagement
10 posts held, back to 26 April 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.67%
- avg views ÷ 15 subscribers
- Avg views / post
- 1.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 10 held
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 11 August 2026 |
|---|---|
| Posts held | 10 (26 April 2026 – 11 August 2026) |
| Views total | 2 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 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.
What this channel posts
- Photos
- 7
- Videos
- 5
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 1m 10s
- Average length
- 14s
Measured directly from 5 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
27 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 40.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 11 | 40.7% | |
| ❤ | 9 | 33.3% | |
| 👍 | 7 | 25.9% |
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 6 of the 10 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 27reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 26 April 2026 to 11 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
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
Video, posted without a caption
❤2🔥2👍1
Video, posted without a caption
❤2🔥2👍1
今日大哥战绩狂飙,以下分167个开户咨询本人一直在现场 新盛娱乐网址 xs10825.com 招商专员✈️ @xm88722 开户专员✈️ @xm88722 代理专员✈️@xm88722
❤2👍2🔥1
Video, posted without a caption
🔥2❤1👍1
Video, posted without a caption
🔥2❤1👍1
Video, posted without a caption
🔥2❤1👍1
Channel photo updated
Channel created
Showing the 10 most recent of 10 posts we hold for @xsyldc11. 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.
Citation-graph rank
Citation-graph rank — 775,038 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 29 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@ag_lululu · 121 post笨笨 aIGC ArT
@aIGCArT · 401 post新盛网上合法赌场-金沙PG电子游戏-美高梅娱乐
@ashui3344 · 61 post百度
@baiduyixia00 · 91 post百家乐技术-赛车飞艇澳洲五-138系列-K11酒店系统-idc/boss系统-幸运五星彩-SM并包赢技术-盈利技术-改单技术
@cczb91 · 81 post缅甸赌场-PG游戏-棋牌
@dddz123aa · 101 post电报精准获客|高效涨粉
@hgjjugg56855 · 411 post新加坡滨海湾金沙赌场--华亚国际--银河赌场
@jkl45678 · 101 post恐怖|故事|深夜|一起看
@Kongbugushi · 1781 post利博官网 利博代理 利博百家乐 利博私网
@liboguanwang2 · 8231 post山红
@munaozi · 201 post环球360代理 环球360官网 环球360私网 线上百家乐
@oubo588 · 41 post万利私网🅰️利博私网🅰️皇冠私网🅰️亚星欧博百家乐代理
@oubohuangguandd · 51 post福布斯代理 福布斯官网 福布斯百家乐 福布斯真人
@ouboooa · 41 post体育赛事--世俱杯--欧洲杯
@partygirlsuperb_partygirlsuperb · 101 post接码 实卡接码 国内接码 接码平台
@sadsa6655 · 471 postAG真人视讯-BG百家乐-开云棋牌
@SYZS6 · 91 post《BG真人视讯博彩代理招商》开云棋牌
@tanxing888 · 151 post故事|悬疑|恐怖|未解之谜
@xuanyigushi · 771 post腾龙集团博源国际 · 真人赌场
@xzdsa15 · 61 post皇冠官网|皇冠登1|皇冠登2|皇冠登3
@yaxing534 · 2931 post欧博官网🅱️欧博私网🅱️欧博开户🅱️欧博代理
@yaxing543 · 61 postPA真人 PA会员 PA代理 PA官方
@yaxingbaijiale1688 · 71 post利博百家乐 万利百家乐 UG环球百家乐 福布斯百家乐
@zh_cnjmnkd · 331 post
Names
Channels on the register whose handles appear in this channel's posts.
@TeleTopOrg · 33,0792 posts速搜官方频道-TON中文索引🇨🇳
@cn123 · 8,9681 post🏆速搜官方🆔@SSOU反诈群
@fanzhachannel · 1451 post利博代理 利博官网 利博正网 利博私网
@hdnkfngpo · 3931 post利博代理 利博百家乐 万利代理 利博官网
@liboxd · 31 post🏅速搜官方🏅|🔥福利吃瓜1️⃣群🔥
@mianfeifuli01 · 3251 post大漠孤烟⛓️皇汉
@NBC_Chinese · 241 post皇冠招商 欧博招商 亚星招商 利博招商
@nfjfnjff · 51 post球速体育 赌王之王-PG电子/麻将胡了/AG捕鱼
@pg56984 · 15,7151 post速搜
@ssou · 209,6721 post速搜❤️🔥流量互推/广告交易
@TonAdNews · 8,6201 post五件小事
@wujianxiaoshi · 161 post环球国际-新盛赌场平台
@xm72582 · 91 postXX789🔞成人资源一站式导航
@xx789 · 6451 post皇冠体育|欧博包杀|亚星包杀|万利包杀
@yaxing523 · 3321 post长大以后
@zhangdayihou1 · 191 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@xsyldc11 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 12 August 2026 – 12 August 2026 · confirmed gone 13 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“皇家娱乐/皇冠娱乐/v58国际/新盛国际” (@xsyldc11), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/xsyldc11.
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.