Telegram RegisterThe public register of Telegram
Telegram profile photo for Hoyoverse Network

Channel

Hoyoverse Network

@hoyoversenetwork

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

658subscribers

+10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002097354605
TypeChannel
Username@hoyoversenetwork
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/hoyoversenetwork

Growth

6486586537 August 2026 — 648 subscribers8 August 2026 — 648 subscribers16 August 2026 — 658 subscribers7 August 202616 August 2026
3 measurements spanning 8 days, net +10. 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 647–660 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 04:38658+10
8 Aug 2026, 02:47648no change
7 Aug 2026, 21:49648first reading

Engagement

19 posts held, back to 1 July 2026the 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
103.4%
avg views ÷ 658 subscribers
Avg views / post
680
13 posts measured
Reaction rate
0.21%
reactions ÷ views · ER floor
Posts in window
14
of 19 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. It is computed over the 5 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (1 July 20266 August 2026)
Views total8,845
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:47 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.

Reaction mix

11 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍436.4%
218.2%
💩218.2%
😡218.2%
😁19.09%

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

Measured over the 19 most recent posts we hold, published 1 July 2026 to 6 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

6 Aug 2026, 09:56 UTC398 viewsread 8 August 2026

#进度同步 #香港区域 #维护信息 我们预计将于下周将香港故障硬件进行更换,维护时长约2Hours 期间网络会中断 具体时间和维护窗口将在后续公布 网站: https://mhyidc.com 群组: https://t.me/hoyoversenet

4 Aug 2026, 17:30 UTC484 views1 reactionsread 8 August 2026
Photo

#进度同步 德国9929 v6也已经优化完毕 电信163-retn 回程9929 移动联通双程9929 网站: https://mhyidc.com 群组: https://t.me/hoyoversenet

👍1

2 Aug 2026, 18:56 UTC589 views0 reactionsread 8 August 2026

#维护 因德国区域产品销量超出预期,服务器内存资源不足,为防止出现超售情况,我们将进行短暂停机扩容升级。 维护时长:10 分钟,期间服务暂时关闭,给您带来不便敬请谅解。 3.40更新 预计还需要1小时左右 (ps 远程手不知道在搞什么飞机) 3.53 已完成

2 Aug 2026, 06:07 UTC565 viewsread 8 August 2026

#补货 最低配置目前已经补货,目前是享受流量上浮预售特权的最后一天

2 Aug 2026, 06:07 UTC578 viewsread 8 August 2026

🎉 德国BGP-512M 补货通知! 🎊 商品名称: 德国BGP-512M 🚀 补货数量: 50 🕒 补货时间: 2026-08-02 14:01:48

1 Aug 2026, 08:01 UTC701 viewsread 8 August 2026

#进度同步 德国目前已更新完到期时间开始计费 如果您对到期时间有疑问 尽快开启工单

31 Jul 2026, 15:39 UTC701 viewsread 8 August 2026
Photo

#进度同步 德国目前V4已经彻底优化完毕 v6还需等待联通操作 移动到联通偶尔会出现跨网问题后续将动态切换最优路由 9929/CMIN2/Retn

30 Jul 2026, 16:55 UTC875 views2 reactionsread 8 August 2026
Photo

预售为了满足小流量用户的需求 新增配置如下仅售17.99 1C 512M 5G SSD 600G(享受20%流量上浮 ) 目前德国已经开机线路持续优化中 优化完毕统一补偿时间 目前多线程实测最高2Gbps 德国纯净原生IP加持 无需落地 网站: https://mhyidc.com 群组: https://t.me/hoyoversenet

2

27 Jul 2026, 03:57 UTC855 views3 reactionsread 8 August 2026

#临时维护 尊敬的客户/用户: 您好! 因虚拟化系统在部署过程中发生配置偏差,导致部分服务器实例被错误地分配至非预期的存储磁盘。为保障服务的稳定运行与数据安全,我们现计划对受影响的服务器进行紧急迁移操作,将其整体迁移至正确的磁盘设备。 操作安排如下: 操作内容:关闭受影响的服务器实例,完成数据与配置的完整迁移; 预计耗时:整个迁移过程预计在 10分钟以内 完成; 影响范围:迁移期间,相关服务器将暂时无法提供服务,服务恢复后所有功能将自动恢复正常。 我们将全力压缩操作时间,尽可能减少对您业务的影响。对于此次操作给您带来的不便,我们深表歉意,并感谢您的理解与支持。 网站: https://mhyidc.com 群组: https://t.me/hoyoversenet

😡2😁1

26 Jul 2026, 15:54 UTCviews —

Hoyoverse Network pinned «#进度同步 尊敬的客户,您好! 您的德国服务器现已全部开机,系统运行正常,相关资源均已分配就绪。 特别提醒: 目前 9929优化路由(联通AS9929)暂未接通,我们正积极与上游协调接入,预计近期完成。在此期间,您通过普通国际线路仍可正常访问和管理服务器,服务不受影响。 目前暂时不更新到期时间 等9929路由接通后在开始计费 预售也将于9929正式接通后在结束 待9929路由正式启用后,我们将第一时间告知。给您带来的不便深表歉意,感谢您的理解与耐心! 如有任何疑问,请随时联系我们的技术支持团队。 祝您使用愉快!…»

26 Jul 2026, 15:07 UTC520 viewsread 8 August 2026
Forwarded from @NineOneTelecom

核心交换机维护 2026/7/27 2:00 UTC+8 更新交换机配置 约中断~10min

Showing the 12 most recent of 19 posts we hold for @hoyoversenetwork. 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 — 931,148 of 1,481,306entries 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.

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.

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

“Hoyoverse Network” (@hoyoversenetwork), 658 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/hoyoversenetwork.

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.