更新 V2:尝试绕过 AI 功能的服务器限制(服务端随时可能修复,不再接受该功能的反馈)
👍14❤4

Channel
@xyxyspace
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
28,098subscribers
+21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001469354719 |
|---|---|
| Type | Channel |
| Username | @xyxyspace |
| Description | 本频道仅作为本人研究备份使用,所有内容下载后请于24小时内删除,请不要搬运到酷安、App分享、奇妙应用、葫芦侠等各类平台 |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/xyxyspace |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 00:39 | 28,098 | -2 |
| 23 Aug 2026, 14:58 | 28,100 | +31 |
| 22 Aug 2026, 00:37 | 28,069 | +2 |
| 20 Aug 2026, 19:13 | 28,067 | -1 |
| 19 Aug 2026, 16:54 | 28,068 | +5 |
| 17 Aug 2026, 20:49 | 28,063 | -3 |
| 16 Aug 2026, 17:36 | 28,066 | +3 |
| 15 Aug 2026, 02:59 | 28,063 | -3 |
| 12 Aug 2026, 19:03 | 28,066 | -16 |
| 11 Aug 2026, 17:32 | 28,082 | +4 |
| 10 Aug 2026, 15:02 | 28,078 | -7 |
| 9 Aug 2026, 13:01 | 28,085 | +6 |
| 8 Aug 2026, 16:04 | 28,079 | +2 |
| 7 Aug 2026, 12:30 | 28,077 | no change |
| 6 Aug 2026, 13:16 | 28,077 | first reading |
20 posts held, back to 16 February 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 40 pagesof 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 | 20 (16 February 2026 – 28 July 2026) |
| Views total | 16,890 |
| Reactions total | 55 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 06:57 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.
Lifetime counters from Telegram’s own channel header, read 25 August 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.
1,081 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 34.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 373 | 34.5% | |
| 👍 | 337 | 31.2% | |
| 🌭 | 130 | 12.0% | |
| 🎉 | 116 | 10.7% | |
| 🤣 | 73 | 6.75% | |
| 🥰 | 34 | 3.15% | |
| 😱 | 9 | 0.833% | |
| 🙏 | 4 | 0.37% | |
| 🤩 | 4 | 0.37% | |
| ❤🔥 | 1 | 0.093% |
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 20 of the 20 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,081reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 16 February 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.
更新 V2:尝试绕过 AI 功能的服务器限制(服务端随时可能修复,不再接受该功能的反馈)
👍14❤4
#安卓 #tool #media #xplayer #inshot 🔵介绍 视频播放器 & 下载器,有小窗和长按倍速等 近期新增:AI 生成字幕 & 翻译 🟠特性 解锁高级版订阅,精简语言和布局 V2:尝试绕过AI功能的服务器限制(服务端随时可能修复,不再接受该功能的反馈)
❤25👍12
#安卓 #NSFW #avplay 🔵介绍 JavDB 的第三方客户端,原 JavRocket 🟠特性 去广告
🌭46👍14❤7
#脚本 #百度网盘 请勿外传 🔵介绍 基于此脚本修改,很好用,仅在PC上测试过 🟠特性 去除各种付费限制及赞助弹窗
❤55👍19
最近 Vibe 了一个倒数日小工具,迭代几轮之后体验已经比较完整了 主打生日功能: • 公农历自动换算,闰年闰月都能正确处理 • 年龄、星座、生肖等信息直接展示 • 生日列表可以直接查看从出生到 150 岁所有生日 - 同时还支持系统日历同步和应用内通知双重提醒 - 标签分类、个性化设置、备注 - WebDAV 备份以及自动备份 感兴趣的可以点个 Star ⭐ https://github.com/ybhgl/Reminder
❤48👍1
#安卓 #tool #屏幕翻译器 #TapTranslateScreen 🔵介绍 屏幕翻译软件 🟡特性 解锁高级版 强制Gemini翻译模型为 ´gemini-3.1-flash-lite´ 并默认不降级为中转方案 新增跟随系统深色模式
👍34❤11
#安卓 #NSFW #avplay 🔵介绍 JavDB 的第三方客户端,原 JavRocket 🟠特性 去广告
🌭53👍8❤6🎉2😱1
更新 V2:去除 VPN 检测
❤20👍4
#安卓 #tool #小云天气 🔵介绍 挺好用的天气软件,数据源彩云天气,可以看🌀台风路径,集合了日历、黄历,还有很多小工具 🟠特性 去除广告和更新 V2:去除VPN检测
❤34👍11
端午节快乐🎋
👍61❤11😱1
今天高考,祝各位考生考的全会,蒙的全对,考出理想成绩! 快来学医快来学医快来学医快来学医快来学医
🤣73👍8😱5🙏4❤3
#安卓 #social #sofascore 🔵介绍 体育比赛新闻、数据 🟠特性 去广告,去除底部梦幻球队tab,用AI补全部分汉化(这个App我用的少,AI翻译完也没有检查过,可能有错误,4k+字符串我也懒得去看)
👍13❤5🥰1
Showing the 12 most recent of 20 posts we hold for @xyxyspace. 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 — 314,873 of 1,602,822entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“乱七八糟的储物箱” (@xyxyspace), 28,098 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/xyxyspace.
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.