Telegram RegisterThe public register of Telegram
Telegram profile photo for Clash-Party channel

Channel

Clash-Party channel

@MihomoPartyChannel

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

16,658subscribers

+2,404 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002349572233
TypeChannel
Username@MihomoPartyChannel
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/MihomoPartyChannel

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 the other topics.

Growth

14,25416,83115,542.516,6586 August 202611 November 2026
65 measurements spanning 97 days, net +2,404. 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 13,867–17,218 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
11 Nov 2026, 06:4916,658-37
9 Nov 2026, 14:1616,695-39
8 Nov 2026, 09:1816,734-34
7 Nov 2026, 06:3816,768-24
6 Nov 2026, 05:4716,792-36
5 Nov 2026, 02:5016,828-3
4 Nov 2026, 00:5416,831+12
2 Nov 2026, 00:0516,819+9
1 Nov 2026, 01:4716,810+35
31 Oct 2026, 04:1816,775+43
30 Oct 2026, 04:5916,732-5
29 Oct 2026, 06:2716,737+66
28 Oct 2026, 05:0016,671+66
27 Oct 2026, 02:4416,605+21
26 Oct 2026, 04:2816,584+6
25 Oct 2026, 05:1016,578+29
24 Oct 2026, 08:1516,549+43
23 Oct 2026, 08:0516,506+26
22 Oct 2026, 08:0816,480+56
21 Oct 2026, 03:1016,424first reading

Engagement

25 posts held, back to 3 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.0%
avg views ÷ 16,658 subscribers
Avg views / post
3,660
1 post measured
Reaction rate
0.355%
reactions ÷ views · ER floor
Posts in window
1
of 25 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 18 October 2026
Posts held25 (3 October 2025 – 18 October 2026)
Views total3,660
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 18:16 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

Photos
4
Videos
1
Links
66

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

338 reactions across 25 posts, in 7 distinct kinds. The most used accounts for 53.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤18253.8%
👍11935.2%
👏164.73%
🥰102.96%
🎉82.37%
🆒20.592%
🤩10.296%

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

Measured over the 25 most recent posts we hold, published 3 October 2025 to 18 October 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

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

18 Oct 2026, 12:19 UTC≈3,660 views13 reactionsread 12 November 2026

🌟 Clash Party v2.0.4 正式发布 # 2.0.4 新功能 - 新增简易模式,可视化编辑订阅、代理组、规则、规则集、DNS 及域名嗅探配置 - 简易模式支持本地节点管理、节点链接导入及订阅代理集合高级设置 - 支持从连接详情快速添加简易模式规则,内联规则集支持列表编辑 - 新增切换节点时仅关闭当前代理组连接的选项 - 新增 DNS 覆写保护开关、日志等级筛选及 macOS 流量文字颜色设置 - 侧边栏折叠后支持悬停展开 性能优化 - 优化历史流量统计迁移,减少磁盘写入并增加迁移提示 - 优化跨平台连接应用识别及图标处理,改进 Linux 应用图标匹配 修复 - 修复系统唤醒后 TUN 重建时配置不完整,以及修改 TUN 设置后未重启内核的问题 - 修复启动时未等待初始代理集合就绪及代理组选择状态未刷新的问题 - 修复不含节点的远程订阅模板无法使用,以及订阅自动更新间隔字段不一致的问题 - 修复配置模…

❤11👍1🤩1

22 Sept 2026, 11:27 UTC≈4,990 views14 reactionsread 12 November 2026

🚧 Clash Party Dev Build 开发版本发布 基于版本: 2.0.3-d0922.e36747b 提交哈希: e36747b 更新日志: # 2.0.3 新功能 - 新增订阅 DNS 覆写保护,避免意外覆盖自定义解析配置 - Smart 内核新增模型状态、手动下载及自动更新设置 - 支持按 WiFi SSID 自动切换订阅,macOS 使用事件驱动检测 - 新增自定义 GitHub 下载代理和覆写全局开关快捷入口 - 机场插件支持多网关、备用发现源、签名发现文档、网关说明及网络请求自动回退 性能优化 - 优化应用启动流程,首屏完成后再执行其余初始化 - 合并连接列表高频更新,页面不可见时暂停处理 - 修复连接页面、IPC 监听器及 Monaco 编辑器相关资源泄漏 修复 - 修复恶意 `rule-providers` 配置可能执行任意命令的安全问题 - 修复内核下载校验、解压失败及 macOS 路…

👍8❤6

20 Sept 2026, 13:59 UTC≈4,070 views16 reactionsread 12 November 2026

🌟 Clash Party v2.0.3 正式发布 # 2.0.3 新功能 - 新增订阅 DNS 覆写保护,避免意外覆盖自定义解析配置 - Smart 内核新增模型状态、手动下载及自动更新设置 - 支持按 WiFi SSID 自动切换订阅,macOS 使用事件驱动检测 - 新增自定义 GitHub 下载代理和覆写全局开关快捷入口 - 机场插件支持多网关、备用发现源、签名发现文档、网关说明及网络请求自动回退 性能优化 - 优化应用启动流程,首屏完成后再执行其余初始化 - 合并连接列表高频更新,页面不可见时暂停处理 - 修复连接页面、IPC 监听器及 Monaco 编辑器相关资源泄漏 修复 - 修复恶意 `rule-providers` 配置可能执行任意命令的安全问题 - 修复内核下载校验、解压失败及 macOS 路径含空格时的权限问题 - 修复 Smart 组生成、设置热重载及模型重复下载问题 - 修复 PAC、Gi…

