Telegram RegisterThe public register of Telegram
Telegram profile photo for Heki 资讯

Channel

Heki 资讯

@heki_news

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

370subscribers

+7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003655692975
TypeChannel
Username@heki_news
CreatedBetween 1 December 2025 and 4 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/heki_news

Growth

363370366.56 August 2026 — 363 subscribers6 August 2026 — 363 subscribers7 August 2026 — 366 subscribers14 August 2026 — 370 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +7. 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 362–371 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:35370+4
7 Aug 2026, 08:44366+3
6 Aug 2026, 21:02363no change
6 Aug 2026, 14:52363first reading

Engagement

20 posts held, back to 4 April 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
96.5%
avg views ÷ 370 subscribers
Avg views / post
357
1 post measured
Reaction rate
0.28%
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 22 July 2026
Posts held20 (4 April 202622 July 2026)
Views total357
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:02 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

20 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
945.0%
👍630.0%
👏210.0%
🔥210.0%
🤷‍♀15.00%

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 9 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 20reactions 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 4 April 2026 to 22 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

22 Jul 2026, 11:49 UTC357 views1 reactionsread 6 August 2026

Heki v1.2.3 🆕 新功能 新增 PPanel ShadowsocksR 节点支持 新增 PPanel 结构化 Shadowsocks 插件适配,支持 Simple Obfs、V2Ray Plugin、Gost、Shadow-TLS、Restls、KCPTun 接入 PPanel 最新 TUIC、Mieru、调度间隔及流量上报字段 新增 XBoard / XiaoV2Board 可信转发头支持,可正确获取前置代理后的客户端真实 IP ⚡ 优化 优化诸多已知问题 🛠 定制 需要魔改定制协议、插件适配或特殊面板对接的,可以直接联系我 📦 更新 heki update 1.2.3 docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

🤷‍♀1

5 Jul 2026, 03:54 UTC555 views3 reactionsread 6 August 2026

Heki v1.2.2 🆕 新功能 - 增强 TUIC V5 支持,新增 ECH key 能力 - XBoard V2 上报能力增强,状态同步更完整 🐛 修复 - 修复 XiaoV2Board / XBoard 下 Shadowsocks 部分兼容问题 - 修复部分面板节点状态、在线 IP、用户同步异常问题 - 修复诸多已知问题 ⚡ 优化 - 优化 Shadowsocks / SS2022 缓存与连接处理逻辑 - 优化限速器实现,降低 CPU 占用 - 优化授权校验与整体运行稳定性 - 同步更新协议依赖版本:Hysteria2 core / extras v2.9.2、Mieru v3.34.0、ShadowTLS v0.2.1 - 优化诸多已知问题 🛠 定制 - 需要魔改定制协议、插件适配或特殊面板对接的,可以直接联系我 📦 更新 heki update 1.2.2 docker pull hekicore/heki

👍21

6 Jun 2026, 02:02 UTC847 views4 reactionsread 6 August 2026

Heki v1.2.1 🆕 新功能 - Hysteria2 上游 core / extras 升级到 v2.9.2 🐛 修复 - 优化诸多已知问题和细节 📦 更新 heki update 1.2.1 docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

2👍2

24 May 2026, 05:49 UTC≈1,000 viewsread 6 August 2026

Heki v1.2.0 🆕 新功能 - Mieru 现已支持 Proxy Protocol - Mieru TCP 支持 Proxy Protocol v1 / v2 - Mieru UDP 支持 Proxy Protocol v2 DGRAM,可获取真实源地址并保持正确回包映射 - 在线授权 max_users 现已支持热刷新,升级授权后无需重启即可生效 🐛 修复 - 修复 xiaov2board 在 AnyTLS / v2node 上报场景下在线状态和在线人数显示异常的问题 - 优化诸多已知问题和细节 📦 更新 heki update 1.2.0 docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

16 May 2026, 10:20 UTC917 viewsread 6 August 2026

Heki v1.1.9 🆕 新功能 - AnyTLS 现已补齐服务端 ECH 支持,并适配 XBoard / XiaoV2Board 常见下发格式 🐛 修复 - 修复日志长期运行时无关日志导致占用过大的问题 -优化诸多已知问题和细节 📦 更新 heki update 1.1.9 docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

8 May 2026, 12:26 UTC≈1,040 views3 reactionsread 6 August 2026

