Telegram RegisterThe public register of Telegram

Channel

Clash爱好者

@clashios

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

14,049subscribers

+6 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-1001982865923
TypeChannel
Username@clashios
DescriptionClash 是最好滴🎉
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/clashios

Growth

14,04314,05114,0476 August 2026 — 14,043 subscribers7 August 2026 — 14,051 subscribers11 August 2026 — 14,045 subscribers12 August 2026 — 14,049 subscribers14,0496 August 202612 August 2026
4 measurements spanning 6 days, net +6. 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 14,042–14,052 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:1214,049+4
11 Aug 2026, 05:1414,045-6
7 Aug 2026, 03:3614,051+8
6 Aug 2026, 04:0714,043first reading

Engagement

18 posts held, back to 10 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 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 18 posts for this entry, the most recent from 6 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
8
Links
45

Lifetime counters from Telegram’s own channel header, read 12 August 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

429 reactions across 17 posts, in 19 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12328.7%
😭7517.5%
👍6916.1%
🤣4811.2%
😁399.09%
🌚194.43%
🥰122.80%
92.10%
🤔81.86%
🆒61.40%
🤬51.17%
🖕40.932%
30.699%
😈30.699%
🤩20.466%
👏10.233%
🔥10.233%
😢10.233%
🥴10.233%

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

Measured over the 18 most recent posts we hold, published 10 January 2025 to 6 June 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 Jun 2026, 06:18 UTC≈6,600 views8 reactionsread 12 August 2026
Forwarded from @sstrojanPoll

目前观察到通报力度有所加强,恶意DDOS事件不减,有国内入口的机场已经少之又少(一只手都能数得过来),“封端”貌似成为大环境所逼的必然趋势,现在的你是否支持你所在的机场采取“封端”措施?

  1. 支持全封端,我只想用稳定高速的线路23%
  2. 支持通用客户端用直连或海外中转线路,私有客户端用高级专线或者公网中转30%
  3. 不支持,懒得多下软件不如用直连53%

The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

8

19 Apr 2026, 06:38 UTC≈11,200 views10 reactionsread 12 August 2026

收集了一些采用 AnyTLS 新兴小众加密协议中转机场,持续更新补充中。 AnyTLS 是一款专为对抗 TLS-in-TLS 握手指纹设计的代理协议,通过灵活可配置的分包填充策略 + 连接复用,让流量特征更随机、更接近普通 HTTPS,大幅提升抗 DPI 能力。 https://clashios.com/anytls-jichang-recommend/

9🥰1

29 Mar 2026, 12:18 UTC≈18,400 views65 reactionsread 12 August 2026

从 2025 年下半年开始,中转/专线机场的入口封锁已经进入常态化阶段。(开启让机场叫苦不迭的大通报时代。) 随着检测自动化 + 运营商层级的执行体系落地,入口 IP 生命周期被大幅压缩。 👉 中转模式,正在快速失去可持续性。 目前来看,所有中转/专线机场,可选的路不多: 跑路退出:小体量服务商拿不到资源只能跑路离场 转 3C 线路:提高复杂度对抗,但成本高、波动大 转直连架构:放弃国内中转,走海外优化线路 封端模式:限制订阅分发,提高控制力(也就等同于 VPN了) 继续硬抗:头部厂商用资源换时间,但是否可持续依然成谜 本质分化只有三种: ❌ 放弃(跑路) ⚠️ 对抗(3C / 硬抗) ✅ 适应(直连 / 封闭生态) 📌 作为用户怎么办: 不要依赖单一中转厂商 优先选择“直连 + 多线路” 此时更不应该选择较长周期的套餐 中转机场短期内也不太可能完全消失,不乐观的情况是或许会有一波「跑路潮」,而剩下的中转机场

😭4615😈3🔥1

18 Mar 2026, 07:20 UTC≈10,800 views5 reactionsread 12 August 2026

收集了一些较为稀有的 VLESS 协议中转机场,持续更新补充中。 https://clashios.com/vless-reality-nodes/

5

17 Jan 2026, 02:14 UTC≈13,200 views8 reactionsread 12 August 2026
Forwarded from @jichangtj

当前通报封锁IP和污染情况严峻,正处于严打国内中转阶段。 若订阅“自焚”无法解决问题,仍然频繁通报机场可以从以下几个方向尝试应对(只是个人观察与猜测,不一定对): 1. 若认为人工拉取订阅后上交导致 可考虑采取“封端”策略。例如,目前有些机场从一开始就不提供订阅,仅允许使用专属客户端,反而从未被通报;也有部分在通报后封端,后续不再出现通报的情况。 影响: 无法使用Clash,小火箭等第三方客户端,部分用户可能会产生不满。 2.若认为协议层面问题 防火墙很可能将原本用于海外出口、识别直连协议(SS/SSR/Vmess/Trojan)的部署方案,直接用在国内环境(比如省墙)中。此类情况下,可尝试更换为当前直连环境下可用的协议,如 Reality 或 AnyTLS。感觉升级协议是迟早的事。 目前观察到,手上两家使用 AnyTLS 的节点尚未出现通报,也已有机场开始逐步切换到 Reality 协议。 影响: 协议相对较新,可能未优化

8

17 Dec 2025, 08:20 UTC≈13,400 views8 reactionsread 12 August 2026
Forwarded from @StashFeedPhoto

