公费可以免费试用两天 到期后可以选择续费 或者 自动转公益 不用保号☺️
Signed 𝑮𝒓𝒆𝒆𝒏

Channel
@iOSScripthub
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
82subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003512149173 |
|---|---|
| Type | Channel |
| Username | @iOSScripthub |
| Created | 22 January 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/iOSScripthub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:17 | 82 | -1 |
| 9 Aug 2026, 17:32 | 83 | no change |
| 6 Aug 2026, 05:19 | 83 | first reading |
12 posts held, back to 22 January 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 28 July 2026 |
|---|---|
| Posts held | 12 (22 January 2026 – 28 July 2026) |
| Views total | 197 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 17:32 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.
18 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 77.8% | |
| 👍 | 4 | 22.2% |
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 7 of the 12 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 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 22 January 2026 to 28 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.
公费可以免费试用两天 到期后可以选择续费 或者 自动转公益 不用保号☺️
Signed 𝑮𝒓𝒆𝒆𝒏
▎ETFLIX 「此篇内容由腐竹强烈要求发布」 ETFLIX 是一个主推移动网盘资源的公费服,可根据个人需求在开启天翼资源。 😀新人福利: 新人注册即送 2 天免费公费体验(公费到期自动降级为公益资源),公费可跑满千兆带宽; 😀拉新福利: 用专属链接邀请新人,即送 7 天公费时长(切记不要在别服发送造成不良影响); 😀自研后端:公费emby后端采用 golang 重构,完全自研; 😀海量资源:总集数超过 38 万+,电影 2.7万+; 官方群组: @ETFLIX_EMBY_GROUP 友情提示:ETFLIX Emby已于26年2月正式运营,至今已满足频道三个月的宣传要求。 该Emby服务为付费服,本文内容由腐竹提供,考虑到预付消费存在一定风险,建议选择月付方式以降低风险。请各位自行理性评估,并承担相应风险。 🗒 标签: #Emby 📢 频道: @me888888888888 🎈 群组: @imbbbbbbbbbbb…
Signed 𝑮𝒓𝒆𝒆𝒏
脚本功能:解锁两步路 VIP/去广告 使用方法:添加到重写,打开两步路会员页即可生效 应用下载: 两步路 QX脚本链接: https://raw.githubusercontent.com/curtinp118/Scripthub/refs/heads/main/scripts/2bulu/2bulu.js #解锁
👍3❤1
Signed 𝑮𝒓𝒆𝒆𝒏
🚀 吹雪云|低价高速机场推荐 注册即送 7 天 128G 试用流量,先体验线路再决定是否购买。 开业限时活动:使用优惠券 50OFF,全场 5 折,截止 7 月 9 日。 🔗 立即注册吹雪云 低至 ¥4 / 月,适合日常浏览、流媒体及多设备使用 #机场
Signed 𝑮𝒓𝒆𝒆𝒏
修复了豪华VIP功能
❤4
Signed 𝑮𝒓𝒆𝒆𝒏
脚本功能:蛋蛋不语 - 解锁VIP会员 使用方法:添加到重写,打开蛋蛋不语App即可生效 应用下载:https://danboxingqiu.cn/ QX脚本链接: https://raw.githubusercontent.com/curtinp118/QuantumultX/main/scripts/dandanvip.conf Loon脚本链接: https://raw.githubusercontent.com/curtinp118/Loon/main/plugins/dandanvip.lpx Surge脚本链接: https://raw.githubusercontent.com/curtinp118/Surge5/main/modules/dandanvip.sgmodule #解锁
❤5
脚本功能:V2EX 每日签到领取铜币 使用方法:访问 V2EX 个人主页(/member/用户名)自动抓包保存 Cookie,定时任务每天 9:10 自动签到 QX脚本链接: https://raw.githubusercontent.com/curtinp118/QuantumultX/main/scripts/v2ex.conf Loon脚本链接: https://raw.githubusercontent.com/curtinp118/Loon/main/plugins/v2ex.lpx Surge脚本链接: https://raw.githubusercontent.com/curtinp118/Surge5/main/modules/v2ex.sgmodule #签到
脚本功能:GLaDOS / Railgun 自动签到 + 积分查询 + 积分兑换(多账号、多域名) 使用方法:访问 GLaDOS 任意域名的 /console/account 页面自动抓包保存 Cookie,定时任务每天 7:10 自动签到,≥500 积分自动兑换 plan500 QX脚本链接: https://raw.githubusercontent.com/curtinp118/QuantumultX/refs/heads/main/scripts/glados.conf Loon脚本链接: https://raw.githubusercontent.com/curtinp118/Loon/main/plugins/glados.lpx Surge脚本链接: https://raw.githubusercontent.com/curtinp118/Surge5/main/modules/glados.sgmodu…
❤4
#出窍 #免费节点 #节点分享 ✅ 软件内容 免费获取高速节点 — 速度如闪电 如有需要提取别的软件节点请评论 ✅ 软件更新 优化线路获取,增加导入模式 ✅ 安装方法 导入巨魔安装 📄 或证书安装
👍1
一个自用长期维护的 Quantumult X 配置仓库: https://github.com/curtinp118/QuantumultX
请通过本频道 左下角(iOS) / 右下角(安卓) 的直通消息与我私信。
Channel created
Showing the 12 most recent of 12 posts we hold for @iOSScripthub. 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 — 977,382 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“𝑮𝒓𝒆𝒆𝒏 𝑺𝒄𝒓𝒊𝒑𝒕𝑯𝒖𝒃” (@iOSScripthub), 82 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/iOSScripthub.
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.