Telegram RegisterThe public register of Telegram

Channel

辉夜Proxy Channel

@hyproxy_channel

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

1,475subscribers

+13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001845436397
TypeChannel
Username@hyproxy_channel
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/hyproxy_channel

Growth

1,4611,4751,4687 August 2026 — 1,462 subscribers7 August 2026 — 1,462 subscribers8 August 2026 — 1,461 subscribers11 August 2026 — 1,470 subscribers14 August 2026 — 1,475 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +13. 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 1,459–1,477 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 02:091,475+5
11 Aug 2026, 05:141,470+9
8 Aug 2026, 04:271,461-1
7 Aug 2026, 22:011,462no change
7 Aug 2026, 12:091,462first reading

Engagement

20 posts held, back to 7 August 2025the 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
20.5%
avg views ÷ 1,475 subscribers
Avg views / post
303
1 post measured
Reaction rate
1.32%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 31 July 2026
Posts held20 (7 August 202531 July 2026)
Views total303
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:01 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

84 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2934.5%
custom 62538064240574496532732.1%
custom 54565937028834417731720.2%
custom 625372321336105753089.52%
👍22.38%
custom 623115631702153911011.19%

Custom emoji. 4 of the rows above are 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 counts beside them areTelegram’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 10 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 84reactions 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 August 2025 to 31 July 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

31 Jul 2026, 16:05 UTC303 views4 reactionsread 7 August 2026

辉夜Proxy四周年优惠 全场七折优惠码 4year 有效时间2026.8.1-2026.9.1 推荐符合以下条件用户使用 1. 使用移动/联通网络 2. 不在 新疆/江苏/福建泉州等地区 (若不满足以上两个条件,使用体验可能无法得到保证) www.hyproxy.org @hyproxy_channel

4

22 Apr 2026, 13:29 UTC≈1,670 views3 reactionsread 7 August 2026
Photo

下载站更新了根据系统和芯片架构筛选适合您的代理软件的功能 欢迎体验 纯公益无SLA镜像下载站 主地址 https://download.hyproxy.net/ 备用地址 https://download.hyproxy.org/ @hyproxy_channel

3

20 Apr 2026, 14:08 UTC≈1,400 viewsread 7 August 2026

流量处理有问题 今天五点后到维护完成前有使用流量记录的可以发工单全额补偿重置流量

20 Apr 2026, 09:08 UTC≈1,120 viewsread 7 August 2026

网站将进行升级维护 暂不可使用 预计维护时间一小时

5 Apr 2026, 09:19 UTC≈1,660 views11 reactionsread 7 August 2026

新增AnyTLS直连节点 香港美国节点直连 0.4倍率 新加坡和日本直连 0.2倍率 请更新您的代理软件到最新版本以支持AnyTLS协议节点 Android手机推荐: Srufboard [下载地址](https://download.hyproxy.org/files/surfboard/mobile-arm64-v8a-release.apk) Windows电脑推荐: Clash Verge [下载地址](https://download.hyproxy.org/files/clash-verge-rev/Clash.Verge_2.4.7_x64-setup.exe) Clash Party [下载地址](https://download.hyproxy.org/files/clash-party/mihomo-party-windows-1.9.4-x64-setup.exe)

6custom 62538064240574496535

31 Mar 2026, 16:35 UTC≈1,410 views9 reactionsread 7 August 2026

免单优惠券码: 41 可用于: 所有一次性订阅重置 所有周期套餐重置包 仅限今日有效 限量41份,先到先得

9

16 Feb 2026, 16:04 UTC≈2,020 views11 reactionsread 7 August 2026
Photo

新年快乐! 感谢您对辉夜Proxy一直以来的支持! 我们准备了50份总价50USDT的随机红包送给大家, 希望能为各位的新年增添一点小彩头! https://www.bsmkweb.com/activity/red-packets/SRPC64123010411126044486409/share 辉夜Proxy新年七折券: new2026 辉夜Proxy官网: www.hyproxy.org @hyproxy_channel

6custom 62538064240574496535

16 Feb 2026, 07:23 UTC≈1,470 viewsread 7 August 2026

新年七折优惠码 new2026 2026年2月16日-2026年2月28日 此外部分节点年后重新上架

23 Jan 2026, 14:00 UTC≈1,760 viewsread 7 August 2026

节点域名已更换 请更新订阅获取最新节点信息

31 Dec 2025, 16:16 UTC≈2,230 views1 reactionsread 7 August 2026

元旦快乐 七折优惠码 2026 有效期 2026/01/01-2026/01/07

custom 62538064240574496531

3 Dec 2025, 11:28 UTC≈2,770 views17 reactionsread 7 August 2026

订阅线路协议更新提醒 由于近期防火墙策略升级,实现了对特性协议的精准流量封锁, 我们全面升级了所有节点的协议与线路以保证您的上网体验。 此外我们还额外新增了五十个冷门地区节点供您使用。 (二编,冷门节点暂不可用,后续会重新开放) 请更新节点信息以获取最新的订阅配置。 @hyproxy_channel

custom 6253806424057449653141custom 62311563170215391101custom 62537232133610575301

Showing the 12 most recent of 20 posts we hold for @hyproxy_channel. 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 — 1,022,217 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.

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

“辉夜Proxy Channel” (@hyproxy_channel), 1,475 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hyproxy_channel.

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.