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

Channel

Chavy Scripts

@chavyscripts

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

10,252subscribers

-18 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-1001405837783
TypeChannel
Username@chavyscripts
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/chavyscripts

Growth

10,25210,27110,261.56 August 2026 — 10,270 subscribers7 August 2026 — 10,270 subscribers8 August 2026 — 10,269 subscribers10 August 2026 — 10,271 subscribers12 August 2026 — 10,269 subscribers13 August 2026 — 10,268 subscribers14 August 2026 — 10,264 subscribers16 August 2026 — 10,260 subscribers17 August 2026 — 10,255 subscribers20 August 2026 — 10,256 subscribers21 August 2026 — 10,254 subscribers22 August 2026 — 10,252 subscribers6 August 202622 August 2026
12 measurements spanning 17 days, net -18. 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 10,249–10,274 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 17:3710,252-2
21 Aug 2026, 07:2410,254-2
20 Aug 2026, 10:2510,256+1
17 Aug 2026, 14:1510,255-5
16 Aug 2026, 04:3910,260-4
14 Aug 2026, 15:2610,264-4
13 Aug 2026, 07:3410,268-1
12 Aug 2026, 10:2710,269-2
10 Aug 2026, 04:3910,271+2
8 Aug 2026, 04:5210,269-1
7 Aug 2026, 01:4310,270no change
6 Aug 2026, 05:1810,270first reading

Engagement

17 posts held, back to 21 April 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 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 17 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
47
Videos
14
Links
92

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

Video runtime
1m 22s
Average length
27s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

241 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 53.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12853.1%
👍9439.0%
🎉177.05%
🤔20.83%

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

Measured over the 17 most recent posts we hold, published 21 April 2024 to 15 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

15 Jul 2026, 15:31 UTC≈2,630 views4 reactionsread 23 August 2026
File

#Relay 1.0.1(build 13) What's New! - 支持纯JSON内容导入订阅(无需订阅 URL,某种程度上也算是匿名订阅) - 结合skill和纯JSON内容内容订阅解决部分用户订阅加载失败及数据问题(部分开发者的订阅格式是非标准写法,Relay 客户端无法做到全部完全兼容) - 一些 UI 细节调整 - 新增意见反馈入口,携带日志发送邮件,快速帮助开发者定位问题 下一个版本将支持: - 自定义壁纸 - 其他 UI 细节调整 #skill - 专门用于创建、检查和修复标准 BoxJS 订阅 JSON,避免因为字段缺失、类型错误或非标准格式,导致 Relay 用户的数据无法正常加载 - 特别适合 BoxJS 订阅作者、脚本开发者以及 Relay 兼容性排查

4

Signed Senku

27 Mar 2026, 09:31 UTC≈8,680 views6 reactionsread 23 August 2026
Video

Video, posted without a caption

👍42

Signed Senku

12 Mar 2026, 11:27 UTC≈21,900 viewsread 23 August 2026
Photo

让 AI 写了个 Scritable 的脚本看看 Claude 使用量 地址: https://github.com/gideonsenku/Scriptable/blob/master/ClaudeUsage/claude-usage.js

Signed Senku

13 Feb 2026, 09:28 UTC≈33,400 views5 reactionsread 23 August 2026

同程旅行脚本 /** * * hostname = app.17u.cn * * # Surge * http-request ^https:\/\/app\.17u\.cn\/welfarecenter\/index\/signIndex script-path=https://raw.githubusercontent.com/chavyleung/scripts/master/tongcheng-trip/tongcheng-trip.js, tag=同程旅行 * cron "5 12 * * *" script-path=https://raw.githubusercontent.com/chavyleung/scripts/master/tongcheng-trip/tongcheng-trip.js, timeout=300, tag=同程旅行-签到 * * # QuanX * ^https:\

2👍2🎉1

Signed Senku

11 Feb 2026, 07:12 UTC≈28,500 views0 reactionsread 23 August 2026

https://github.com/chavyleung/scripts/commit/1d691675451bf0416f4e7619c61b2ea057a9fbbd #Scripts 尝试修复智行火车签到

Signed Senku

1 Jul 2025, 03:06 UTC≈13,500 views24 reactionsread 23 August 2026

Jetbrains 全家桶免费一年 活动网址: https://www.jetbrains.com/store/redeem/ 兑换码:DataGrip2025

24

Signed Senku

10 Mar 2025, 07:59 UTC≈16,100 views2 reactionsread 23 August 2026

#release 0.19.21 - 修复部分用户订阅超过20导致更新失败 fix(boxjs): 订阅并发控制

2

Signed Senku

21 Feb 2025, 16:19 UTC≈15,300 views8 reactionsread 23 August 2026

#书籍推荐 问就是在如何解决内耗 https://www.dev-life.site/

👍71

Signed Senku

15 Nov 2024, 07:13 UTC≈19,400 views17 reactionsread 23 August 2026

#PayPal 刚刚发现 PayPal 偷偷地把 币种兑换 从 通过银行兑换 改成 通过PayPal兑换 这会导致自动付款时多收一笔费用 有用 MasterCard 绑定 PayPal 自动付款的同学尽快检查处理一下

13👍2🤔2

Signed Chavy

28 Oct 2024, 06:50 UTC≈21,800 views19 reactionsread 23 August 2026
Photo

支持首页删除收藏应用,开启方式在悬浮按钮上

👍136

Signed Senku

Showing the 12 most recent of 17 posts we hold for @chavyscripts. 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 — 293,314 of 1,584,486entries 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 8 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“Chavy Scripts” (@chavyscripts), 10,252 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/chavyscripts.

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.