Release v3.5.41· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 fix(脚本): 修复 Hysteria2 端口跳跃、订阅配置及 Geo 更新问题 1️⃣ 脚本异常处理 2️⃣ 脚本使用注意事项 3️⃣ 低价联通AS4837年付10美 4️⃣ 搭建最新的VLESS Vision和VLESS Reality防止VPS端口封禁 5️⃣ 八合一脚本入门到精通 6️⃣ VPS选购攻略,避坑指南 7️⃣ 自定义证书教程 8️⃣ VPS哪吒探针 新版Socks5分流教程。

Channel
技术小木屋 channel
@v2rayAgentChannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
9,701subscribers
+363 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001457926576 |
|---|---|
| Type | Channel |
| Username | @v2rayAgentChannel |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/v2rayAgentChannel |
Topic
Ecommerce storefront — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 17:51 | 9,701 | +4 |
| 7 Nov 2026, 20:41 | 9,697 | +10 |
| 5 Nov 2026, 00:38 | 9,687 | +11 |
| 2 Nov 2026, 01:36 | 9,676 | +76 |
| 29 Oct 2026, 18:39 | 9,600 | +30 |
| 26 Oct 2026, 08:55 | 9,570 | +1 |
| 22 Oct 2026, 22:48 | 9,569 | +10 |
| 20 Oct 2026, 01:10 | 9,559 | +8 |
| 17 Oct 2026, 07:06 | 9,551 | +16 |
| 14 Oct 2026, 17:20 | 9,535 | +12 |
| 11 Oct 2026, 02:57 | 9,523 | +23 |
| 4 Oct 2026, 21:56 | 9,500 | +59 |
| 25 Sept 2026, 08:37 | 9,441 | +52 |
| 15 Sept 2026, 15:18 | 9,389 | -2 |
| 11 Sept 2026, 18:20 | 9,391 | +12 |
| 7 Sept 2026, 08:38 | 9,379 | -3 |
| 2 Sept 2026, 19:38 | 9,382 | +14 |
| 30 Aug 2026, 08:05 | 9,368 | +4 |
| 26 Aug 2026, 23:07 | 9,364 | -8 |
| 23 Aug 2026, 19:24 | 9,372 | first reading |
Engagement
38 posts held, back to 5 June 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 50 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 28.0%
- avg views ÷ 9,701 subscribers
- Avg views / post
- 2,720
- 10 posts measured
- Reaction rate
- 0.122%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 38 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 7 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 38 (5 June 2026 – 9 November 2026) |
| Views total | 27,200 |
| Reactions total | 23 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 11:19 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
136 reactions across 27 posts, in 8 distinct kinds. The most used accounts for 58.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 80 | 58.8% | |
| ❤ | 39 | 28.7% | |
| 💊 | 5 | 3.68% | |
| 😴 | 4 | 2.94% | |
| 🔥 | 3 | 2.21% | |
| 🙊 | 2 | 1.47% | |
| 🤯 | 2 | 1.47% | |
| 🤩 | 1 | 0.735% |
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 27 of the 38 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 136 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 5 June 2026 to 9 November 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 10 posts 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).
Release v3.5.40· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 fix(xray): 修复 Xray 安装 Hysteria2 无法查看账号 fix(脚本):修复 Hysteria2 订阅缺少上下行速率 1️⃣ 脚本异常处理 2️⃣ 脚本使用注意事项 3️⃣ 低价联通AS4837年付10美 4️⃣ 搭建最新的VLESS Vision和VLESS Reality防止VPS端口封禁 5️⃣ 八合一脚本入门到精通 6️⃣ VPS选购攻略,避坑指南 7️⃣ 自定义证书教程 8️⃣ VPS哪吒探针 新版Socks5分流教程。
❤1👍1
Release v3.5.39· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 docs(socks5): 新增入站与出站分流教程并优化交互排版 - 新增 SOCKS5 入站搭建、出站连接、分流规则及连通性测试教程 - 补充教程配图、交互记录和截图生成工具 - README 增加 SOCKS5 简明教程入口 - 调整中英文入站安装提示间距 - 优化出站菜单、节点录入及入站和用户选择的展示间距 新版Socks5分流教程。
👍2
Release v3.5.38· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 feat: 增强 SOCKS5 用户分流并统一订阅展示 - 支持按入站及认证用户配置 SOCKS5 分流 - 支持落地节点默认用户选择、规则继承及编辑保留 - 增加失效用户引用校验和账号删除保护 - 优化 SOCKS5 节点、规则管理及入站配置展示 - 完善配置事务、核心重启和失败回滚处理 - 统一 Xray 与 sing-box 服务清理,失败时中止卸载或切换 - 自定义 Xray 安装时清理未选协议配置 - 合并查看订阅与生成订阅后的展示逻辑 - 恢复重复查看订阅时的二维码输出,确保二维码使用纯链接 - 优化订阅配色、信息层次及标签与链接间距 - 未初始化订阅服务时自动进入生成流程 - 修复单独安装Tuic判断问题 1️⃣ 脚本异常处理 2️⃣ 脚本使用注意事项 3️⃣ 低价联通AS4837年付10美 4️⃣ 搭…
❤2
Release v3.5.37· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 fix(xray): 修复 Xray 自定义安装 Hysteria2 二次启动报错 fix(xray): 修复首次安装配置写入错误目录 1️⃣ 脚本异常处理 2️⃣ 脚本使用注意事项 3️⃣ 低价联通AS4837年付10美 4️⃣ 搭建最新的VLESS Vision和VLESS Reality防止VPS端口封禁 5️⃣ 八合一脚本入门到精通 6️⃣ VPS选购攻略,避坑指南 7️⃣ 自定义证书教程 8️⃣ VPS哪吒探针 #套餐推荐 RackNerd 2026最新套餐 https://t.me/v2rayAgentChannel/2047 DMIT Premium Pro【优质三网GIA】 https://t.me/v2rayAgentChannel/2041 搬瓦工商务套餐 https://t.me/v2ra…
👍3
Release v3.5.35· mack-a/v2ray-agent 已开通X,欢迎关注 #更新日志 现在对新版xray-core做出了兼容更改。需要重新生成订阅信息。 xray-core(v2rayNG、v2rayN) 客户端和服务端需要升级到最新版本。 mihomo升级最新版本后重新拉取服务单最新的订阅。 服务端是sing-box的不受此次更新影响,可以正常使用。 小火煎升级最新版本后,打开Reality节点->TLS->指纹->选择Chrome120或者选择支持X25519MLKEM768的指纹即可。 fix(xhttp): 修正 REALITY 与 TLS 的 CDN 支持描述 fix(reality): 完善 Mihomo ML-KEM 配置及 pqv 导出规则 1️⃣ 脚本异常处理 2️⃣ 脚本使用注意事项 3️⃣ 低价联通AS4837年付10美 4️⃣ 搭建最新的VLESS Vision和VLE…
👍7❤2
最近升级xray-core后无法使用的,可以回退到上一个正式版本。
CloudCone 活动款,洛杉矶DC1。推荐用于备用或者非高峰期下载视频游戏等大流量场景。 Year-End-25-VPS-1 1 x vCPU 1GB RAM 50GB SSD 1TB流量 1x IPv4和3x IPv6 数据中心:美国洛杉矶DC1 $9.99/Year https://app.cloudcone.com/vps/498/create?ref=6758&token=year-end-25-vps-1 Year-End-25-VPS-2 2 x vCPU 2GB RAM 100GB SSD 2TB流量 1x IPv4和3x IPv6 数据中心:美国洛杉矶DC1 $14.49/Year https://app.cloudcone.com/vps/499/create?ref=6758&token=year-end-25-vps-2
❤1
ZgoCloud补货洛杉矶9929+CMIN2优化线路机型,上游kurun,带宽300Mbps,原生IP 支持3天内流量不超过10G可工单退款 电信,联通走9929,移动走CMIN2 1 Core AMD EPYC 7003 Series or Intel(R) Xeon(R) Gold 2 GB DDR4 RAM 30G NVMe SSD 1 IPV4 1T/Month/300Mbps 购买:https://clients.zgovps.com/?cmd=cart&action=add&affid=1584&id=66 2 Cores AMD EPYC 7003 Series or Intel(R) Xeon(R) Gold 3 GB DDR4 RAM 50G NVMe SSD 1 IPV4 2T/Month/300Mbps 购买:https://clients.zgovps.com/?cmd=cart&action=…
❤2👍2
大佬们,有没有稳定的Opus5.5渠道。
最近有什么新技术和新玩法吗?(沉迷Ai中
❤1
现在有靠谱的家宽IP厂商推荐吗?
Showing the 12 most recent of 38 posts we hold for @v2rayAgentChannel. 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.
Posts recorded as deleted after publishing
We recorded 4 posts on @v2rayAgentChannel as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 20 August 2026
- Most recent seen missing
- 22 August 2026
- Median time before seen missing
- 4 days
- Seen missing in the last 30 days
- 0
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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
Names
Channels on the register whose handles appear in this channel's posts.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@moviepilot_channel · 19,991
Telegram ranks this channel #22 of 40 here — alongside 39 others — read 30 September 2026
@AI_News_CN · 23,317
Telegram ranks this channel #43 of 45 here — alongside 44 others — read 22 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“技术小木屋 channel” (@v2rayAgentChannel), 9,701 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/v2rayAgentChannel.
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.