Channel
@clashbyhako
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,313subscribers
+2,026 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004470944182 |
|---|---|
| Type | Channel |
| Username | @clashbyhako |
| Created | 28 July 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/clashbyhako |
Technology — 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 16 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 03:18 | 2,313 | +272 |
| 14 Sept 2026, 11:16 | 2,041 | +218 |
| 10 Sept 2026, 23:40 | 1,823 | +193 |
| 5 Sept 2026, 15:00 | 1,630 | +348 |
| 1 Sept 2026, 18:55 | 1,282 | +856 |
| 25 Aug 2026, 09:28 | 426 | +136 |
| 17 Aug 2026, 10:25 | 290 | +2 |
| 8 Aug 2026, 20:52 | 288 | +1 |
| 8 Aug 2026, 08:19 | 287 | no change |
| 8 Aug 2026, 01:34 | 287 | first reading |
5 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 50.0% | |
| ❤ | 8 | 26.7% | |
| 😨 | 7 | 23.3% |
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 4 of the 5 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 28 July 2026 to 2 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.
关于 TestFlight 版本逾期的通知 尊敬的 Clash 测试用户： 目前，TestFlight 中的所有测试版本均已过期，暂时无法安装。经核查，Apple 开发者社区中亦有其他开发者遭遇相同情况，此系 App Store Connect 端出现的偶发性技术故障。我们已向 Apple 提交服务请求，目前正在积极跟进处理。 同时，我们正准备上传新版本（Build 1.0.0.(10)）进行测试。 由此带来的不便，敬请谅解。
😨7❤2
1.0.0 (8) TestFlight Release New Feature: Users can paste a node, and Clash will offer to add it. Supported protocols include ss, ssr, vmess, vless, trojan, hysteria, hysteria2, tuic, anytls, and socks5. These are available in the dialects panels, as well as nodes exported from other clients. Bug Fix: Resolves two application crashes and enables subscriptions that were previously rejected due to the absence of a DN…
❤5
Clash 客户端的 iPhone 与 iPad 版本目前正在接受 App Store 审核。为响应审核反馈并完善正式发布版本，Apple 客户端目前正在进行重大调整。 完整的 Apple 客户端源代码我们计划在首次审核版本及其架构稳定后，再发布第一份公开源码。公开仓库将提供用户实际能够安装的版本，而非一份即将过时、与正式版本存在差异的临时快照。 暂缓首次发布客户端源码，并不代表我们改变了完整开源的承诺。待首次审核周期稳定后，本仓库将提供以下内容： - 完整的 Apple 客户端源代码 - 构建与开发说明 - 开源许可信息 - 贡献指南 - 与公开版本对应的版本记录 macOS 与 tvOS 版本仍在开发中。
👍15❤1
🎉 Clash 1.0.0 已提交 Apple App Store 审核 Clash 经典回归，这次是 Apple 原生。 首发版本面向 iPhone、iPad，由开源 Hako 内核驱动，支持订阅导入、多种出站协议，以及规则、全局和直连三种模式。 这是 Clash by Hako 官方频道。审核进度、正式下载地址、版本更新与重要公告都会在这里发布。 🎉 Clash 1.0.0 has been submitted for Apple App Store review Clash is back — this time, it’s native to Apple platforms. The first release is coming to iPhone, iPad. Powered by the open-source Hako core, it supports subscription imports, …
Channel created
Showing the 5 most recent of 5 posts we hold for @clashbyhako. 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.
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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Clash by Hako Channel” (@clashbyhako), 2,313 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/clashbyhako.
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.