Telegram RegisterThe public register of Telegram
Telegram profile photo for 好软分享·资源频道

Channel

好软分享·资源频道

@haoruanfenxiangresources

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

22,764subscribers

+1,008 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-1002304701415
TypeChannel
Username@haoruanfenxiangresources
Description好软分享·主频道: @haoruanfenxiang 好软分享·列表频道: @haoruanfenxianglist 好软分享·资源频道: @haoruanfenxiangresources 好软分享·交流群: @haoruanfenxianggroup
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/haoruanfenxiangresources

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 68% 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 why it has no browse page of its own yet.

Growth

21,75622,76422,2606 August 2026 — 21,756 subscribers6 August 2026 — 21,756 subscribers7 August 2026 — 21,793 subscribers8 August 2026 — 21,809 subscribers9 August 2026 — 21,829 subscribers10 August 2026 — 21,849 subscribers11 August 2026 — 21,866 subscribers12 August 2026 — 21,875 subscribers13 August 2026 — 21,887 subscribers14 August 2026 — 21,907 subscribers15 August 2026 — 21,927 subscribers17 August 2026 — 21,968 subscribers18 August 2026 — 21,997 subscribers19 August 2026 — 22,016 subscribers20 August 2026 — 22,036 subscribers21 August 2026 — 22,043 subscribers22 August 2026 — 22,080 subscribers24 August 2026 — 22,122 subscribers25 August 2026 — 22,148 subscribers26 August 2026 — 22,168 subscribers27 August 2026 — 22,179 subscribers28 August 2026 — 22,196 subscribers29 August 2026 — 22,218 subscribers30 August 2026 — 22,231 subscribers31 August 2026 — 22,246 subscribers1 September 2026 — 22,278 subscribers2 September 2026 — 22,305 subscribers3 September 2026 — 22,337 subscribers6 September 2026 — 22,402 subscribers9 September 2026 — 22,477 subscribers11 September 2026 — 22,514 subscribers13 September 2026 — 22,538 subscribers15 September 2026 — 22,577 subscribers17 September 2026 — 22,613 subscribers25 September 2026 — 22,764 subscribers6 August 202625 September 2026
35 measurements spanning 50 days, net +1,008. 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 21,605–22,915 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 02:4022,764+151
17 Sept 2026, 05:3922,613+36
15 Sept 2026, 06:5922,577+39
13 Sept 2026, 14:1722,538+24
11 Sept 2026, 18:5822,514+37
9 Sept 2026, 10:1722,477+75
6 Sept 2026, 02:3822,402+65
3 Sept 2026, 18:4122,337+32
2 Sept 2026, 08:1322,305+27
1 Sept 2026, 07:3622,278+32
31 Aug 2026, 05:0422,246+15
30 Aug 2026, 07:2422,231+13
29 Aug 2026, 09:3722,218+22
28 Aug 2026, 12:4222,196+17
27 Aug 2026, 12:0822,179+11
26 Aug 2026, 15:1922,168+20
25 Aug 2026, 12:2822,148+26
24 Aug 2026, 11:3422,122+42
22 Aug 2026, 17:0222,080+37
21 Aug 2026, 05:2522,043first reading

Engagement

211 posts held, back to 5 August 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 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.13%
avg views ÷ 22,764 subscribers
Avg views / post
713
64 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
64
of 211 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 September 2026
Posts held211 (5 August 2026 – 25 September 2026)
Views total45,660
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 02:05 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
≈293
Links
≈3,640

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

25 Sept 2026, 09:35 UTC≈1,370 viewsread 27 September 2026
File

#bilipai v0.2.3-alpha.5(2026-09-25) === 致谢 感谢 @1290000 提交 PR #825 与 PR #826,贡献视频快捷收藏以及 QQ / 微信好友直达分享功能。 感谢 @CoderTCY 提交 PR #828,重构播放器倍速配置与长按临时加速功能。 播放与倍速 [添加] 播放设置新增可编辑的统一倍速列表,播放器倍速菜单、双指调速与默认播放速度统一使用同一套配置。(PR #828 · @CoderTCY) [添加] 长按临时加速改为独立倍速设置,支持 1.0x–8.0x 滑块调节、1.5x / 2x / 3x / 4x / 6x / 8x 快捷倍速,以及点按数值直接输入。(PR #828 · @CoderTCY) [适配] 离线视频播放器同步接入新的倍速配置体系。(PR #828 · @CoderTCY) [修复] 删除当前默认倍速或上次使用倍速后,自动切换至最接近的有效倍速,避免倍速…

Signed yoyodadada

25 Sept 2026, 09:35 UTC≈1,360 viewsread 27 September 2026
Photo

