Telegram RegisterThe public register of Telegram

Channel

XXOO通知频道

@XXOOBYBD

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,677subscribers

+43 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003866706939
TypeChannel
Username@XXOOBYBD
DescriptionXO老巢 客服@XXOONBY
CreatedBetween 1 February 2026 and 29 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/XXOOBYBD

Growth

9,6349,6779,655.57 August 2026 — 9,634 subscribers7 August 2026 — 9,634 subscribers8 August 2026 — 9,646 subscribers11 August 2026 — 9,677 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +43. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,628–9,683 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 13:489,677+31
8 Aug 2026, 11:119,646+12
7 Aug 2026, 16:019,634no change
7 Aug 2026, 15:489,634first reading

Engagement

16 posts held, back to 29 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
36.9%
avg views ÷ 9,677 subscribers
Avg views / post
3,570
15 posts measured
Reaction rate
11.2%
reactions ÷ views · ER floor
Posts in window
15
of 16 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held16 (29 June 202612 August 2026)
Views total53,601
Reactions total6,012
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 16:08 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
10
Links
5

Lifetime counters from Telegram’s own channel header, read 12 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.

Reaction mix

6,023 reactions across 16 posts, in 17 distinct kinds. The most used accounts for 20.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,25120.8%
1,20720.0%
👍1,13218.8%
🎉1,08318.0%
😁1,00316.7%
💯801.33%
🥰711.18%
🤩631.05%
❤‍🔥580.963%
😍580.963%
💩50.083%
👎40.066%
🖕30.05%
🤔20.033%
👏10.017%
😨10.017%
🤬10.017%

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 16 of the 16 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,023reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 29 June 2026 to 12 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

12 Aug 2026, 14:08 UTC111 views1,127 reactionsread 12 August 2026
Photo

双机内部月/600(10名)

👍234🎉230🔥226225😁212

7 Aug 2026, 08:23 UTC≈3,320 views1,134 reactionsread 12 August 2026

QQ总群:1102574993😳🎉 QQ单端交流群:1092729468🥳

🔥238235🎉224😁218👍216💩3

3 Aug 2026, 11:14 UTC≈3,750 views1,027 reactionsread 12 August 2026

双机外部已优化, 帮朋友宣传 SKY🌟三角洲SKY解密项目 🌐不是拉闸内存解密,不修改任何数据 📣全人物透视/陀螺仪自喵/物资透视 提卡地址https://911.222bx.cn/item/p7azrw

😁230221🎉215👍181🔥178👎1😨1

3 Aug 2026, 06:06 UTC≈1,730 views1,149 reactionsread 12 August 2026
Photo

时间加范围,爽到起飞,😍😍😍

270🎉227🔥218👍216😁215🖕3

1 Aug 2026, 10:52 UTC≈3,310 views1,495 reactionsread 12 August 2026

建军节牛逼🫡 中国牛逼🫡 中国共产党牛逼🫡

🔥390👍259202🎉187😁128💯80🥰69🤩63

28 Jul 2026, 09:28 UTC≈2,860 views7 reactionsread 12 August 2026

限时福利卡已上架,备用卡网,没上架多少库存啥时候购买不了就是没卡了🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 福利送起来 早上恢复原价

2💩2🥰2👍1

27 Jul 2026, 16:36 UTC≈2,860 views7 reactionsread 12 August 2026

双机已云更新😍 解决部分人网络波动⭐ 必须刷网盘必刷模块⭐

6👍1

26 Jul 2026, 05:33 UTC≈3,200 views7 reactionsread 12 August 2026

🎮卡网已降价为福利价格, 🫢主卡网(不支持微信) 🫢备用卡网(支持微信支付) 📣📣📣📣📣📣📣📣📣📣 😍😍😍😍😍😍😍😍😍😍

4👍3

25 Jul 2026, 10:26 UTC≈3,260 views4 reactionsread 12 August 2026

备用卡网地址(可使用微信支付) 双机必须两个安卓, 端口本身是不用获取root权限的,但是你开东西得有root权限,所以你那个设备开东西那个设备root, ios局内数据跟安卓不互通,ios用户可以下载腾讯先锋当绿玩设备

👍4

24 Jul 2026, 08:30 UTC≈3,600 views6 reactionsread 12 August 2026

依旧稳定兄弟们冲冲冲, 有问题就看反馈群😍

5👍1

22 Jul 2026, 06:54 UTC≈4,230 views10 reactionsread 12 August 2026

xo双机外部已修复部分人网波问题😍 已修复卡加载界面问题😍 已修复遁地问题😍 现在继续连打😍

9👍1

22 Jul 2026, 04:29 UTC≈4,220 views7 reactionsread 12 August 2026

反馈6张以上质量结算图联系客服加时,一张卡只能加时一次

5👍2

Showing the 12 most recent of 16 posts we hold for @XXOOBYBD. 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 — 290,025 of 1,336,469entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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.

“XXOO通知频道” (@XXOOBYBD), 9,677 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/XXOOBYBD.

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.