Telegram RegisterThe public register of Telegram
Telegram profile photo for XO521免费小说阅读

Channel

XO521免费小说阅读

@xo521

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,636subscribers

-28 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001776589377
TypeChannel
Username@xo521
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/xo521

Topic

Literature — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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

2,6362,6642,6507 August 2026 — 2,664 subscribers7 August 2026 — 2,664 subscribers8 August 2026 — 2,662 subscribers10 August 2026 — 2,658 subscribers13 August 2026 — 2,662 subscribers23 August 2026 — 2,659 subscribers26 August 2026 — 2,655 subscribers29 August 2026 — 2,652 subscribers31 August 2026 — 2,649 subscribers3 September 2026 — 2,648 subscribers8 September 2026 — 2,644 subscribers12 September 2026 — 2,637 subscribers15 September 2026 — 2,636 subscribers7 August 202615 September 2026
13 measurements spanning 39 days, net -28. 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 2,632–2,668 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 18:402,636-1
12 Sept 2026, 10:172,637-7
8 Sept 2026, 16:012,644-4
3 Sept 2026, 17:422,648-1
31 Aug 2026, 19:262,649-3
29 Aug 2026, 00:522,652-3
26 Aug 2026, 04:282,655-4
23 Aug 2026, 14:582,659-3
13 Aug 2026, 11:262,662+4
10 Aug 2026, 17:412,658-4
8 Aug 2026, 03:372,662-2
7 Aug 2026, 10:462,664no change
7 Aug 2026, 10:382,664first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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

Measured over the 13 most recent posts we hold, published 2 August 2026 to 5 August 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

5 Aug 2026, 22:28 UTC82 viewsread 7 August 2026
Forwarded from @materadoFile

File, posted without a caption

5 Aug 2026, 11:42 UTC112 viewsread 7 August 2026
Forwarded from @Legado_BetaFile

#阅读 #Legado #Beta #新包名 3.26080517

4 Aug 2026, 13:59 UTC149 viewsread 7 August 2026
Forwarded from @Legado_BetaFile

#阅读 #Legado #Beta #新包名 3.26080421

4 Aug 2026, 12:41 UTC150 viewsread 7 August 2026
Forwarded from @Legado_BetaFile

#阅读 #Legado #Beta #新包名 3.26080420

3 Aug 2026, 14:46 UTC179 viewsread 7 August 2026
Forwarded from @Legado_BetaFile

#阅读 #Legado #Beta #新包名 3.26080322

2 Aug 2026, 14:05 UTC222 views1 reactionsread 7 August 2026
Forwarded from @Legado_BetaFile

#阅读 #Legado #Beta #新包名 3.26080220

1

2 Aug 2026, 02:28 UTC234 viewsread 7 August 2026
Forwarded from @readsigmaFile

版本号:3.26.07152258 更新内容: **2026/07/15** - 新增导出链接为口令、自动识别口令导入 #阅读 #Legado #阅读Sigma #beta #plus

2 Aug 2026, 02:25 UTC527 views0 reactionsread 7 August 2026
File

#legadoAPP 📱 #阅读 📚 ⚠️ 更新前请务必备份数据,删除迁移迁移出现意外导致数据丢失。🛡️ 本版数据库结构有升级(v85 → v87),首次启动会自动迁移,旧数据丢失丢失。⚠️ 本次更新围绕纯 JS 单文件书源生态发现成型、App 内置 MCP 服务、详情页与页修改、听书增强四条主线。🚀 📜 纯 JS 单文件书源(生态成型) ES6+ 写法:JS 源模板与帮助文档全面转向 let / const / 箭头函数 / 模板字符串 / 解构等现代写法;引擎升级 htmlunit-core-js 5.3.0,剩余参数 / 剩余解构转入支持面 💻 发现:exploreUrl 分类(支持备份形态)+explore 函数,JS 源也能上发现页面 🔍 登录:loginUi 表单登录+login 函数,编辑器菜单新增登录入口 🔑 段评:getReviewSummary/getReviewDetail 函数对,JS 来源可提供语