Heki v1.1.8 🆕 新功能 - Docker / docker-compose 现已支持直接配置 Proxy Protocol 新增支持: proxy_protocol udp_proxy_protocol force_proxy_protocol - Mieru 新增配置项 mieru_user_hint_is_mandatory 默认关闭,优先兼容旧版或第三方 Mieru 客户端;多用户节点如需降低异常连接、错误用户名或缺少 user hint 时的 CPU 消耗,可手动开启 📦 更新 heki update docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

3

30 Apr 2026, 16:44 UTC946 viewsread 6 August 2026

Heki v1.1.7 🆕 新功能 - 证书申请支持切换 ACME CA,现已支持 Let's Encrypt 和 ZeroSSL - 补齐 PPanel 的 xhttp/splithttp 配置链路,host、path、xhttp_mode、xhttp_extra 现在可以正确下发到运行时 🐛 修复 - 优化 AnyTLS 稳定性,修复 WebSocket 场景反复显示建立/断开问题 - 优化 TUIC 内存占用 - 优化 Mieru 维护与热更新稳定性 📦 更新 heki update docker pull hekicore/heki:latest && docker compose up -d 📚 https://hekicore.github.io/heki-docs/

27 Apr 2026, 14:23 UTC785 views2 reactionsread 6 August 2026

Heki v1.1.6 🆕 新功能 - AnyTLS 整体性能优化,实测提升约 18% - 配置现已支持显式 `routes_file / block_list_file / white_list_file / dns_rules_file`,可把本地路由、审计、白名单与 DNS 规则文件直接指向任意路径 - 已同步 Mieru / Hysteria2 / TUIC 最新上游核心代码: Mieru v3.32.0 hysteria core/extras v2.8.2 sing-quic v0.6.1 - Mieru 在同步上游核心代码后,补齐静态 DNS host mapping 校验与下发、可选 userHintIsMandatory 收口,以及更快的 user-hint 选路逻辑 - xhttp / splithttp 入站运行时现已支持 VMess / VLESS / Trojan / AnyTL

👏2

25 Apr 2026, 04:23 UTC643 views0 reactionsread 6 August 2026

Heki v1.1.5 🐛 优化修复已知问题 📦 更新 heki update docker pull hekicore/heki:latest && docker compose up -d 📚 文档 https://hekicore.github.io/heki-docs/

20 Apr 2026, 14:16 UTC809 views1 reactionsread 6 August 2026

Heki v1.1.4 🆕 新功能 - AnyTLS 现已支持UDP 入站与 routes.toml AnyTLS 出站能力 - 用户流量耗尽后,服务端会主动断开该用户现有连接,覆盖 vmess / vless / trojan / ss / ss2022 / ssr / anytls / tuic / hysteria2 / mieru / naive 🐛 优化修复已知问题 📦 更新 heki update docker pull hekicore/heki:latest && docker compose up -d 📚 文档 https://hekicore.github.io/heki-docs/

1

17 Apr 2026, 16:02 UTC735 views0 reactionsread 6 August 2026

# Heki v1.1.3 🆕 新功能 - 新增 xhttp / splithttp 入站支持,已补齐 VMess / VLESS / Trojan / AnyTLS 🐛 优化修复已知问题 📦 更新 heki update docker pull hekicore/heki:latest && docker compose up -d 📚 文档 https://hekicore.github.io/heki-docs/

17 Apr 2026, 02:59 UTC649 viewsread 6 August 2026

🚀 Heki - 高性能多协议代理后端 完全独立内核,从零重写,不基于任何 core 📡 十大协议全覆盖 VMess / VLESS / Trojan / SS / SSR / Hysteria2 / TUIC / AnyTLS / Naive / Mieru 不只是协议名更多,而是真正把新协议、新字段、新传输层和复杂落地场景一起接住。 🔐 主流协议能力完整落地 - VMess:支持 tcp / ws / httpupgrade / h2 / grpc,兼容 AEAD 与 legacy 模式,支持错误访问防护 - VLESS:支持 tcp / ws / httpupgrade / h2 / grpc,支持 Reality / Vision / decryption - Trojan:支持 tcp / ws / httpupgrade / h2 / grpc - SS:支持传统 AEAD 与 SS2022 - SSR:支持协

Showing the 12 most recent of 20 posts we hold for @heki_news. 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 — 410,252 of 1,549,704entries 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.

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

“Heki 资讯” (@heki_news), 370 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/heki_news.

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.