Telegram RegisterThe public register of Telegram
Telegram profile photo for ShellCrash发布

Channel

ShellCrash发布

@ShellClash

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

17,648subscribers

+26 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001470834583
TypeChannel
Username@ShellClash
Description支持各类Linux/OpenWrt环境下一键部署
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/ShellClash

Growth

17,62217,64817,6357 August 2026 — 17,622 subscribers7 August 2026 — 17,622 subscribers8 August 2026 — 17,624 subscribers9 August 2026 — 17,629 subscribers11 August 2026 — 17,636 subscribers12 August 2026 — 17,637 subscribers13 August 2026 — 17,641 subscribers14 August 2026 — 17,648 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +26. 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 17,618–17,652 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 21:5517,648+7
13 Aug 2026, 09:4617,641+4
12 Aug 2026, 10:2417,637+1
11 Aug 2026, 09:2317,636+7
9 Aug 2026, 07:1217,629+5
8 Aug 2026, 09:0117,624+2
7 Aug 2026, 13:0017,622no change
7 Aug 2026, 12:4817,622first reading

Engagement

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

ERR · 30 days
39.1%
avg views ÷ 17,648 subscribers
Avg views / post
6,900
1 post measured
Reaction rate
0.667%
reactions ÷ views · ER floor
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 July 2026
Posts held20 (17 January 202318 July 2026)
Views total6,900
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:40 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.

What this channel posts

Photos
1
Links
42

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

1,087 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 95.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,03995.6%
242.21%
🔥70.644%
👏40.368%
🥰40.368%
🍾30.276%
🎉30.276%
🫡20.184%
😁10.092%

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 19 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 1,087reactions 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 17 January 2023 to 18 July 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

18 Jul 2026, 12:24 UTC≈6,900 views46 reactionsread 15 August 2026

v1.9.5beta3 公测版 ——————————— b3: ~所有本地配置模板统一新增interval: 120字段,以优化检查逻辑 ~增加UI选项的翻译文本 ~优化新手引导中启用IP转发的提示及实现逻辑 ~修复下载自定义数据库时无法输入超过9的数字的bug b2: ~修复热更新配置失败的bug ~现在修改劫持范围时不再重置代理模式 ~优化清理数据库提示并增加对.metadb文件的清理 ~增加对ss命令的兼容以替代netstat命令 ~现在对未启用IP转发的设备,启动局域网代理时默认会检查并启用IP转发 b1: ~修复Tailscale因为内网网段缺少后缀导致的异常问题 ~修复dns端口修改时缺失的报错提示 ~修复部分语法错误 a1-a15:https://t.me/ShellClash/228 ——————————— 进群讨论: https://t.me/+6AElkMDzwPxmMmM1 项目地址: https://gi

👍46

15 Feb 2026, 11:46 UTC≈26,100 views99 reactionsread 15 August 2026

v1.9.4稳定版-祝大家马年春节快乐!阖家团圆,马到成功! ——————————— 🌟 新增功能 新增访问与控制菜单: ~新增tg控制机器人,支持管理内核服务、查看日志、下载上传配置文件、备份还原脚本设置、上传内核等功能 ~新增自定义公网vmess及ss入站功能,支持一键生成秘钥,一键生成分享链接 ~新增自定义内网穿透功能,支持快速配置Tailscale/Wireguard内网穿透服务 增加upx压缩版内核和内核版本分支选择菜单,现在支持精简版、标准版和开发版三个版本mihomo及singboxr内核下载 增加单独指定dns劫持端口的功能(用于搭配第三方DNS服务) 增加ecs优化功能 增加自启检测,修复反复自启导致死机循环的bug ⚡️ 优化改进 优化了大量界面层级及内容,将原有的局域网过滤、quic过滤等功能整合到2-3流量过滤菜单 优化为统一使用ON/OFF来表示功能开启关闭状态 全面重构代码,优化代码结构,优化脚本运

👍99

4 Feb 2026, 11:53 UTC≈20,100 views19 reactionsread 15 August 2026

v1.9.5alpha15开发版 ——————————— a15: ~适配singbox1.14+版本内核 ~增加梅林固件启动时优化系统默认内存检测机制 ~将fakeip地址从28.0.0.0/8调整为198.18.0.0/15 合并PR: https://github.com/juewuy/ShellCrash/pull/1271 https://github.com/juewuy/ShellCrash/pull/1272 https://github.com/juewuy/ShellCrash/pull/1284 https://github.com/juewuy/ShellCrash/pull/1293 https://github.com/juewuy/ShellCrash/pull/1301 https://github.com/juewuy/ShellCrash/pull/1302 https://github.co

👍19

