Telegram RegisterThe public register of Telegram
Telegram profile photo for Cool Scripts

Channel

Cool Scripts

@cool_scripts

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

16,359subscribers

+131 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 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/cool_scripts

Topic

Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

16,21416,36416,2896 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 subscribers14 August 2026 — 16,224 subscribers15 August 2026 — 16,214 subscribers16 August 2026 — 16,217 subscribers17 August 2026 — 16,220 subscribers19 August 2026 — 16,229 subscribers20 August 2026 — 16,233 subscribers21 August 2026 — 16,235 subscribers22 August 2026 — 16,236 subscribers24 August 2026 — 16,240 subscribers25 August 2026 — 16,244 subscribers26 August 2026 — 16,242 subscribers27 August 2026 — 16,244 subscribers28 August 2026 — 16,246 subscribers29 August 2026 — 16,250 subscribers30 August 2026 — 16,255 subscribers31 August 2026 — 16,263 subscribers1 September 2026 — 16,268 subscribers2 September 2026 — 16,266 subscribers3 September 2026 — 16,268 subscribers9 September 2026 — 16,264 subscribers11 September 2026 — 16,268 subscribers15 September 2026 — 16,267 subscribers17 September 2026 — 16,271 subscribers19 September 2026 — 16,278 subscribers26 September 2026 — 16,294 subscribers4 October 2026 — 16,306 subscribers9 October 2026 — 16,314 subscribers13 October 2026 — 16,323 subscribers14 October 2026 — 16,321 subscribers15 October 2026 — 16,320 subscribers16 October 2026 — 16,321 subscribers18 October 2026 — 16,326 subscribers19 October 2026 — 16,337 subscribers20 October 2026 — 16,339 subscribers21 October 2026 — 16,333 subscribers22 October 2026 — 16,335 subscribers25 October 2026 — 16,337 subscribers26 October 2026 — 16,332 subscribers27 October 2026 — 16,335 subscribers28 October 2026 — 16,334 subscribers29 October 2026 — 16,337 subscribers31 October 2026 — 16,343 subscribers31 October 2026 — 16,346 subscribers1 November 2026 — 16,350 subscribers2 November 2026 — 16,352 subscribers3 November 2026 — 16,353 subscribers4 November 2026 — 16,355 subscribers6 November 2026 — 16,357 subscribers6 November 2026 — 16,359 subscribers7 November 2026 — 16,364 subscribers9 November 2026 — 16,362 subscribers10 November 2026 — 16,359 subscribers16,3596 August 202610 November 2026
58 measurements spanning 96 days, net +131. 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,192–16,387 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
10 Nov 2026, 19:0616,359-3
9 Nov 2026, 07:5616,362-2
7 Nov 2026, 22:4516,364+5
6 Nov 2026, 22:5416,359+2
6 Nov 2026, 00:4616,357+2
4 Nov 2026, 22:4916,355+2
3 Nov 2026, 21:1616,353+1
2 Nov 2026, 17:3816,352+2
1 Nov 2026, 19:3116,350+4
31 Oct 2026, 22:0616,346+3
31 Oct 2026, 00:4516,343+6
29 Oct 2026, 22:3016,337+3
28 Oct 2026, 23:1916,334-1
27 Oct 2026, 23:0616,335+3
26 Oct 2026, 22:0516,332-5
25 Oct 2026, 22:5816,337+2
22 Oct 2026, 21:3716,335+2
21 Oct 2026, 17:3016,333-6
20 Oct 2026, 16:0916,339+2
19 Oct 2026, 17:4616,337first reading

Engagement

56 posts held, back to 13 July 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 71 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.6%
avg views ÷ 16,359 subscribers
Avg views / post
1,890
8 posts measured
Reaction rate
0.079%
reactions ÷ views · ER floor
Posts in window
8
of 56 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 4 of 8 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 10 November 2026
Posts held56 (13 July 2026 – 10 November 2026)
Views total15,154
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 06: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.

What this channel posts

Photos
455
Videos
31
Links
843

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

50 reactions across 21 posts, in 5 distinct kinds. The most used accounts for 64.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3264.0%
👍1224.0%
🎉36.00%
👏24.00%
🥰12.00%

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

Measured over the 56 most recent posts we hold, published 13 July 2026 to 10 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 8 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).

