Telegram RegisterThe public register of Telegram
Telegram profile photo for 玄武云科技『主频道』

Channel

玄武云科技『主频道』

@BY520XW

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

5,504subscribers

-1,171 since we began measuring on 21 August 2026

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

Register entry

Telegram ID-1002916705925
TypeChannel
Username@BY520XW
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live25 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/BY520XW

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

5,5046,6806,09221 August 2026 — 6,675 subscribers23 August 2026 — 6,680 subscribers26 August 2026 — 6,633 subscribers29 August 2026 — 6,508 subscribers1 September 2026 — 6,318 subscribers6 September 2026 — 6,155 subscribers11 September 2026 — 5,981 subscribers15 September 2026 — 5,748 subscribers25 September 2026 — 5,504 subscribers21 August 202625 September 2026
9 measurements spanning 35 days, net -1,171. 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 5,328–6,856 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 18:175,504-244
15 Sept 2026, 09:005,748-233
11 Sept 2026, 09:015,981-174
6 Sept 2026, 12:006,155-163
1 Sept 2026, 23:486,318-190
29 Aug 2026, 15:496,508-125
26 Aug 2026, 10:026,633-47
23 Aug 2026, 09:336,680+5
21 Aug 2026, 22:016,675first reading

Engagement

20 posts held, back to 7 January 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 20 posts for this entry, the most recent from 18 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

42,142 reactions across 20 posts, in 58 distinct kinds. The most used accounts for 19.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8,09919.2%
🔥7,93518.8%
🥰7,89118.7%
🎉7,87818.7%
👏7,75418.4%
custom 50711138339473339671,2582.99%
👾3010.714%
😁1790.425%
👻1480.351%
👍1340.318%
🤔490.116%
😈370.088%
👀350.083%
🫡350.083%
🤗240.057%
🆒230.055%
🤓220.052%
😘200.047%
🦄190.045%
💋150.036%
38 further kinds2860.679%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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

Measured over the 20 most recent posts we hold, published 7 January 2026 to 18 June 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

18 Jun 2026, 17:12 UTC≈3,770 views107 reactionsread 21 August 2026
File

「海海海」- 小雪 专辑: 海海海 今天端午节哦 祝大家端午快乐 同时也祝我的小宝端午安康呀 愿大家付出的每一份真心都不被辜负 ================================================== 点击使用玄武神秘速刷机器人 点击使用玄武投稿机器人 点击一键加入玄武神秘频道

👍47🔥23🥰8👾6❤4👏4👻4🤡3

10 Jun 2026, 15:38 UTC≈2,640 views80 reactionsread 21 August 2026
Photo

天气预报说今晚有雨 我听成了今晚有你 ================================================== 点击使用玄武神秘速刷机器人 点击使用玄武投稿机器人 点击一键加入玄武神秘频道

❤43🎉8👻5🆒5💘4👍3👾3😁3

12 May 2026, 14:26 UTC≈4,100 views134 reactionsread 21 August 2026

今天是汶川特大地震18周年纪念日 也是全国防灾减灾日 2008年5月12日,汶川发生里氏8.0级特大地震,这是新中国成立以来破坏性最强、波及范围最广、救灾难度最大的一次地质灾害,给人民群众生命财产造成了重大损失,给全国人民留下了刻骨铭心的伤痛记忆。为铭记灾难、警示未来,自2009年起,每年5月12日被设立为全国防灾减灾日,旨在增强全民防灾减灾意识,提升全社会灾害风险防范能力,筑牢防灾减灾的人民防线。 铭记历史 缅怀逝者 山河无恙 人间皆安 愿岁月静好 国泰民安

👾77🫡14👏7❤5❤‍🔥5🥰5🙏5👍4

23 Apr 2026, 11:41 UTC≈57,500 views39,077 reactionsread 21 August 2026
Photo

人生不会重来,属于你的花也不会再开 点击使用玄武神秘速刷机器人 点击使用玄武投稿机器人 点击一键加入玄武神秘频道

🎉7,870🔥7,820🥰7,810❤7,790👏7,680👾60👻15😘15

15 Mar 2026, 05:52 UTC≈58,900 views211 reactionsread 21 August 2026
Photo

🔴👍👍👍 人生就像一杯茶 不会苦一辈子 但总会苦一阵子. ================================================== ✅玄武速刷主项目频道✅ ⚠️认准速刷专区:⚠️ 👋 @XWYYDSA 👋 📣官方速刷机器人: 📣 🎉 @BY520XWNB_BOT 🎉 ==================================================

custom 5071113833947333967100🔥25👍15❤13👏10👾10😁9☃8

2 Mar 2026, 14:54 UTC≈5,100 views246 reactionsread 21 August 2026

一言看破度轮回 两情相遇 千世姻缘来

custom 5071113833947333967105👍28❤22🔥17👏15🤓12🥰12😁10

28 Feb 2026, 11:41 UTC≈5,280 views182 reactionsread 21 August 2026
Photo

两袖清风怎敢误佳人 #玄武云科技

custom 5071113833947333967105🥰13🔥10💔8😨8🤡7🤨7😭7

25 Feb 2026, 18:29 UTC≈5,470 views183 reactionsread 21 August 2026

✅玄武售后客服✅ ✅新客服地址✅: ❤️ @BY520XWA❤️ 🌟原客服地址🔗: 😏@BYXW888 😏 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 #玄武云科技

custom 5071113833947333967106❤19🤔11👏7👾7👻6🫡6😁6

18 Feb 2026, 06:21 UTC≈5,360 views227 reactionsread 21 August 2026

♥️玄武导航页✅ ✔️速刷机器人😃 速刷机器人: @BY520XWNB_BOT 对接api版 @BYXWYBOT 😂投稿机器人😃 @BYXWTGABOT 📱各个频道地址🕠🕠 官方主频道:@BY520XW 中转教学:@BYXWA 速刷专区:@XWYYDSA 投稿分享:@BYXWFKW 云商城:@BYXWC 交流群组:@BYXWYYDS

custom 5071113833947333967114❤39🥰10👀9💘9😁9👍8👻8

12 Feb 2026, 13:32 UTC≈5,090 views173 reactionsread 21 August 2026
Photo

📱诋毁,本身就是一种仰望✔️

custom 5071113833947333967105👍12🔥11❤7👀6🥰6🫡6🆒6

6 Feb 2026, 10:51 UTC≈4,960 views182 reactionsread 21 August 2026
Photo

伦敦的雨下得很克制,就像我藏了又藏的心事。 The rain in London falls in a restrained way, just like the secrets I keep hiding. 🌹🌹🌹🌹🌹🌹🌹🌹🌹🌹 官方主频道: @BY520XW 😀😀😀😀😀😀😀😀😀😀 —— 感谢你对玄武云科技的支持

custom 5071113833947333967105❤14🥰9👍8🌚7👏7🔥7🤓7

31 Jan 2026, 09:20 UTC≈4,570 views150 reactionsread 21 August 2026

路由器导不出你的心 加密算法算不出我们之间的距离

👾103🤗9🎃5🤝5❤4🍓4🐳4👏4

Showing the 12 most recent of 20 posts we hold for @BY520XW. 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.

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 3 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.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“玄武云科技『主频道』” (@BY520XW), 5,504 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/BY520XW.

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.