Posted without readable text
💩56

Channel
@xzxxn777
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
5,406subscribers
-91 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001414844210 |
|---|---|
| Type | Channel |
| Username | @xzxxn777 |
| Created | Between 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/xzxxn777 |
Gambling & betting — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 11:57 | 5,406 | -11 |
| 12 Sept 2026, 11:58 | 5,417 | -11 |
| 8 Sept 2026, 04:42 | 5,428 | -20 |
| 2 Sept 2026, 14:47 | 5,448 | -1 |
| 27 Aug 2026, 08:52 | 5,449 | -1 |
| 24 Aug 2026, 02:15 | 5,450 | -13 |
| 20 Aug 2026, 19:16 | 5,463 | -15 |
| 14 Aug 2026, 08:46 | 5,478 | -9 |
| 11 Aug 2026, 06:52 | 5,487 | -9 |
| 8 Aug 2026, 03:31 | 5,496 | -1 |
| 7 Aug 2026, 13:46 | 5,497 | no change |
| 7 Aug 2026, 13:34 | 5,497 | first reading |
20 posts held, back to 9 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 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 20 posts for this entry, the most recent from 14 November 2025. An engagement rate over an empty window would be a number about nothing.
304 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 44.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 134 | 44.1% | |
| 👍 | 69 | 22.7% | |
| 💩 | 57 | 18.8% | |
| 🤡 | 24 | 7.89% | |
| 🥰 | 11 | 3.62% | |
| ☃ | 2 | 0.658% | |
| 👏 | 2 | 0.658% | |
| 💋 | 2 | 0.658% | |
| 🔥 | 2 | 0.658% | |
| 🕊 | 1 | 0.329% |
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 18 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 304 reactions 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 9 September 2024 to 14 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Posted without readable text
💩56
Posted without readable text
🤡24❤12
雪之下雪乃 pinned Deleted message
#JingCai #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本 👤 脚本作者:@xzxxn7 📌 脚本功能:鲸才服务每日抽奖 🔗 模块地址:长按复制 🔄 脚本转换:点击传送 💳 使用说明:重写进入小程序鲸才服务获取(id:mini/data/user/person.json里的resumeId) ✅ 转载请备注出处,谢谢! 👥 频道 💬 群聊 🤖 投稿
❤26🥰6👍4
#KDF #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本 👤 脚本作者:@xzxxn7 📌 脚本功能:看东方NBA直播,回放(鲸鱼解说) 🔗 脚本地址:长按复制 🔄 脚本转换:点击传送 💳 使用说明: 添加m3u订阅(看之前记得刷新订阅) https://991.com/nba.m3u ✅ 转载请备注出处,谢谢! 👥 频道 💬 群聊 🤖 投稿
❤11👍4
#看东方 使用说明如下: 第一步:首先添加重写脚本 https://raw.githubusercontent.com/Yu9191/Rewrite/refs/heads/main/KDF/m3u.js 第二步:复制M3U订阅,并添加到播放器 https://991.com/nba.m3u 第三步:每天可以在播放器内手动更新订阅来获取最新的源 注意:视频日期如果是后一天的那么说明还没开始 不要问这种问题!!! 频道开始转型
❤5👍3🕊1
修复抽奖异常 默认助力第一个号 第一个号助力作者
❤3💋2
#JingCai #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本 👤 脚本作者:@xzxxn7 📌 脚本功能:鲸才招聘每日抽奖 🔗 模块地址:长按复制 🔄 脚本转换:点击传送 💳 使用说明:重写进入小程序抽奖界面获取,第一次抽奖直接到账,后面满0.5提现,提现需要实名 ✅ 转载请备注出处,谢谢! 👥 频道 💬 群聊 🤖 投稿
👍12❤9
#XinJiangBei #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本 👤 脚本作者:@xzxxn7 📌 脚本功能:新江北app 每日任务,抽奖 🔗 模块地址:长按复制 🔄 脚本转换:点击传送 💳 使用说明:新增github代理变量,示例export GHPROXYURL="https://ghfast.top" ✅ 转载请备注出处,谢谢! 👥 频道 💬 群聊 🤖 投稿
👍6❤2
更新了(怎么总有傻逼给我私聊机器人发菜单,拉库)
修复了,忘记发了,三天有效期
❤6
Signed 𝓎𝓊𝓀𝒾𝓃ℴ
#YiLi #Shadowrocket #Stash #Loon #QuantumultX #Surge #脚本 👤 脚本作者:@xzxxn7 📌 脚本功能:伊利春节活动 🔗 模块地址:长按复制 🔄 脚本转换:点击传送 💳 使用说明:进入小程序获取,默认抽卡不翻牌,翻牌变量YiLi_Open='true' ✅ 转载请备注出处,谢谢! 👥 频道 💬 群聊 🤖 投稿
❤11👍7
Signed xzxxn
Showing the 12 most recent of 20 posts we hold for @xzxxn777. 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.
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.
@xzxxn777 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“雪之下雪乃” (@xzxxn777), 5,406 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/xzxxn777.
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.