Telegram RegisterThe public register of Telegram
Telegram profile photo for 护航仔-官方频道

Channel

护航仔-官方频道

@xuehuabox

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

28,633subscribers

+2,046 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001514559397
TypeChannel
Username@xuehuabox
Description交流群:https://t.me/hhzjlq
Created22 June 2023 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/xuehuabox

Topic

Gaming — 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 10 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

26,52428,63327,578.510 August 2026 — 26,587 subscribers10 August 2026 — 26,696 subscribers11 August 2026 — 26,772 subscribers12 August 2026 — 26,809 subscribers14 August 2026 — 26,819 subscribers15 August 2026 — 26,832 subscribers16 August 2026 — 26,849 subscribers17 August 2026 — 26,836 subscribers18 August 2026 — 26,826 subscribers19 August 2026 — 26,794 subscribers20 August 2026 — 26,633 subscribers22 August 2026 — 26,524 subscribers23 August 2026 — 26,703 subscribers25 August 2026 — 27,351 subscribers26 August 2026 — 27,783 subscribers27 August 2026 — 27,990 subscribers28 August 2026 — 27,979 subscribers29 August 2026 — 27,969 subscribers30 August 2026 — 28,051 subscribers31 August 2026 — 28,102 subscribers1 September 2026 — 28,123 subscribers2 September 2026 — 28,137 subscribers3 September 2026 — 28,146 subscribers4 September 2026 — 28,215 subscribers7 September 2026 — 28,273 subscribers10 September 2026 — 28,330 subscribers12 September 2026 — 28,516 subscribers14 September 2026 — 28,563 subscribers16 September 2026 — 28,603 subscribers18 September 2026 — 28,633 subscribers10 August 202618 September 2026
30 measurements spanning 39 days, net +2,046. 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 26,208–28,949 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
18 Sept 2026, 15:1828,633+30
16 Sept 2026, 03:5828,603+40
14 Sept 2026, 07:5828,563+47
12 Sept 2026, 15:1528,516+186
10 Sept 2026, 15:1628,330+57
7 Sept 2026, 11:2028,273+58
4 Sept 2026, 18:5828,215+69
3 Sept 2026, 06:1828,146+9
2 Sept 2026, 02:3428,137+14
1 Sept 2026, 03:0428,123+21
31 Aug 2026, 01:2428,102+51
30 Aug 2026, 02:4628,051+82
29 Aug 2026, 02:5627,969-10
28 Aug 2026, 04:1327,979-11
27 Aug 2026, 01:3427,990+207
26 Aug 2026, 03:3627,783+432
25 Aug 2026, 00:0727,351+648
23 Aug 2026, 12:5926,703+179
22 Aug 2026, 02:2626,524-109
20 Aug 2026, 19:5426,633first reading

Engagement

387 posts held, back to 22 June 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.55%
avg views ÷ 28,633 subscribers
Avg views / post
444
226 posts measured
Reaction rate
1.68%
reactions ÷ views · ER floor
Posts in window
226
of 387 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 24 September 2026
Posts held387 (22 June 2023 – 24 September 2026)
Views total100,350
Reactions total1,685
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 15:56 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
≈2,140
Videos
≈23
Links
≈128

Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
13m 05s
Average length
1m 52s

Measured directly from 7 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

2,695 reactions across 344 posts, in 4 distinct kinds. The most used accounts for 97.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2,62897.5%
❤371.37%
🔥260.965%
💩40.148%

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

Measured over the 387 most recent posts we hold, published 22 June 2023 to 24 September 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

24 Sept 2026, 14:48 UTC392 views21 reactionsread 24 September 2026
Photo

三角洲护航仔解密 解密方式:模拟执行 也就是大家说的算法解密 由于解密技术的原因,在抓包方式上出现了问题,导致了小部分玩家使用后出现了十年封禁的情况,冻结一天,再追十年封禁,今晚我们会进行大更新,彻底解决两个问题, 1:杜绝十年问题 2:解决设备兼容性,使解密不依赖设备 对于一个项目而言,出现封禁十年是非常致命的,口碑会直接崩塌,我们不回避问题,确实是做的还不够好,目前已经解决了这个技术难点,今晚不定时会发布护航仔全新公益解密版本。对于封号的玩家后续我们也会发布通知给与补偿,感谢大家能使用护航仔,谢谢你们,护航仔一定不会让大家失望。

👍21

24 Sept 2026, 14:21 UTC460 views21 reactionsread 24 September 2026

今晚会更新。丢了的脸面,我会自己拿回来。

👍21

24 Sept 2026, 11:39 UTC993 views11 reactionsread 24 September 2026

大家注意: 新版本新增了 模式一 跟模式二,模式一只支持高内核版本,低内核版本还未兼容适配,模式一开启无效就用模式二。

👍11

24 Sept 2026, 09:35 UTC505 views12 reactionsread 24 September 2026
Photo

三角洲国服算法解密—护航仔 更新时间:9/24日 公益通用卡密: GYKD9348A110CF6DD2B165B56773C6BD ━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━ ✅下载 ✅网盘下载 ━━━━━━━━━━━━━━━━ 🟢使用教程 🟢护航仔详细介绍 ━━━━━━━━━━━━━━━━ 🟢疑难杂症解决 🟢反馈图加时 ━━━━━━━━━━━━━━ 😃客服:@hhz1666 😃双向bot:@hhzsxjqrbot 🥇技术客服1:@laifeng13 🥈技术客服2:@CGDYXiong 🥉技术客服3:@zhehan6696 使用中遇到任何问题请联系技术客服解决 技术客服只是老玩家请不要有任何金钱交易 交流群:https://t.me/hhzjlq

👍12

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

Posts edited after publishing

@xuehuabox edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
20 August 2026

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

23 Aug 2026, 11:25 UTCAnonymous Poll650 voters

三角洲公益算法解密—护航仔 是否好用?

  1. 非常好用—继续公益继续支持69%
  2. 垃圾—狗都不用31%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

17 Aug 2026, 08:34 UTCAnonymous Poll1,820 voters approx.

想玩什么游戏?

  1. 三角洲28%
  2. 暗区7%
  3. 和平12%
  4. 王者9%
  5. 失控进化5%
  6. 无畏契约6%
  7. PUBGM4%
  8. CFM29%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 387 most recent posts we hold, published 22 June 2023 to 24 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“护航仔-官方频道” (@xuehuabox), 28,633 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xuehuabox.

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.