8 Jan 2026, 02:17 UTC≈18,400 views12 reactionsread 15 August 2026

v1.9.4rc7.1稳定预览版 ——————————— r7: ~修复Mihomo内核自动检测下载geoip和geosite数据库功能未工作的bug ~修复TG-BOT因守护进程错乱导致的各种bug ~自定义内核链接支持.upx结尾内核文件 ~增加每次启动tg_bot服务时自动推送菜单的开关 r6: ~优化定时任务 ~修复docker相关bug ~修复ddns工具的一些bug ~修复保守模式部分情况下反复重启的bug ~其他bug修复 r5: ~修复因.start_error失败标记导致的部分bug by juewuy ~继续优化定时任务功能 by juewuy ~修复部分情况下自启状态显示不正确的bug by juewuy ~优化容器部署说明,修复持久化问题 by juewuy ~bug fix r4.1: ~重写 set_cron.sh 尝试修复因为定时任务导致系统crontab内容丢失的问题 ~现在跳过证书验证开关对内置

👍12

1 Jan 2026, 02:10 UTC≈14,500 views64 reactionsread 15 August 2026

v1.9.3稳定版-祝大家2026新年快乐! ——————————— 🌟 新增功能 容器化深度支持: 全面适配容器运行环境,支持 S6 守护进程及 Docker Compose 部署,实现首次启动自动设置自启。 https://hub.docker.com/r/juewuy/shellcrash 全新 DNS 模式: 新增 route 模式 DNS,并优化其在 Mihomo 内核下的数据库自动更新机制。 面板与交互: 新增 Zashboard、MetaXD 面板支持;Mihomo 本地模版支持手动选择节点(感谢 @DustinWin)。 自动化增强: 增加设置别名时的系统冲突校验,支持定时任务自动更新规则集(Rule-set/MRS/SRS)。 ⚡️ 优化改进 DNS 逻辑优化: 优化加密 DNS 实现,Mihomo 和 Sing-box 内核不再依赖系统根证书文件。 优化防泄露逻辑,改进 Mix 模式下的国内域名访问速度。

👍64

26 Dec 2025, 13:01 UTC≈12,600 views28 reactionsread 15 August 2026

v1.9.4alpha8开发版 ——————————— 祝大家2026新年快乐! ——————————— a8: ~增加ecs优化功能 ~重写常用端口过滤功能 ~增加单独指定dns劫持端口的功能(用于搭配第三方DNS服务) ~改为统一使用ON/OFF来表示功能开启关闭状态 a7.3: ~优化屏蔽quic实现机制,修复bug ~优化ddns脚本 ~检查更新流程优化 ~padavan自启优化 ~部分界面文本优化 ~bug fix a7: ~开发版meta和singboxr内核移动到内部下载 ~找回被误删的防止dnsmasq重定向功能 ~增加upx压缩版内核和内核版本分支选择菜单,现在支持精简版、标准版和开发版三个版本mihomo及singboxr内核下载 ~调整Tailscale的缓存目录为安装目录,增加设备名称设置选项 ~修复部分设备开机初始化失败的bug ~修复auto_start.sh脚本调用失败 ~修复zsh环境安装报错 ~

👍28

14 Dec 2025, 10:56 UTC≈12,300 views40 reactionsread 15 August 2026

v1.9.3pre4稳定预览版 ——————————— ~本项目官方容器镜像已发布: https://hub.docker.com/r/juewuy/shellcrash ~之前有使用了360dns的同学请重置dns设置,Singbox内核使用360dns可能会因为限速导致明显的卡顿乃至死机~ ——————————— p4: ~修复DNS在route模式下不会自动更新cn.mrs/srs数据库的bug p3: ~修复安装脚本报错 ~优化初始化脚本的环境变量注入逻辑 ~优化version读取 ~修复route模式dns下Mihomo内核不会自动生成ruleset文件的bug p2: ~添加docker compose支持 ~移除错误的fakeip过滤地址 ~修复导入包含&符号的订阅链接时,生成配置文件出错的bug ~修复镜像化设备自定义别名重启后失效的bug ~优化低内存设备更新内核时的/tmp占用 ~Mihomo本地生成模版新增

👍40

6 Dec 2025, 12:16 UTC≈12,700 views42 reactionsread 15 August 2026

