Telegram RegisterThe public register of Telegram
Telegram profile photo for Clash Verge AutoBuild Release

Channel

Clash Verge AutoBuild Release

@vergetest

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

3,597subscribers

+513 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002992211815
TypeChannel
Username@vergetest
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/vergetest

Growth

3,0843,5973,340.56 August 2026 — 3,084 subscribers6 August 2026 — 3,084 subscribers7 August 2026 — 3,109 subscribers10 August 2026 — 3,219 subscribers13 August 2026 — 3,286 subscribers16 August 2026 — 3,348 subscribers19 August 2026 — 3,406 subscribers23 August 2026 — 3,481 subscribers26 August 2026 — 3,534 subscribers29 August 2026 — 3,597 subscribers6 August 202629 August 2026
10 measurements spanning 22 days, net +513. 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 3,007–3,674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 04:443,597+63
26 Aug 2026, 02:443,534+53
23 Aug 2026, 08:463,481+75
19 Aug 2026, 15:413,406+58
16 Aug 2026, 19:343,348+62
13 Aug 2026, 13:063,286+67
10 Aug 2026, 16:033,219+110
7 Aug 2026, 17:553,109+25
6 Aug 2026, 22:453,084no change
6 Aug 2026, 22:393,084first reading

Engagement

20 posts held, back to 16 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
20.2%
avg views ÷ 3,597 subscribers
Avg views / post
728
5 posts measured
Reaction rate
0.166%
reactions ÷ views · ER floor
Posts in window
5
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. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (16 July 20266 August 2026)
Views total3,639
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:57 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

23 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 69.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1669.6%
👍626.1%
👏14.35%

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 12 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 23reactions 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 16 July 2026 to 6 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.

Recent posts

6 Aug 2026, 05:35 UTC647 viewsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0806.b138eb8 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

5 Aug 2026, 11:21 UTC673 views1 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0805.85eb393 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

1

5 Aug 2026, 05:34 UTC589 viewsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0805.85eb393 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

4 Aug 2026, 05:47 UTC738 views2 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0804.a8275b2 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

2

2 Aug 2026, 05:46 UTC992 views1 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0802.1599ca0 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

1

1 Aug 2026, 05:49 UTC957 views2 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0801.8ef6f0c 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

👍2

31 Jul 2026, 05:51 UTC938 viewsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0731.7d8f98e 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 修复 WebSocket 在 onConnected 初始化完成前被保存的问题,避免初始化失败后留下无监听且无法重试的无效连接。 修复 Mihomo API 变更后 inline proxy-provider 被错误过滤的问题,解决节点显示 Unknown 及延迟测试失败的问题 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际

30 Jul 2026, 11:10 UTC882 views1 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0730.5cbb0b6 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际地址与 TCP/UDP 协议检测且保留热重载 - 优化代理数据处理:统一通过单一 IPC 获取有序代理视图,并增强刷新、链路选择、重复判断及异常状态下的稳定性 - 新增 macOS 启动门禁,避免多用户环境下的实例冲突 - 加强 Service 多用户隔离与身份认证,支持安全的

1

30 Jul 2026, 05:31 UTC758 views2 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0730.5cbb0b6 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际地址与 TCP/UDP 协议检测且保留热重载 - 优化代理数据处理:统一通过单一 IPC 获取有序代理视图,并增强刷新、链路选择、重复判断及异常状态下的稳定性 - 新增 macOS 启动门禁,避免多用户环境下的实例冲突 - 加强 Service 多用户隔离与身份认证,支持安全的

1👍1

29 Jul 2026, 11:32 UTC820 views2 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0729.b98c9be 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际地址与 TCP/UDP 协议检测且保留热重载 - 优化代理数据处理:统一通过单一 IPC 获取有序代理视图,并增强刷新、链路选择、重复判断及异常状态下的稳定性 - 新增 macOS 启动门禁,避免多用户环境下的实例冲突 - 加强 Service 多用户隔离与身份认证,支持安全的

1👍1

29 Jul 2026, 05:35 UTC789 viewsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0729.98d7097 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际地址与 TCP/UDP 协议检测且保留热重载 - 优化代理数据处理:统一通过单一 IPC 获取有序代理视图,并增强刷新、链路选择、重复判断及异常状态下的稳定性 - 新增 macOS 启动门禁,避免多用户环境下的实例冲突 - 加强 Service 多用户隔离与身份认证,支持安全的

29 Jul 2026, 00:23 UTC883 views1 reactionsread 7 August 2026

🎉 Clash Verge Rev v2.5.3+autobuild.0729.3d8d773 滚动更新版发布 v2.5.3 🐞 修复问题 修复 macOS 多显示器切换时托盘速率样式不同步 ✨ 新增功能 - 新增混合代理端口冲突自动回退:启动时检测端口占用并持久化可用端口,同时统一首页、设置与系统代理中的生效端口显示 🚀 优化改进 - TUN 模式设置也遵循 原始配置 < Merge 覆写 < Script 脚本 < GUI - 优化监听端口冲突检测:代理端口按最终 Runtime 监听范围校验并协调三层持久化,隧道按实际地址与 TCP/UDP 协议检测且保留热重载 - 优化代理数据处理:统一通过单一 IPC 获取有序代理视图,并增强刷新、链路选择、重复判断及异常状态下的稳定性 - 新增 macOS 启动门禁,避免多用户环境下的实例冲突 - 加强 Service 多用户隔离与身份认证,支持安全的

1

Showing the 12 most recent of 20 posts we hold for @vergetest. 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 — 536,648 of 1,628,927entries 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“Clash Verge AutoBuild Release” (@vergetest), 3,597 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/vergetest.

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.