Telegram RegisterThe public register of Telegram
Telegram profile photo for 免费翻墙小说音乐代理APK

Channel

免费翻墙小说音乐代理APK

@yo520

On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

36,146subscribers

+962 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001003144761
TypeChannel
Username@yo520
Description频道不破解软件,只做破解软件互联网搬运工! 破解软件等所有资源来自互联网收集整理分享!
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live27 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/yo520

Topic

Technology — a classification, not a measurement. 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

35,17536,16935,6726 August 2026 — 35,184 subscribers6 August 2026 — 35,175 subscribers7 August 2026 — 35,220 subscribers8 August 2026 — 35,268 subscribers9 August 2026 — 35,322 subscribers10 August 2026 — 35,366 subscribers11 August 2026 — 35,452 subscribers12 August 2026 — 35,529 subscribers14 August 2026 — 35,653 subscribers15 August 2026 — 35,793 subscribers17 August 2026 — 35,918 subscribers18 August 2026 — 35,975 subscribers19 August 2026 — 35,833 subscribers20 August 2026 — 35,922 subscribers21 August 2026 — 35,949 subscribers23 August 2026 — 36,081 subscribers24 August 2026 — 35,814 subscribers25 August 2026 — 35,816 subscribers26 August 2026 — 35,889 subscribers27 August 2026 — 35,970 subscribers28 August 2026 — 35,969 subscribers29 August 2026 — 35,975 subscribers30 August 2026 — 36,005 subscribers1 September 2026 — 36,043 subscribers3 September 2026 — 36,064 subscribers4 September 2026 — 36,092 subscribers7 September 2026 — 36,151 subscribers10 September 2026 — 36,169 subscribers12 September 2026 — 36,131 subscribers14 September 2026 — 36,104 subscribers15 September 2026 — 36,134 subscribers17 September 2026 — 36,162 subscribers27 September 2026 — 36,146 subscribers36,1466 August 202627 September 2026
33 measurements spanning 52 days, net +962. 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 35,026–36,318 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
27 Sept 2026, 13:4036,146-16
17 Sept 2026, 15:4036,162+28
15 Sept 2026, 12:5936,134+30
14 Sept 2026, 01:0036,104-27
12 Sept 2026, 10:0136,131-38
10 Sept 2026, 08:5936,169+18
7 Sept 2026, 03:5736,151+59
4 Sept 2026, 08:5936,092+28
3 Sept 2026, 00:3636,064+21
1 Sept 2026, 01:3536,043+38
30 Aug 2026, 22:3736,005+30
29 Aug 2026, 21:0635,975+6
28 Aug 2026, 19:4435,969-1
27 Aug 2026, 19:5635,970+81
26 Aug 2026, 20:5435,889+73
25 Aug 2026, 20:3435,816+2
24 Aug 2026, 18:4735,814-267
23 Aug 2026, 00:4636,081+132
21 Aug 2026, 10:4535,949+27
20 Aug 2026, 09:3635,922first reading

Engagement

234 posts held, back to 3 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 108 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.878%
avg views ÷ 36,146 subscribers
Avg views / post
317
103 posts measured
Reaction rate
0.454%
reactions ÷ views · ER floor
Posts in window
103
of 234 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 81 of 103 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 28 September 2026
Posts held234 (3 August 2026 – 28 September 2026)
Views total32,691
Reactions total116
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Sept 2026, 08:49 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
5
Links
396

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

129 reactions across 94 posts, in 6 distinct kinds. The most used accounts for 46.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6046.5%
🥰1713.2%
💋1612.4%
👎1511.6%
😍1511.6%
🔥64.65%

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

Measured over the 234 most recent posts we hold, published 3 August 2026 to 28 September 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

27 Sept 2026, 12:07 UTC180 views2 reactionsread 28 September 2026
Forwarded from @yo521

#flclash v0.8.99-pre.4 https://github.com/chen08209/FlClash/actions/runs/36312105059 新功能 • 编辑器支持自动换行、Clash和脚本代码片段的自动补全,以及一个不再阻止选择的上下文菜单。 • 更多仪表盘卡片,以及一个始终保持打开状态的添加窗口。 • 侧边栏、浮动停靠栏或底部停靠栏,支持窗口对齐、拖动返回,以及重新设计的“主题”页面。 • 自定义规则可以突出显示无效的代理和规则,并且添加的规则可以快速设置预设。 • DNS查询日志,仅更改选定键的DNS和NTP设置,以及一个“常规设置”页面,以及更多快捷键。 • 服务检查通过代理进行,并且显示出口IP的质量和风险。 • 托盘显示快捷键、节点延迟以及延迟测试。 错误修复 • 推送通知在Doze模式下可以重新连接,并且唤醒屏幕不再测试所有节点。 • 恢复操作不再留下未完全应用的备份。

