Telegram RegisterThe public register of Telegram
Telegram profile photo for 辉耀主频道

Channel

辉耀主频道

@HYZPD

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

7,418subscribers

+636 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-1002492486833
TypeChannel
Username@HYZPD
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/HYZPD

Growth

6,7827,4187,1007 August 2026 — 6,782 subscribers7 August 2026 — 6,782 subscribers7 August 2026 — 6,783 subscribers11 August 2026 — 6,844 subscribers14 August 2026 — 6,941 subscribers17 August 2026 — 7,000 subscribers20 August 2026 — 7,117 subscribers23 August 2026 — 7,150 subscribers26 August 2026 — 7,177 subscribers29 August 2026 — 7,233 subscribers2 September 2026 — 7,290 subscribers7 September 2026 — 7,418 subscribers7 August 20267 September 2026
12 measurements spanning 31 days, net +636. 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 6,687–7,513 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 06:377,418+128
2 Sept 2026, 03:027,290+57
29 Aug 2026, 23:177,233+56
26 Aug 2026, 18:267,177+27
23 Aug 2026, 23:487,150+33
20 Aug 2026, 13:587,117+117
17 Aug 2026, 17:257,000+59
14 Aug 2026, 07:376,941+97
11 Aug 2026, 02:026,844+61
7 Aug 2026, 19:236,783+1
7 Aug 2026, 12:166,782no change
7 Aug 2026, 12:096,782first reading

Engagement

61 posts held, back to 8 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 12 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.0%
avg views ÷ 7,418 subscribers
Avg views / post
813
34 posts measured
Reaction rate
1.16%
reactions ÷ views · ER floor
Posts in window
34
of 61 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 20 August 2026
Posts held61 (8 July 202620 August 2026)
Views total27,638
Reactions total320
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 15:18 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

Video runtime
2m 23s
Average length
48s

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

688 reactions across 60 posts, in 17 distinct kinds. The most used accounts for 58.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍40358.6%
🖕10515.3%
7611.0%
👎385.52%
😘162.33%
🤡111.60%
💩101.45%
🤔81.16%
🫡71.02%
🤣40.581%
😁30.436%
🤨20.291%
🍌10.145%
🎃10.145%
😱10.145%
🥰10.145%
🥴10.145%

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

Measured over the 61 most recent posts we hold, published 8 July 2026 to 20 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

20 Aug 2026, 15:03 UTC37 views6 reactionsread 20 August 2026
Video

Video, posted without a caption

👍6

Signed 怒怒耀

20 Aug 2026, 09:15 UTC270 views11 reactionsread 20 August 2026

视频结尾闪退已修复

👍11

Signed 怒怒耀

20 Aug 2026, 09:14 UTC268 views10 reactionsread 20 August 2026
Video

Video, posted without a caption

👍10

Signed 怒怒耀

19 Aug 2026, 22:39 UTC420 views3 reactionsread 20 August 2026

接联想y700系列刷机 @HuiYao6

👍3

Signed 怒怒耀

19 Aug 2026, 21:32 UTC429 views9 reactionsread 20 August 2026

NY半火 天卡20FZ0leZs5 天卡Pptt6Ol6Sa 天卡VxhKft9tlk 天卡22Z82JkIm7 天卡3B79FjkP9c 天卡1UchvliTQz 天卡BCGIv6xIog 天卡iWapuU6Yl7 天卡Yz7WswwJBw 天卡96zlyf2gvh

👍81

Signed 努努耀

19 Aug 2026, 20:54 UTC424 views5 reactionsread 20 August 2026
File

NY半火 ------------------------------- 对接众多驱动(QX,RT,TWT,DITPRO等) 全新自研内核级隐藏进程读写无视检测 纯外部 Nohook No注入 适配功能: 局内衣服 枪械秒刷 枪械开火换弹特效 枪械自适应打击 挂件 检视 全局秒遍历美化 裸奔范围 开火肩射 0占用 众多手持功能 0闪退 0封号 ------------------------------- 全新重构多线程架构 0占用 0卡顿 0禁令 ------------------------------- 神秘赞助:https://918.oioix.cn/links/1DC1DFB3 反馈加时 @HuiYao6

👍41

Signed 努努耀

19 Aug 2026, 20:52 UTC399 views7 reactionsread 20 August 2026
File

宫水三叶瓦手美化 解决侦察无音效✔️ DIY自定义特效✔️ 无视加时一小时✔️ 长期稳定项目✔️ 多款内核读写✔️ 众多物品美化✔️ 裸奔无后✔️ 裸奔广角✔️ 频道 @HYZPD 卡网:https://918.oioix.cn/links/1DC1DFB3 反馈可加时长 @HuiYao6

👍7

Signed 努努耀

19 Aug 2026, 13:53 UTC494 views9 reactionsread 20 August 2026

这种人他妈的是不是脑子有病?4957589253 快手ID帮我点点举报,或者把他支付宝套出来😀,你妈的,骚扰我对象,看他妈逼内搭呢

👍9

Signed Midnight Echo

19 Aug 2026, 13:52 UTC483 views9 reactionsread 20 August 2026
Photo

操你妈的,七夕节给我气死了,我对象发给我的

👍8🤣1

Signed Midnight Echo

18 Aug 2026, 13:17 UTC663 views15 reactionsread 20 August 2026

准备出一个和平的稳定半火项目 叫什么名字还没有想好 你们有推荐的吗🤓

👍132

Signed 努努耀

17 Aug 2026, 23:19 UTC749 views6 reactionsread 20 August 2026

对接新版ditpro_ko刷了6.6读写会卡屏重启不知道是不是我自己的原因

👍51

Signed 努努耀

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

Polls

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

7 Aug 2026, 17:08 UTCAnonymous Poll234 voters

和平和PUBG美化更新软件还是sh

  1. 软件43%
  2. sh57%

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 61 most recent posts we hold, published 8 July 2026 to 20 August 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

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.

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.

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

“辉耀主频道” (@HYZPD), 7,418 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/HYZPD.

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.