10 Nov 2026, 10:04 UTC734 viewsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.44.7 🌐 前端: 2.34.2 Egern 的 XHTTP 还没更 等鼠爸 PR ▎完善 Shadowsocks URI extra 处理 感谢 issue 的反馈 XHTTP/REALITY URI 会处理 extra 字段 跟之前一样 若存在原始的 _extra 字段, 则直接使用该字段的值输出到 URI 的 extra 部分, 而不进行解析和重组 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

8 Nov 2026, 13:04 UTC≈1,070 views0 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.44.5 🌐 前端: 2.34.2 Egern 的 XHTTP 还没更 等鼠爸 PR ▎优化 YAML 逻辑 感谢 issue 的反馈 和 亚托莉 ▎修复 Egern WireGuard preshared_key 感谢 shica 的反馈 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

5 Nov 2026, 11:51 UTC≈1,680 views0 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.44.4 🌐 前端: 2.34.2 Egern 的 XHTTP 还没更 等鼠爸 PR ▎mihomo 支持 Snell v6 ▎尝试修复同步页面标题行显示不全 感谢深巷有喵的反馈 ▎更新依赖 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

25 Oct 2026, 13:05 UTC≈2,630 views5 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.44.2 🌐 前端: 2.34.1 ▎优化 Gist 处理逻辑 感谢群友 Classcool 的反馈 ▎修复 Gist 代码 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

❤4👍1

Signed 小一

25 Oct 2026, 04:03 UTC≈2,220 views1 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.44.1 🌐 前端: 2.34.1 ▎优化 VMess/Trojan/AnyTLS 逻辑 感谢 Pharex38 的 PR ▎修复 AnyTLS 重复解码密码 ▎更新依赖 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

👍1

Signed 小一

22 Oct 2026, 02:04 UTC≈2,340 viewsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.43.0 🌐 前端: 2.34.1 ▎升级 Node.js 和依赖版本 ▎sing-box wireguard 支持使用顶层简写的 allowed-ips 感谢 PR 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

21 Oct 2026, 15:55 UTC≈1,960 viewsread 11 November 2026
Forwarded from @sion_channelPhoto

SubCase 1.3.1已发布! 一款适用于Android平台上的强大易用的 SubStore 封装应用 更新内容 : * 修复在「同步」页上传配置到已有 GitHub Gist 时,提示“找不到 Sub-Store Gist”或 JSON 解析错误的问题 https://github.com/sub-store-org/subcase/releases/tag/v1.3.1 #SubStore #SubCase

Signed 小一

15 Oct 2026, 08:37 UTC≈2,520 viewsread 11 November 2026
Photo

🔗 Sub-Store 更新 ⚙️ 后端: 2.42.5 🌐 前端: 2.34.1 ▎分享支持长期有效 感谢 PR ▎produceArtifact 可通过 includeRaw: true 同时返回处理结果和 context.raw 对应的原始内容 详见 demo.js 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

10 Oct 2026, 13:14 UTC≈9,200 views3 reactionsread 11 November 2026

https://youtu.be/Qtf6U8Rx95o

🎉3

Signed 小一

7 Oct 2026, 04:04 UTC≈2,980 views0 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.42.3 🌐 前端: 2.34.0 ▎调整 sing-box TLS certificate_sha256 相关逻辑 sing-box 1.15.0 起支持 certificate_sha256: 自动将 tls-fingerprint 的 hex 解码后转成 Base64 数组; 手动设置 _certificate_sha256 时优先原样使用, 例如 $server._certificate_sha256 = ['47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='] 相关阅读: 自建节点证书相关说明 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

27 Sept 2026, 03:59 UTC≈3,120 views3 reactionsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.42.0 🌐 前端: 2.34.0 ▎使用 shoutrrr-ts Docker 版也移除了 shoutrrr 二进制 感谢 Delusions6515 佬的努力 在 Node.js 环境中无需 Shoutrrr 即可发送支持的 Shoutrrr URL 顺带,现在 Shoutrrr URL 还可以用代理 ▎生成 Basic Auth 前,对用户名和密码各做一次 URL 解码 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

❤3

Signed 小一

26 Sept 2026, 04:59 UTC≈2,580 viewsread 11 November 2026