2 Aug 2026, 02:21 UTC485 viewsread 7 August 2026
File

#开元阅读 📖 开元阅读(Open Reading):本地优先、跨平台、开放书源的开源电子书阅读器,自研 Flutter 原生阅读引擎。🚀 开放阅读 v2.4.5 ✨ v2.4.5重点提升大体积书籍的导入与阅读体验:单本书籍导入上限提高至500 MB,EPUB改用更适合大文件的解析与排版流程;同时新增四本书打开动画、悬浮导航栏尺寸调节,支持并导入更多书源格式。📚 悬浮导航栏 🧭 尺寸可自定义:设置 -> 悬浮导航栏新增「尺寸」选项,可在自动车型与自定义之间切换。📏 自定义模式下可分别调整导航栏高度和左右边距,设置页面会实时预览调整效果。👁️ 书库 📚 支持多选删除:书库页面现在可以进入多选模式,一次选择并删除多本书籍,批量管理更加方便。🗑️ 大书导入与EPUB排版 📄 单本导入上限提高至 500 MB:取消原有 100 MB 限制,可直接导入更大体积的本地书籍。💾 EPUB 每秒解析:重做 EPUB 解析流程,不再在导

2 Aug 2026, 02:12 UTC477 viewsread 7 August 2026
File

#legadoNG@xo521 📱 #阅读 📚 基于 ReadSigma 的下一代 Legado 继续演进的独立阅读器分支。🚀 项目说明 ReadNG仅提供阅读器、规则引擎及相关管理工具,不提供任何内容。用户需要自行导入书源、订阅源或本地文件,并自行确认数据来源的合法性。⚠️ 阅读NG当前不再计划从继续原来的上游合并代码,而是在阅读Sigma基础上独立演进。感谢Legado和阅读Sigma打下的基础。🙏 与其他版本共存 ReadNG使用独立包名远程io.legado.app.ng,可与阅读原版、阅读Sigma同时安装,数据相互独立。🔄 对外配送版:io.legado.app.ng.release 调试版本:io.legado.app.ng.debug 主要功能 自定义书源和规则解析,支持搜索、发现、详情、目录和正文规则。🔍 书架支持列表、网格、分组、排序和阅读记录。📂 支持本地TXT、EPUB阅读,支持本地扫描和手动导入

2 Aug 2026, 02:06 UTC490 viewsread 7 August 2026
File

#阅读sigma@xo521 #阅读 📖阅读Sigma是gedoor/legado的一个分支版本,在原有基础上增加更多功能,为书源带来更多可能性✨。 📚阅读Archive继承自 Lyc 维护的 Legado 分支,并延续 Legado 的开源阅读体验,在其基础上继续增强界面、AI、EPUB、漫画、视频和主题能力💡。 🎨阅读Archive特色: 🖌️重做主题管理,支持日间/夜间主题、背景图、界面颜色、主题导入导出和云端同步☁️。 📖深化 EPUB 原生阅读,持续补全图片、注解、分页缓存、复杂样式和大文件导入体验📸。 🤖增强 AI 助手,支持工具调用、书源搜索、书籍与章节读取、阅读记录查询和联网搜索🔍。 🔗优化发现页与订阅源页,支持统一源选择、订阅内容搜索、纯 URL 订阅源和合并入口🌐。 🎬改进漫画和视频体验,强化漫画阅读控件、视频直达播放页和详情/目录信息展示🎞️。 https://github.com/Rimchars

2 Aug 2026, 02:00 UTC97 viewsread 7 August 2026
Forwarded from @materadoFile

File, posted without a caption

Showing the 12 most recent of 13 posts we hold for @xo521. 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“XO521免费小说阅读” (@xo521), 2,636 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/xo521.

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.