v1.9.3beta6公测版 ——————————— b6: ~新增安装时自定义别名功能 ~小米自动开机清理功能适配更多设备 ~将项目内置Geosite.dat数据库替换为Mihomo官方数据库以修复报错 ~暂时移除了由于项目内文件夹路径变动导致不可用的wwng2333下载源 ~集中修复了一些Singbox相关内核的启动报错,并增加提示信息 ~修复部分设备自动更新Mihomo内核失败的bug b5: ~增加新的 DNS 模式:route 模式 ~增加小米设备升级后自动清理备份文件夹及开机自动禁止日志写入闪存功能 ~优化自动任务功能,屏蔽低于 60 分钟任务的远程日志推送,并增加容错 ~public 目录文件在线更新改为从 dev 分支获取 ~优化本地生产配置文件功能,增加容错并禁止纯数字名称 ~优化端口设置界面显示 ~优化 Mihomo 内核 mix 模式逻辑,提升国内域名访问速度 ~优化 setconfig 函数,提升系统兼容

👍42

2 Dec 2025, 07:20 UTC≈14,200 views48 reactionsread 15 August 2026

v1.9.3alpha7开发版 ——————————— a7: ~优化默认dns服务器 ~优化DNS逻辑 ~自定义内核功能增加最近更新时间显示 ~singbox内核增加自动设置缺省GLOBAL组功能,以适配更多配置文件提供者 ~singbox内核增加自动设置proxy-DNS出口节点功能,以防止DNS泄露 ~修复因为设置面板密码导致启动缓慢的bug ~修复谷歌商店转圈bug a6: ~增加公共版tg推送机器人 ~将ruleset规则链接改为cdn链接 ~修复clash内核启动报错 ~优化源地址 ~修复局域网设备IP过滤时的显示错误 ~修复部分情况下启动超时后报错不正确的bug ~移除了部分已经不支持的内核版本信息 a5: ~修复小闪存模式内核会被重复下载的bug ~修复小闪存模式部分设备无法启用的bug ~修复部分设备Tproxy失效的bug a4: ~mihomo内核dns优化,移除无用的fallback组,default_n

👍48

8 Mar 2025, 07:18 UTC≈57,000 views99 reactionsread 15 August 2026

v1.9.2beta7公测版 ——————————— b7: ~修复部分订阅配置用6-2获取失败的问题 ~修复mix模式与自定义配置文件冲突的bug ~修复自定义数据库文件功能部分数据库失效的bug ~默认更新服务器改成cloudflare源 ~修复部分设备本地更新内核和配置文件报错的bug ~将默认路由表改成166避免冲突 ~优化6-x菜单返回 ~暂时屏蔽singbox相关内核 b6: ~优化自定义ua功能 ~修复6-1部分bug ~修复因为空格未对其导致的mihomo内核mix模式报错的bug 合并pr: ~使用 sing-box check 的返回值来判断配置文件是否正确 by MoonFruit ~设置变量时完整匹配变量名称 by MoonFruit ~变更 tun 工作地址 by MoonFruit b5: ~优化华硕官方固件安装时的U盘目录选择列表 ~优化6-2和6-3的文字提示及界面逻辑 ~新增自定义浏览器UA功能

👍99

19 Jan 2025, 09:18 UTC≈45,100 views61 reactionsread 15 August 2026

v1.9.2alpha9开发版 ——————————— a9: ~修改上游srs数据库地址 ~禁止安装到tmp|opt|sys等目录 a8: ~优化内核名称显示 ~自定义规则列表增加进程名匹配,meta内核增加进程匹配自动开关机制 ~修复meta内核mix模式GooglePlay下载失败的问题 ~修复一些无意义的报错提示 a7: ~添加LOL语音相关域名 ~优化了nftables处理流程 ~优化了自动下载数据库功能,现在会自动识别配置文件中是否存在相关链接,如是则不触发 ~优化新手引导默认参数,现在默认启用绕过cnip功能,非mips设备默认启用混合模式 ~新手引导选择局域网设备时,增加了net.bridge.bridge-nf-call-iptables禁用,以修复部分设备因docker冲突而导致代理异常的问题 ~将cn_ip与cn_ipv6文件默认包含到安装包中 ——————————— 进群讨论: https://t.me/

👍61

12 Jan 2025, 08:49 UTC≈32,700 views75 reactionsread 15 August 2026

颈椎病犯了,这周没有更新了😭

👍75

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

21 May 2023, 07:40 UTCFinal Results1,010 voters approx.

新冠小调查

  1. 一直金身未破17%
  2. 去年🐑了,今年没🐑61%
  3. 去年没🐑,今年🐑了7%
  4. 王重🐑12%
  5. 三🐑开泰3%

Shares as published. No per-option vote count is published by Telegram, so none is 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 20 most recent posts we hold, published 17 January 2023 to 18 July 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 — 854,544 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.

Mentions

Named by 3 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.

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

“ShellCrash发布” (@ShellClash), 17,648 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ShellClash.

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.