🔗 Sub-Store 更新 ⚙️ 后端: 2.41.1 🌐 前端: 2.34.0 ▎调整 sing-box SSH 密钥逻辑 感谢群友 shica 的反馈 ▎调整 SS URI UDP 逻辑 感谢群友 美国网安 的反馈 🤭 Sub-Store 合集 🥰 #SubStore #更新记录 #changlog #updates

Signed 小一

Showing the 12 most recent of 56 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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.

Surfboard News
@surfboardnews · 28,389
Telegram ranks this channel #6 of 64 here — alongside 63 others — read 9 September 2026
Shadowrocket News
@ShadowrocketNews · 47,272
Telegram ranks this channel #6 of 60 here — alongside 59 others — read 27 August 2026
Surge & Loon & QX 脚本收集
@NobyDa · 64,479
Telegram ranks this channel #7 of 42 here — alongside 41 others — read 21 August 2026
不止QuantumultX
@Quantumultxxxx · 21,980
Telegram ranks this channel #9 of 37 here — alongside 36 others — read 25 September 2026
Loon News
@LoonNews · 48,270
Telegram ranks this channel #9 of 49 here — alongside 48 others — read 27 August 2026
折腾啥
@zhetengsha · 53,830
Telegram ranks this channel #9 of 50 here — alongside 49 others — read 26 August 2026
֍可莉日常֎
@ibilibili · 49,570
Telegram ranks this channel #11 of 40 here — alongside 39 others — read 14 September 2026
广告必须死
@Aa28413761 · 26,843
Telegram ranks this channel #11 of 37 here — alongside 36 others — read 13 September 2026
APTV通知频道
@AptvPlayerChannel · 37,270
Telegram ranks this channel #12 of 38 here — alongside 37 others — read 5 September 2026
iOS优质应用
@ioskk · 50,613
Telegram ranks this channel #14 of 35 here — alongside 34 others — read 25 August 2026
🍟 整点薯条: 频道
@GetSomeFriesChannel · 20,341
Telegram ranks this channel #15 of 45 here — alongside 44 others — read 29 September 2026
刀刀源 | iOS | 越狱
@ae86_dao · 29,166
Telegram ranks this channel #18 of 25 here — alongside 24 others — read 14 September 2026
Appinn Feed|小众软件
@appinnfeed · 34,958
Telegram ranks this channel #18 of 52 here — alongside 51 others — read 4 September 2026
Faker | iKun聚集地
@scriptalking · 27,954
Telegram ranks this channel #19 of 41 here — alongside 40 others — read 10 September 2026
 Apple Nuts
@AppleNuts · 37,705
Telegram ranks this channel #19 of 56 here — alongside 55 others — read 1 September 2026
iOS宝藏
@iosrxwy · 100,084
Telegram ranks this channel #19 of 28 here — alongside 27 others — read 31 August 2026
CMLiussss 技术干货分享
@CMLiussss_channel · 71,967
Telegram ranks this channel #20 of 47 here — alongside 46 others — read 21 August 2026
TestFlightX
@TestFlightX · 43,470
Telegram ranks this channel #21 of 37 here — alongside 36 others — read 28 August 2026
小果子|iOS越狱交流频道
@guozhiapp · 21,887
Telegram ranks this channel #22 of 25 here — alongside 24 others — read 20 September 2026
秀儿の科技软件|资源分享社🎀
@jianjiaoPD · 133,020
Telegram ranks this channel #23 of 42 here — alongside 41 others — read 4 September 2026
Nexitally Official Channel
@Nexitally_Official · 21,086
Telegram ranks this channel #26 of 44 here — alongside 43 others — read 26 September 2026
叮当猫のiOS资源分享频道
@ddm1023 · 50,298
Telegram ranks this channel #29 of 41 here — alongside 40 others — read 26 August 2026
APPDO 数字生活指南
@AppDoDo · 40,978
Telegram ranks this channel #40 of 57 here — alongside 56 others — read 30 August 2026
Newlearnerの自留地
@NewlearnerChannel · 68,274
Telegram ranks this channel #40 of 62 here — alongside 61 others — read 21 August 2026

This channel appears in 25 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Cool Scripts” (@cool_scripts), 16,359 subscribers as measured 10 November 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.