Channel
@MihomoPartyChannel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
14,903subscribers
+649 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002349572233 |
|---|---|
| Type | Channel |
| Username | @MihomoPartyChannel |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/MihomoPartyChannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 00:42 | 14,903 | +30 |
| 4 Sept 2026, 00:18 | 14,873 | +28 |
| 2 Sept 2026, 16:48 | 14,845 | +20 |
| 1 Sept 2026, 18:24 | 14,825 | +3 |
| 31 Aug 2026, 21:55 | 14,822 | -1 |
| 30 Aug 2026, 21:43 | 14,823 | +14 |
| 29 Aug 2026, 23:45 | 14,809 | +10 |
| 29 Aug 2026, 01:35 | 14,799 | +38 |
| 28 Aug 2026, 00:16 | 14,761 | +8 |
| 27 Aug 2026, 00:18 | 14,753 | +26 |
| 26 Aug 2026, 01:42 | 14,727 | +18 |
| 25 Aug 2026, 01:33 | 14,709 | +23 |
| 23 Aug 2026, 15:15 | 14,686 | +51 |
| 22 Aug 2026, 03:36 | 14,635 | +22 |
| 20 Aug 2026, 23:14 | 14,613 | +24 |
| 20 Aug 2026, 02:25 | 14,589 | +45 |
| 19 Aug 2026, 01:52 | 14,544 | +31 |
| 17 Aug 2026, 22:56 | 14,513 | +25 |
| 16 Aug 2026, 21:43 | 14,488 | +22 |
| 15 Aug 2026, 15:43 | 14,466 | first reading |
22 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 52 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 14 August 2026 |
|---|---|
| Posts held | 22 (3 October 2025 – 14 August 2026) |
| Views total | 6,950 |
| Reactions total | 31 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 11:13 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.
290 reactions across 22 posts, in 6 distinct kinds. The most used accounts for 53.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 154 | 53.1% | |
| 👍 | 100 | 34.5% | |
| 👏 | 16 | 5.52% | |
| 🥰 | 10 | 3.45% | |
| 🎉 | 8 | 2.76% | |
| 🆒 | 2 | 0.69% |
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 22 of the 22 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 290 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 3 October 2025 to 14 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.
🌟 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…
❤8
🌟 Clash Party v2.0.1 正式发布 # 2.0.1 性能优化 (Performance) - 优化应用冷启动关键路径，首屏路由按需加载，并在首屏渲染后再初始化运行文件、内核、流量监控和 Sub-Store，减少启动阶段的资源争用 - 优化应用退出清理，核心进程、DNS 和系统代理采用有界清理流程，避免慢 helper 或子进程长时间阻塞退出 - 支持按配置跳过启动前的内核配置检查，缩短特定场景下的内核启动耗时 修复 (Fix) - 修复 Linux Wayland 下通过托盘复制代理环境变量无效的问题 - 修复启动阶段快速操作内核可能导致重复启动、重启死锁、停止后重新拉起，以及轻量模式无法正确保持内核运行的问题 - 修复内核运行中意外退出后恢复能力不足的问题，自动恢复最多尝试两次，并在显式停止或应用退出时立即取消后续重试 - 修复主窗口首次加载失败或 renderer 崩溃后可能白屏、无法恢复或后台初始…
👍15❤7🥰1
🌟 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
🚧 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
🌟 Clash Party v1.9.6 正式发布 # 1.9.6 新功能 (Feat) - 新增 Tunnel 编辑器 - 新增代理组标题显示当前节点 - 新增 IP 信息来源选择记忆 - 新增关闭应用日志输出选项 - 新增网络信息卡片排序 - 新增记忆侧边栏卡片选中状态 - 新增 Age 加密配置和 Gist 同步支持 - 新增轻量模式行为开关 性能优化 (Performance) - 重构简化连接页 - 优化软件启动和退出速度 - 收敛软件配置，提升渲染性能 - 优化代理组延迟测试结果展示 - 优化核心和 Sub-Store 日志轮转及大小限制截断性能 修复 (Fix) - 修复修改 Mihomo 设置（如日志等级、端口等）后未应用到运行中内核的问题 - 修复托盘菜单可能被回收导致不可用的问题 - 修复 Mihomo 安全路径缺少工作目录的问题 - 修复流量卡片初始尺寸异常的问题 - 修复不允许 IP 段占位…
❤16👍9🥰1
🌟 Clash Party v1.9.5 正式发布 # 1.9.5 新功能 (Feat) - 更新 mihomo 内核 - 新增 WebDAV 备份文件名包含设备名称 - 新增单个日志文件大小限制和截断机制 - 新增每个订阅独立的 User-Agent 配置 - 新增配置开关和覆写保存时使用 Mihomo 热重载生效 - 新增热重载切换配置后的连接关闭选项 - 新增自定义托盘图标支持及裁剪选择器 - 新增托盘策略组延迟测试入口 - 新增网络延迟测试自定义目标地址 - 新增 fake-ip-filter 规则模式支持 - 新增删除配置文件的确认弹窗 - 使用 mshta 在 Electron 初始化前同步检测 PowerShell 版本 修复 (Fix) - 修复 Win7 兼容性问题 - 修复日志清理正则表达式以正确匹配带前缀的文件名 - 修复渲染端和配置相关的类型安全回归 - 修复订阅超时时间为空时未回退到全局超时时…
❤15🥰3
🚧 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
🚧 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
🚧 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
🌟 Clash Party v1.9.4 正式发布 # 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位 | 32位 macOS 11+： - PKG：Intel | Apple Silicon macOS 10.15+： - PKG：Intel | Appl…
👍16❤2🎉1
🌟 Clash Party v1.9.4 正式发布 # 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位 | 32位 macOS 11+： - PKG：Intel | Apple Silicon macOS 10.15+： - PKG：Intel | Appl…
❤1
🌟 Clash Party v1.9.3 正式发布 # 1.9.3 新功能 (Feat) - 新增网络信息页卡片 - 更新下载新增进度显示和 SHA256 完整性校验 修复 (Fix) - 修复更新软件时的超时问题 - 修复切换离开智能内核时未清理智能覆盖配置的问题 - 修复部分机场返回压缩包导致订阅导入失败的问题 - 修复悬浮窗无法关闭的问题 - 修复日志滚动延迟的问题 - 修复添加新订阅时只能重启生效的问题 - 修复进入代理列表页面时滚动位置未重置到顶部的问题 - 修复托盘流量图标闪烁问题 其他 (Chore) - 更新依赖 下载地址： Windows10/11： - 安装版：64位 | 32位 | ARM64 - 便携版：64位 | 32位 | ARM64 Windows7/8： - 安装版：64位 | 32位 - 便携版：64位 | 32位 macOS 11+： - PKG：Intel…
👍5❤1
Showing the 12 most recent of 22 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.
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 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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Clash-Party channel” (@MihomoPartyChannel), 14,903 subscribers as measured 6 September 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.