Telegram RegisterThe public register of Telegram

Channel

Cool Scripts

@cool_scripts

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

16,227subscribers

-1 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-1001240656267
TypeChannel
Username@cool_scripts
DescriptionQuanX, Loon, Surge, JsBox, Pythonista, Scriptable, Shortcuts等脚本分享
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/cool_scripts

Growth

16,22716,23416,230.56 August 2026 — 16,228 subscribers7 August 2026 — 16,232 subscribers8 August 2026 — 16,234 subscribers9 August 2026 — 16,230 subscribers11 August 2026 — 16,229 subscribers12 August 2026 — 16,227 subscribers6 August 202612 August 2026
6 measurements spanning 6 days, net -1. 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 16,226–16,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:0316,227-2
11 Aug 2026, 17:3716,229-1
9 Aug 2026, 20:3216,230-4
8 Aug 2026, 17:4716,234+2
7 Aug 2026, 18:2416,232+4
6 Aug 2026, 21:0116,228first reading

Engagement

24 posts held, back to 13 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.79%
avg views ÷ 16,227 subscribers
Avg views / post
1,430
23 posts measured
Reaction rate
0.154%
reactions ÷ views · ER floor
Posts in window
23
of 24 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 9 of 23 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 11 August 2026
Posts held24 (13 July 202611 August 2026)
Views total32,789
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 01:02 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
446
Videos
31
Links
807

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

22 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1463.6%
👍731.8%
🥰14.55%

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

Measured over the 24 most recent posts we hold, published 13 July 2026 to 11 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

11 Aug 2026, 11:21 UTC707 viewsread 13 August 2026
Photo

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.35 🌐 前端: 2.29.10 ▎🏂 Stash 支持 MASQUE 文档 https://stash.wiki/proxy-protocols/proxy-types#masque ▎📈 Surge MASQUE 不是 Cloudflare 的 WARP MASQUE 感觉应该没人用 先不加了 文档: https://manual.nssurge.com/policies/masque.html 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

11 Aug 2026, 10:05 UTC776 viewsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.34 🌐 前端: 2.29.10 ▎📈 Surge TrustTunnel 支持 h3 支持使用 Surge 格式写 h3=true 作为输入, 或使用节点字段 network: 'h3' 设置 h3=true ▎🐿️ Egern tfo 字段格式规范化 机场下发比较奇葩的值建议发工单骂机场 感谢群友 @Vindurrr 的反馈 ▎📈 Surge MASQUE 不是 Cloudflare 的 WARP MASQUE 感觉应该没人用 先不加了 文档: https://manual.nssurge.com/policies/masque.html 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

9 Aug 2026, 16:07 UTC976 viewsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.32 🌐 前端: 2.29.10 ▎🐿 Egern HTTP 1 传输层字段改为 http1 鼠爸啥时候偷偷改的没告诉我 😏 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

9 Aug 2026, 06:22 UTC≈1,130 viewsread 13 August 2026

群友 @Delusions6515 维护的 Sub-Store Android 模块版又更了 大家多提提反馈建议 最近修复了权限相关的问题 我的模块版可以退休了 😋 Magisk 用户如果想用 WebUI 可以试试这两个 https://github.com/KOWX712/KsuWebUIStandalone/releases https://github.com/MMRLApp/WebUI-X-Portable/releases 🔗 Delusions6515/Sub-Store-Module 🤭 Sub-Store 合集 🤭 Android 版 🥰 #SubStore #Sub-Store #Android #magisk #模块 #脚本 #KernelSU #APatch #Node.js

Signed 小一

7 Aug 2026, 02:34 UTC≈1,730 views7 reactionsread 13 August 2026
Photo

这种傻屄机场别用了吧 🤭 Sub-Store 合集 🥰 #SubStore #说明 #公告 #机场

7

Signed 小一

5 Aug 2026, 04:07 UTC≈1,770 viewsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.31 🌐 前端: 2.29.10 ▎📦 sing-box 🏇 Hysteria 2 支持 disable_chrome_parrot 和 bbr_profile 通过节点的字符串字段 disable-chrome-parrot, bbr-profile 设置 ▎合并 mihomo 配置覆盖层一次, 避免 GLOBAL 出现重复节点 感谢 PR 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

4 Aug 2026, 02:04 UTC≈1,620 viewsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.29 🌐 前端: 2.29.10 ▎支持单条订阅和组合订阅配置 "不查询订阅流量信息" ▎支持订阅链接参数传入 noFlow 强制指定 "不查询订阅流量信息" ▎sing-box AnyTLS 支持设置 client_metadata 即使用节点字段 client-metadata 设置 https://sing-box.sagernet.org/zh/manual/misc/anytls-client-metadata 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

3 Aug 2026, 11:46 UTC≈1,510 viewsread 13 August 2026

🔗 Sub-Store 更新预告 风佬版的 sing-box AnyTLS 使用的是 client_name,用于修改客户端标识 世界最近也更新了 将使用 client_metadata: commit 风佬将随下个版本更新 Sub-Store 下个版本将从 client_name 改为 client_metadata 即使用节点字段 client-metadata 设置 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

1 Aug 2026, 04:03 UTC≈1,530 views1 reactionsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.27 🌐 前端: 2.29.9 ▎🐱 mihomo 支持 ZeroTier https://github.com/MetaCubeX/mihomo/commit/b082515057376c469fd00fb519911788c7cc3181 ▎协议筛选支持 ZeroTier ▎优化环境变量提示 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

🥰1

Signed 小一

29 Jul 2026, 07:20 UTC≈1,720 views1 reactionsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.24 🌐 前端: 2.29.8 ▎📦 sing-box 非官方版 支持 AnyTLS client_name 字段 通过节点字段 client-name 设置 文档 ▎Android 模块版中的更新脚本调整了逻辑 GitHub API 限制太严格了 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

1

Signed 小一

28 Jul 2026, 13:02 UTC≈1,580 viewsread 13 August 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.23 🌐 前端: 2.29.7 ▎sing-box 非官方版 支持 Snell version 6 quic_proxy_mode 字段 通过节点字段 quic-proxy-mode 设置 文档 ▎样式优化 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

25 Jul 2026, 07:30 UTC≈1,920 views1 reactionsread 13 August 2026
Photo

🔗 Sub-Store 更新 ⚙️ 后端: 2.36.22 🌐 前端: 2.29.6 ▎支持配置下载 Gist 数据时 Token 处理逻辑 感谢群友 @inaisii 的建议 ▎增强 🐱 mihomo 输入的兼容性 感谢群友 @Luca_OuO 的反馈 ▎即时预览 节点 JSON 优化 如图 方便查看和复制 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

1

Signed 小一

Showing the 12 most recent of 24 posts we hold for @cool_scripts. 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 — 415,689 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

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.

Mentions

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

“Cool Scripts” (@cool_scripts), 16,227 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/cool_scripts.

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.