❤8👍8

14 Aug 2026, 15:11 UTC≈6,880 views12 reactionsread 12 November 2026

🌟 Clash Party v2.0.2 正式发布 # 2.0.2 修复 (Fix) - 修复数字小键盘的加、减、乘、除及小数点按键无法正确注册为全局快捷键的问题 - 修复首次使用欢迎引导中的提示弹层位置配置无效、可能显示异常的问题 - 修复 Linux ARM64 等交叉编译产物可能混入宿主机架构系统代理模块的问题,并增加原生模块架构校验 - 修复 Linux 无法注册托盘图标的问题 下载地址: Windows10/11: - 安装版:64位 | 32位 | ARM64 - 便携版:64位 | 32位 | ARM64 Windows7/8: - 安装版:64位 | 32位 - 便携版:64位 | 32位 macOS 11+: - PKG:Intel | Apple Silicon macOS 10.15+: - PKG:Intel | Apple Silicon Linux: - DEB…

❤10👍2

11 Aug 2026, 12:44 UTC≈5,600 views24 reactionsread 12 November 2026

🌟 Clash Party v2.0.1 正式发布 # 2.0.1 性能优化 (Performance) - 优化应用冷启动关键路径,首屏路由按需加载,并在首屏渲染后再初始化运行文件、内核、流量监控和 Sub-Store,减少启动阶段的资源争用 - 优化应用退出清理,核心进程、DNS 和系统代理采用有界清理流程,避免慢 helper 或子进程长时间阻塞退出 - 支持按配置跳过启动前的内核配置检查,缩短特定场景下的内核启动耗时 修复 (Fix) - 修复 Linux Wayland 下通过托盘复制代理环境变量无效的问题 - 修复启动阶段快速操作内核可能导致重复启动、重启死锁、停止后重新拉起,以及轻量模式无法正确保持内核运行的问题 - 修复内核运行中意外退出后恢复能力不足的问题,自动恢复最多尝试两次,并在显式停止或应用退出时立即取消后续重试 - 修复主窗口首次加载失败或 renderer 崩溃后可能白屏、无法恢复或后台初始…

👍15❤8🥰1

7 Jul 2026, 02:14 UTC≈7,330 views32 reactionsread 12 November 2026

🌟 Clash Party v2.0.0 正式发布 # 2.0.0 新功能 (Feat) - 机场插件机制,服务商请参考:`docs/plugin/机场服务端对接指南-v2.md` - 插件安装支持拖拽插件文件 - 新增按状态自定义托盘图标 - 新增更多 GitHub 下载代理 - 新增记住所选侧边卡片开关 - 新增锁定侧边卡片位置开关 - 新增内核启动检测方式,可选择使用 Post Up 启动钩子 性能优化 (Performance) - 优化大型订阅下代理组延迟测试的更新性能,减少界面卡顿 - 修复连接图标和应用名称缓存未限制大小的问题,避免内存持续增长 修复 (Fix) - 部分场景下的白屏问题 - Linux (GNOME Wayland) 下窗口尺寸无法记忆、每次启动都最大化的问题,同时保持 Windows 高 DPI 下窗口不再逐次变大 - IP 信息来源下拉切换延迟和请求竞态的问题 - 更新下载多代理…

👏14❤6🎉6👍6

5 Jul 2026, 18:30 UTC≈4,670 views15 reactionsread 12 November 2026

🚧 Clash Party Dev Build 开发版本发布 基于版本: 2.0.0-d0705.53eb7e5 提交哈希: 53eb7e5 更新日志: # 2.0.0 新功能 (Feat) - 机场插件机制,服务商请参考: `docs/plugin/机场服务端对接指南-v2.md` 性能优化 (Performance) - 优化大型订阅下代理组延迟测试的更新性能,减少界面卡顿 - 修复连接图标和应用名称缓存未限制大小的问题,避免内存持续增长 修复 (Fix) - 部分场景下的白屏问题 - Linux (GNOME Wayland) 下窗口尺寸无法记忆、每次启动都最大化的问题,同时保持 Windows 高 DPI 下窗口不再逐次变大 - TUN 排除网段可保存非法 CIDR、且非法项会阻止其它设置保存的问题 # 1.9.6 新功能 (Feat) - 新增 Tunnel 编辑器 - 新增代理组标题显示当前节点…

❤13🆒2

21 Jun 2026, 13:33 UTC≈5,620 views26 reactionsread 12 November 2026

