Channel
@subconverter
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,955subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001377163749 |
|---|---|
| Type | Channel |
| Username | @subconverter |
| Created | Between 1 March 2018 and 5 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/subconverter |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:57 | 1,955 | -3 |
| 10 Aug 2026, 14:51 | 1,958 | -3 |
| 7 Aug 2026, 17:13 | 1,961 | -1 |
| 7 Aug 2026, 11:17 | 1,962 | no change |
| 7 Aug 2026, 11:07 | 1,962 | first reading |
20 posts held, back to 5 April 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 20 posts for this entry, the most recent from 8 April 2024. An engagement rate over an empty window would be a number about nothing.
81 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 65.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 53 | 65.4% | |
| 🥰 | 18 | 22.2% | |
| ❤ | 5 | 6.17% | |
| 😁 | 4 | 4.94% | |
| 🔥 | 1 | 1.23% |
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 5 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 81reactions 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 5 April 2020 to 8 April 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
SubConverter v0.9.0 该版本支持了 Clash, Surge 和 Loon 配置文件中的 WireGuard 节点，以及生成 sing-box 格式的配置文件。macOS ARM 构建也已添加。 增加的功能： * 增加 Clash, Surge 和 Loon 配置文件对 WireGuard 节点的支持 * 增加生成 sing-box 配置和导出节点列表为 sing-box 格式的支持 * 增加选项以在请求时启用重新加载配置 * 增加解析 SOCKS5 链接中的认证信息的支持 (#652) * 增加 Shadowsocks-2022 加密方式 (#564) * 如果存在 no-resolve，则在生成 Clash 规则集时添加 no-resolve (#679) * 增加 Clash 配置文件中代理组的输出样式设置 (#734) * 增加 macOS ARM 构建 修复的问题： * 修复转换尼日利亚节点时的国…
👍46🥰5❤3😁3🔥1
SubConverter v0.8.1 该版本将依赖的 libcurl 网络库更新到 8.4.0，以修补该库的一些较重大的漏洞。 Release 下载 请我喝咖啡
🥰13👍6❤2
SubConverter v0.8.0 该版本修正了一个可能导致远程代码执行的漏洞，建议所有用户升级。 更新日志： * 增加运行脚本前的鉴权 并删除部份未使用的接口 * 增加详细的配置文件加载 log * 修复下载订阅时发送了错误的 header 的问题 * 修复了 Surge 的 load-balance 策略组生成错误的问题 * 增加 Surge 策略组的 persistent 和 evaluate-before-use 参数 * 增加 Quantumult X 和 Loon 配置中 SOCKS5 节点和部份新策略组参数的支持 * 修复 sub 接口不能正常接受 HEAD 请求的问题 * 修复不能正常加载本地规则集的问题 * 修复 Quantumult X 配置中 aead 选项添加的问题 * 修复了生成 Loon 配置时的一些问题 * 增加支持 v2rayN 等使用的 trojan 链接格式 * 调整生成的 Clash …
SubConverter v0.7.2 更新日志: * 更正默认配置中的错误 * 修复未设置 template 路径时的报错 * 修复添加 SSID 策略组到 Loon 配置时崩溃的问题 * 修复解析部分 ShadowsocksR 配置中的问题 * 修复 cache 系统不能正常工作的问题 * 修复生成 Quantumult X 配置的部分问题 * 修复 max_allowed_download_size 选项无效的问题 * 修复 skip-cert-verify 参数未被正确添加到 Surge 配置中的问题 * 修复 Group ID 匹配的 not 范围无效的问题 * 修复 HTTPS 节点的解析生成中的问题 * 修复 ini 策略组配置中 tolerance 与 timeout 反转的问题 * 修复对部分 Shadowrocket 以及 Trojan 链接的解析 * 增加 Quantumult X 策略组配置中 url-…
https://subcon.dlj.tf => https://sub.xeton.dev
SubConverter v0.7.1 已恢复 ARM 平台版本构建 更新日志: * 修复当已设置 surge_rule_base 时 外部配置 TOML 文件加载失败的问题 * 修复默认配置中的错误 * 修复转换的部分 VMess 节点设置缺失的问题 * 回退到旧版本 Clash VMess-WS 节点格式 以支持大部分客户端 * 更新本地规则 Release 下载 请我喝咖啡
SubConverter v0.7.0 增加使用 TOML 作为配置文件格式的支持，允许更整洁的配置文件以及更多的设置可选项 更新日志: * 修复未正确处理 Clash 订阅中 SOCKS5 节点信息的问题 * 修复某些全局选项无效的问题 * 修复对循环请求的识别 * 修复 SSD 订阅中对默认节点参数的处理 * 修复解析部分 Clash rule-providers 时出现的问题 * 修复未处理 Surge Ruleset 行内注释的问题 * 修复有时会生成损坏的 Clash 订阅的问题 * 修复 Clash 订阅中 alterId 处理的错误 * 修复解析 ShadowsocksR 订阅中的问题 * 修复运行 script 时可能导致的崩溃 * 修复某些时候生成 SIP008 及 SSD 订阅的 server_port 为 0 的问题 * 修复使用 auto 作为 target 时 解析到的实际 target 参数未传入…
SubConverter v0.6.4 更新日志: * 修复 auto 自动客户端判断类型不能正常工作的问题 * 修复在转换部分 SSR 订阅至 SSD 订阅时 程序崩溃的问题 * 修复对 Surge 逻辑规则的判断 * 修复输出 Quantumult 配置时部分节点参数位置错误的问题 * 增加对标准 VMess 链接的支持 * 增加简易文件服务器支持 * 增加输出 PROCESS-NAME 规则至 Clash 配置中 * 增加脚本中使用 fetch 发起 POST 请求的支持 * 增加 /flushcache 用于清理所有本地缓存 * 增加设置输出 VMess 订阅时节点 type 的默认值 * 增加在输出不含规则的简单订阅时 略过分组规则的加载 * 更新 Loon 客户端的判断规则 * 更新本地规则仓库 并移除 ConnersHua 仓库 仅保留 DivineEngine 新仓库 * 优化代码 Release 下载 …
SubConverter v0.6.3 更新日志: * 修复对部分非标准订阅的解析问题 * 修复未解析 Trojan 链接中的 group 选项的问题 * 修复未解析 Clash 订阅中的 ShadowsocksR 节点的问题 * 修复当使用 nullnode 作为原订阅时可能出现的崩溃问题 * 修复与 Electron-SSR 配置的兼容问题 * 修复错误的下载大小限制导致的无法下载订阅 配置或规则集 * 修复 /updateconf 导致配置文件清空的问题 * 增加直接转发请求 User-Agent 用于获取订阅 * 增加修改下载文件大小限制的支持 * 增加将只含有 DIRECT / REJECT / REJECT-TINYGIF 的分组转换为 Surge 配置的 Proxy * 增加选项以修改 Clash 配置中 proxies 部分的排版方法 * 增加为 Clash 订阅输出 profile-update-interv…
现在都能满足了
🔨 1 new commit to subconverter:master: f671230: Add option to change style of proxies section in Clash subscriptions by Tindy X
SubConverter v0.6.2 更新日志: * 修复使用 Clash rule-provider 作为规则来源时的问题 * 修复 rename / 添加 Emoji 处的脚本支持 * 修复部分非标准 v2rayN 订阅的解析问题 * 修复生成 Clash Script 时的逻辑错误 * 增加在为 Surge 生成 ShadowsocksR 订阅时是否解析节点域名的选项 * 增加对 Shadowsocks simple-obfs 插件的多个名称的支持 * 增加 auto target 可自动通过客户端 User-Agent 判断客户端类型版本 * 增加获取或解析链接错误时跳过该链接的选项 * 增加对 Surge RULE-SET 的 update-interval 选项的支持 * 增加向 Clash 订阅中输出 ShadowsocksR 节点的支持 * 增加同时向 Clash 策略组中添加节点和 proxy-provid…
👍1
Showing the 12 most recent of 20 posts we hold for @subconverter. 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 — 678,121 of 1,481,217entries 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.
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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“SubConverter 更新频道” (@subconverter), 1,955 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/subconverter.
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.