#NewHook #lwely v2.1.6 === • 新增适配应用: • 无界趣连(订阅会员) • Mola相机(AI构图) • 修复适配应用: • 安卓清理君 • 滴答清单 💠下载链接:点我下载

Signed yoyodadada

25 Sept 2026, 09:35 UTC≈1,260 viewsread 27 September 2026
File

#墨迹天气 #kunkka v9.0948.02会员版_Kunkka

Signed yoyodadada

25 Sept 2026, 09:35 UTC≈1,220 viewsread 27 September 2026
File

#哔哩哔哩 #kunkka v9.13.0-内置漫游7c792dc8fe模块_Kunkka

Signed yoyodadada

25 Sept 2026, 09:35 UTC993 viewsread 27 September 2026

#酷安 #东明 v16.6.2(2609151)v2Fix-by东明 === ✅去广告 ✅去更新 new ✅优化去广告 【下载链接】2026年9月23日23:50 https://drive.uc.cn/s/ae89c4c242a04?public=1

Signed yoyodadada

25 Sept 2026, 09:35 UTC867 viewsread 27 September 2026

#1DM #liu v18.2 === 下载链接: https://pan.quark.cn/s/2efc3c2fe2ef https://pan.baidu.com/s/1ztkNZR3SImEAgnxh9jtmJg?pwd=r77y

Signed yoyodadada

25 Sept 2026, 09:35 UTC801 viewsread 27 September 2026
Photo

#emby_TV版 #kirlif V2.1.59g ATV (Unlocked) === ⚙️ Mods(A7+, Arm + arm64)- ● Paid Features Unlocked (In-App) ● Compression Flags Untouched ● No Third Party Patch/... ● No Additional Component ● Size: 34.9 MB ● Release by Kirlif' 🔗 Download: https://frdl.my/q178pqso8xm3 https://upfiles.com/u3oAPi https://mega4upload.net/yg48egeop0gj https://uploadrar.com/29tb0dsz9si5 https://zdrive.to/2bJG8ao6mOBE

Signed yoyodadada

25 Sept 2026, 09:35 UTC805 viewsread 27 September 2026

#emby #kirlif v3.5.55 [Unlocked] [Altered] === ⛏️Short Info (A5+, 36 MB): ● Paid Features Unlocked (In-App) ● Firebase Removed ● Datatransport Removed ● Compression Flags Untouched ● No Third Party Patch/Hook/... ● Release by Kirlif' -arm: https://frdl.my/tabd9d1frw4b https://upfiles.com/qxGFi4Q https://mega4upload.net/fpsx5400ib87 https://uploadrar.com/3sb0yryyeuxv https://zdrive.to/qw1zew8emXyn -arm64: https://frdl…

Signed yoyodadada

25 Sept 2026, 09:35 UTC939 viewsread 27 September 2026
File

#Hills v1.9.1-Hills === 支持 mpv HDR 显示输出 支持弹幕自定义字体 支持聚合视界按最近观看排序 支持下载字幕持久化保存 优化 WebDAV 备份还原兼容性 修复服务器列表菜单无法显示异常 修复部分服务器无法播放 mpv HDR 显示输出: 开启后,在支持 HDR 的设备上播放 HDR 视频时,可触发系统 HDR 显示模式,提升屏幕亮度并输出 HDR 效果。该功能默认关闭,可前往“设置” → “播放器” → “mpv 播放器设置” → “HDR 显示输出”开启。 目前不支持 Google Play 的设备也支持使用兑换码添加账号权益,购买兑换码可联系 @Mountains0Bot

Signed yoyodadada

25 Sept 2026, 09:35 UTC828 viewsread 27 September 2026
File

#合集_xposed #BiliFix #哔哩哔哩 v0.11.0-37 === 针对国际白版b站(com.bilibili.app.in)的功能修复与增强 兼容性 • 仅支持哔哩哔哩国际白版 (com.bilibili.app.in) 3.20.4 • Xposed API 101 或更高版本 功能 功能设置入口已集成进应用内设置 BugFix • 重构部分Hook,大幅缩减某些情况下的内存占用与性能开销

Signed yoyodadada

25 Sept 2026, 09:35 UTC813 viewsread 27 September 2026
File

#合集_xopsed #Dyyds #抖音 v0922151325 === 适配 抖音正式版 40609900 抖音港版 40319900 ‼️注意 免费模块,请勿倒卖 请勿在国内平台分享 禁止用于商业用途及非法用途 如果看到有人倒卖请帮忙举报

Signed yoyodadada

Showing the 12 most recent of 211 posts we hold for @haoruanfenxiangresources. 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.

Mentions

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

“好软分享·资源频道” (@haoruanfenxiangresources), 22,764 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/haoruanfenxiangresources.

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.