🌟 Clash Party v1.9.6 正式发布 # 1.9.6 新功能 (Feat) - 新增 Tunnel 编辑器 - 新增代理组标题显示当前节点 - 新增 IP 信息来源选择记忆 - 新增关闭应用日志输出选项 - 新增网络信息卡片排序 - 新增记忆侧边栏卡片选中状态 - 新增 Age 加密配置和 Gist 同步支持 - 新增轻量模式行为开关 性能优化 (Performance) - 重构简化连接页 - 优化软件启动和退出速度 - 收敛软件配置,提升渲染性能 - 优化代理组延迟测试结果展示 - 优化核心和 Sub-Store 日志轮转及大小限制截断性能 修复 (Fix) - 修复修改 Mihomo 设置(如日志等级、端口等)后未应用到运行中内核的问题 - 修复托盘菜单可能被回收导致不可用的问题 - 修复 Mihomo 安全路径缺少工作目录的问题 - 修复流量卡片初始尺寸异常的问题 - 修复不允许 IP 段占位…

❤16👍9🥰1

11 May 2026, 13:26 UTC≈8,090 views18 reactionsread 12 November 2026

🌟 Clash Party v1.9.5 正式发布 # 1.9.5 新功能 (Feat) - 更新 mihomo 内核 - 新增 WebDAV 备份文件名包含设备名称 - 新增单个日志文件大小限制和截断机制 - 新增每个订阅独立的 User-Agent 配置 - 新增配置开关和覆写保存时使用 Mihomo 热重载生效 - 新增热重载切换配置后的连接关闭选项 - 新增自定义托盘图标支持及裁剪选择器 - 新增托盘策略组延迟测试入口 - 新增网络延迟测试自定义目标地址 - 新增 fake-ip-filter 规则模式支持 - 新增删除配置文件的确认弹窗 - 使用 mshta 在 Electron 初始化前同步检测 PowerShell 版本 修复 (Fix) - 修复 Win7 兼容性问题 - 修复日志清理正则表达式以正确匹配带前缀的文件名 - 修复渲染端和配置相关的类型安全回归 - 修复订阅超时时间为空时未回退到全局超时时…

❤15🥰3

10 May 2026, 04:58 UTC≈5,830 views5 reactionsread 12 November 2026

🚧 Clash Party Dev Build 开发版本发布 基于版本: 1.9.5-d0510.92f21d0 提交哈希: 92f21d0 更新日志: # 1.9.5 新功能 (Feat) - 更新 mihomo 内核 - 新增 WebDAV 备份文件名包含设备名称 - 新增单个日志文件大小限制和截断机制 - 新增每个订阅独立的 User-Agent 配置 - 新增配置开关和覆写保存时使用 Mihomo 热重载生效 - 新增热重载切换配置后的连接关闭选项 - 新增自定义托盘图标支持 - 新增托盘策略组延迟测试入口 - 新增网络延迟测试自定义目标地址 - 使用 mshta 在 Electron 初始化前同步检测 PowerShell 版本 修复 (Fix) - 修复 Win7 兼容性问题 - 修复日志清理正则表达式以正确匹配带前缀的文件名 - 修复渲染端和配置相关的类型安全回归 - 修复订阅超时时间为空时未回退到全局…

❤3👍1🥰1

26 Apr 2026, 08:46 UTC≈6,190 views7 reactionsread 12 November 2026

🚧 Clash Party Dev Build 开发版本发布 基于版本: 1.9.4-d0426.9ea9da7 提交哈希: 9ea9da7 更新日志: # 1.9.4 新功能 (Feat) - 新增每个订阅独立的 User-Agent 配置 - 使用 mshta 在 Electron 初始化前同步检测 PowerShell 版本 修复 (Fix) - 修复 Win7 兼容性问题 - 修复日志清理正则表达式以正确匹配带前缀的文件名 其他 (Chore) - 重构 rule-item 额外字段处理逻辑并补充类型定义 - 更新依赖 ⚠️ 注意:这是开发版本,可能存在不稳定性,仅供测试使用 下载地址: Windows10/11: - 安装版:64位 | 32位 | ARM64 - 便携版:64位 | 32位 | ARM64 Windows7/8: - 安装版:64位 | 32位 - 便携版:64位 …

❤5👍2

26 Apr 2026, 05:06 UTC≈5,000 views2 reactionsread 12 November 2026

🚧 Clash Party Dev Build 开发版本发布 基于版本: 1.9.4-d0426.f494ff7 提交哈希: f494ff7 更新日志: # 1.9.4 新功能 (Feat) - 新增每个订阅独立的 User-Agent 配置 - 使用 mshta 在 Electron 初始化前同步检测 PowerShell 版本 修复 (Fix) - 修复 Win7 兼容性问题 - 修复日志清理正则表达式以正确匹配带前缀的文件名 其他 (Chore) - 重构 rule-item 额外字段处理逻辑并补充类型定义 - 更新依赖 ⚠️ 注意:这是开发版本,可能存在不稳定性,仅供测试使用 下载地址: Windows10/11: - 安装版:64位 | 32位 | ARM64 - 便携版:64位 | 32位 | ARM64 Windows7/8: - 安装版:64位 | 32位 - 便携版:64位 …

❤2

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

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.

Mentions

Named by 2 registered channels — 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.

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

“Clash-Party channel” (@MihomoPartyChannel), 16,658 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/MihomoPartyChannel.

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.