🎯 IPPure Collapsed Tiles:在首页面板展示你的 IP 纯净度 🧪 主要功能: 风险系数评分:判断 IP 是否易被识别为代理、异常流量或高风险来源。 原生 IP / 非原生 IP(Announced IP)识别:区分真实本地网络 vs 从其他国家“广播”宣告的跨区域 IP。 住宅 IP(Residential) vs 机房 IP(Data Center)识别:自动识别当前 IP 是否来自家庭宽带或 IDC/云厂商。 🛠 使用方式: 首页:点击 「第三方服务」 → 即可查看当前 默认出口 IP 的完整信息。 策略组 / 节点列表:长按代理 → 选择 「代理信息」 → 切换到 「第三方服务」 → 查看该代理节点的 出口 IP 信息。 ▎点击此处安装覆写

8

10 Dec 2025, 16:19 UTC≈11,200 views21 reactionsread 12 August 2026
Forwarded from @jichangtj

最近几天情况更加严重了,各个机场群里不断出现“炸了”的消息。不少机场开始采取措施:订阅链接会自焚,或者在几分钟后自动失效。只要已经拉取到节点,使用上不会受影响,但无法用同一个订阅链接更新节点。平时影响不大,但目前仍存在域名污染问题,一旦遇到域名污染,只能重新从官网导入订阅。如果官网恰好需要翻墙访问,就无法拉取最新订阅,容易形成死循环。还有机场直接封端:只允许使用其站点定制客户端,暂时不开放订阅。 这些措施未必能完全解决问题,但对于通报严重的机场,如果不做任何调整,每天必然会出现节点不可用,直到无可用 IP。 中转机场严打时刻,对于需要高强度翻墙的用户,建议同时购买多个机场,轮换使用。

👍9822

6 Nov 2025, 10:58 UTC≈14,300 viewsread 12 August 2026
Forwarded from @LoonNews

近期多人反馈遇到了假的Loon官方网站,这里特别说明下,Loon目前唯二的官网只有下面这两个,其他的网站都不是官方网站,大家谨防上当受骗。 nsloon.app nsloon.com

9 Oct 2025, 05:54 UTC≈16,900 views18 reactionsread 12 August 2026
Forwarded from @haitun_channelFile

《参数汇总:代理工具的协议支持 & Apps与通用核心的隶属》 如两张图所示 VLESS 家族过于庞大,仅节选机场节点常用的特性/分支。 待有统计数据后,会再补充一些信息…… To be announced…… 网页版地址: https://www.haitunt.org/cheatsheet.html ⚠️ 这不是一份测评,而是纯粹的协议参数汇总表 #app #协议 #代理工具 #代理核心 #代理协议 #mihomo #singbox #xray #v2ray #v2fly #dae #大鹅 #surge #小火箭 #loon #stash #qx #surfboard #vless #reality #encryption #hy2 #anytls #windows #win #macos #linux #openwrt #路由器 #华硕 #小米 #软路由 #插件 #内网穿透 #参数 #速查手册 #cheatshe

15👍3

17 Sept 2025, 12:48 UTC≈14,800 views10 reactionsread 12 August 2026
Forwarded from @gaojiriji

[General] use-local-host-item-for-proxy = true [Host] 91.108.56.100 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.101 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.104 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.107 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.120 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.125 = 91.108.56.147,91.108.56.135,91.108.56.130 91.108.56.126 = 9

😁43🆒2👍1

24 Aug 2025, 04:25 UTC≈16,100 views15 reactionsread 12 August 2026
Forwarded from @egern_news

自 2.6.0 起,Egern 将由付费下载调整为免费 + 付费解锁高级功能模式。已购买的用户权益不变可继续使用全部功能。 免费功能:代理相关能力、MITM、HTTP 抓包。 高级功能(付费):模块、DNS 流量控制、脚本、重写、Map Local。

🥰7🤬5🌚21

16 Aug 2025, 05:46 UTC≈17,400 views26 reactionsread 12 August 2026

GLaDOS Basic Plan 30天兑换码: 6OCL1-46C4B-D3CTL-M98FU UIXTE-XYEQ0-KSB1P-OEW84 TCBN1-0W715-HFPRA-M6QDS N4QZX-6ZRRN-5Z5SU-PDH0I MMJMO-S84TS-TQZ9I-PL06Y R2VQZ-BKC8C-ZV97A-L8WDU P1U5C-I1OLB-TSULQ-U3ZUM 兑换地址:https://clashios.com/glados 全部已使用,over.

🤣13121

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

6 Jun 2026, 06:18 UTCAnonymous Poll1,420 voters approx.

目前观察到通报力度有所加强,恶意DDOS事件不减,有国内入口的机场已经少之又少(一只手都能数得过来),“封端”貌似成为大环境所逼的必然趋势,现在的你是否支持你所在的机场采取“封端”措施?

  1. 支持全封端,我只想用稳定高速的线路23%
  2. 支持通用客户端用直连或海外中转线路,私有客户端用高级专线或者公网中转30%
  3. 不支持,懒得多下软件不如用直连53%

The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 10 January 2025 to 6 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 979,610 of 1,151,006entries 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.

Forward network

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

“Clash爱好者” (@clashios), 14,049 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/clashios.

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.