💋1🥰1

27 Sept 2026, 05:47 UTC209 views1 reactionsread 28 September 2026
Forwarded from @yo521

#Bettbox v1.19.3 Bettbox 新版本 一个现代且轻量级的 Mihomo (Clash Meta) 客户端 如果您正在寻找一个快速且易于使用的 Mihomo 客户端替代品,Bettbox 是一个最佳选择。 该项目基于早期的 FlClash 版本进行重建,但几乎所有方面都得到了优化,从用户界面到电池消耗和整体性能。 它的目标很简单:使其运行更流畅,消耗更少的电池,并且始终稳定运行。 🔹 支持的协议: • VLESS (Reality / XHTTP) • VMess • Trojan • Shadowsocks (R / 2022 / ShadowTLS / Restls) • Hysteria 1 & 2 • TUIC • WireGuard • Tailscale • OpenVPN • SSH • AnyTLS • Snell (v1 到 v5) • Masque • TrustTunnel • Gost-…

🔥1

27 Sept 2026, 05:04 UTC190 views1 reactionsread 28 September 2026
Forwarded from @yo521

#sushtun@yo521 sushTun 是一个开源且免费的 X 代理客户端,支持 VLESS、VMess、Trojan、Shadowsocks、Hysteria2 和 WireGuard 等协议,并将系统所有流量通过 X 代理进行传输。 该程序(适用于 Windows、Linux 和 macOS)的一个实用功能是智能路由,允许您指定来自伊朗、俄罗斯、中国、广告以及特定域名或 IP 地址的流量,不通过代理隧道传输。此外,还支持 DNS 设置、TLS 分片、多路复用等功能。低功耗模式允许系统后台流量(如遥测和更新)直接连接到互联网,而无需经过代理。 👉 github.com/soroushdeimi/sushTun/releases

🥰1

26 Sept 2026, 10:58 UTC276 views1 reactionsread 28 September 2026
Forwarded from @yo521

🚀 #Satelite One 一个客户端,3个内核,适用于Android 如果您对普通的客户端感到厌倦,Satelite One是一个有趣的项目,它将多个功能整合在一起。 这个Android客户端支持三个内核: 🔹 sing-box 1.14 🔹 mihomo (Clash Meta) 🔹 Xray v26 更重要的是,您可以在运行时在这些内核之间切换。 🔥 它与许多其他客户端的不同之处在于: 🧠 智能模式 该程序每30秒检查当前节点的状况,如果延迟过高,它会自动检查其他节点,并在合适的情况下切换到更好的选项。 📡 真实节点测试 它不仅依赖于Ping,还通过实际连接来测试节点,以确保选择基于真实的连接状态。 ⚙️ 一个应用程序中的三个内核 如果使用sing-box的配置效果更好,则继续使用;如果需要,可以尝试mihomo或Xray。所有内容都包含在一个客户端中。 📦 支持多种格式 支持Clash YAML、B…

😍1

26 Sept 2026, 05:02 UTC256 viewsread 28 September 2026
Forwarded from @yo521

#Satelite Satelite 是一款开源且免费的代理应用程序,适用于 Android、Windows、Linux 和 macOS 系统。它可以切换 Sing-box、Xray 和 mihomo 等内核。 它涵盖了各种订阅和配置的导入,以及基于规则的路由、代理链、智能 DNS、系统代理和 TUN 等功能。其中一个有趣的功能是多核模式,允许多个内核同时工作;例如,Sing-box 可以作为主内核,并将某些协议分配给 Xray 或 mihomo。 其他功能包括智能节点选择、延迟和出口 IP 测试、DNS 和 Hosts 管理,以及自动检测进程和在系统托盘中永久运行。 👉 github.com/zn0wii/satelite-proxy/releases 💡 github.com/zn0wii/satelite-one/releases

25 Sept 2026, 23:38 UTC261 views1 reactionsread 28 September 2026
Forwarded from @yo521

#throne@yo521 Throne for Android 🔥 Android版本 基于NekoBox for Android开发,使用sing-box内核。 https://github.com/throneproj/ThroneForAndroid https://github.com/throneproj/ThroneForAndroid/releases/tag/v2.0.0

😍1

25 Sept 2026, 23:37 UTC244 views1 reactionsread 28 September 2026
Forwarded from @TAndroidAPKFile

12.10.5 (7105) Directly downloadable from telegram.org/android

👎1

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

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 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.

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

“免费翻墙小说音乐代理APK” (@yo520), 36,146 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/yo520.

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.