Channel
@h5683577
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,593subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001543775171 |
|---|---|
| Type | Channel |
| Username | @h5683577 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/h5683577 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 15:15 | 6,593 | -8 |
| 11 Aug 2026, 09:04 | 6,601 | -6 |
| 8 Aug 2026, 05:42 | 6,607 | -5 |
| 7 Aug 2026, 08:31 | 6,612 | no change |
| 7 Aug 2026, 08:28 | 6,612 | first reading |
19 posts held, back to 11 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 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 19 posts for this entry, the most recent from 24 April 2026. An engagement rate over an empty window would be a number about nothing.
88 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 66 | 75.0% | |
| 👍 | 13 | 14.8% | |
| 🤡 | 3 | 3.41% | |
| 🤮 | 3 | 3.41% | |
| 😘 | 2 | 2.27% | |
| 💯 | 1 | 1.14% |
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 18 of the 19 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 88reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 11 May 2025 to 24 April 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.
📝 Script Hub Beta 版 更新 热烈欢迎 YuHeng @onz3v 佬加入 Script Hub 开发组 🥰 并带来了本次更新 - 优化 📈 Surge 和 🎈 Loon 对参数的处理 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤10👍4🤮2
Signed 小一
📝 Script Hub 更新 - 优化 仅进行兼容性转换 参数判断和 在脚本开头添加代码 功能 刚刚在看 Surge 的新功能：Logbook... 用 在脚本开头添加代码 或 高级操作(使用代码处理脚本的内容) 就能实现在原来没接入 这个 API ( $surge.logbook ) 的脚本里使用它 同样的 它其实也能用来给没给通知加图片/声音参数的脚本加上参数( 之前也发了 项目情况说明 1. 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 2. 欢迎 PR. 但是需要维护. 可先 PR 到 beta 文件里 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤6🤮1
Signed 小一
📝 Script Hub 更新 - 脚本转换时也使用自定义请求 Headers 如图 感谢 群友的反馈 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤3🤡3
Signed 小一
📝 Script Hub 更新 - 修复 🏂 Stash 的 transparent 重写 - 🌀 QX jq 转 📈 Surge 和 🎈 Loon 时, 包裹单引号 没有老张有点修不来 现阶段可能需要用户发挥主观能动性 使用 高级操作 自己处理未修复的问题 🎲 项目地址 🥰 #ScriptHub #更新记录 #changlog #updates
❤4
Signed 小一
还差八个！！！
Signed 那天我被张佩服用石头砸了一下头
📝 Script Hub 更新 - 🐿️ Egern 模块一键导入 感谢群友 @dewd117 的建议 🎲 项目地址 🥰 #ScriptHub
❤16
Signed 小一
我一定不是最后一个知道的
Signed 那天我被张佩服用石头砸了一下头
Shadowrocket 测试版更新 Version 2.2.70 (2712) 测试内容： * add macOS x86_64 and arm64 supports 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]
❤4
Signed 那天我被张佩服用石头砸了一下头
📝 Script Hub 更新 - 修复 qx echo-response 转 loon mock 失败的问题 - 修复 jq 输出到 shadowrocket 时会丢失的问题 - 修复 surge body rewrite 转至 loon 时 type 错误的显示为 jq 的问题 老张持续发力 🎲 项目地址 🥰 #ScriptHub
❤1💯1
Signed 小一
📝 Script Hub 更新 - 修复了 Shadowrocket 的 {{{禁用MITM}}} 一直是 hostname 的 bug 老张持续发力 不忘🚀 🎲 项目地址 🥰 #ScriptHub
❤2
Signed 小一
📝 Script Hub 更新 - 支持 qx 的 jsonjq 类型作为输入 老张又偷偷努力了 🎲 项目地址 🥰 #ScriptHub
❤2
Signed 小一
推荐一个手机端可以推git的app，PolyGit Git Client https://apps.apple.com/app/id1508942822
❤1
Signed 那天我被张佩服用石头砸了一下头
Showing the 12 most recent of 19 posts we hold for @h5683577. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@h5683577 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“张佩服应该判几年” (@h5683577), 6,593 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/h5683577.
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.