⚠️ 异世界大门即将关闭 ⚠️ 距离【纸片人】服务器生命值归零还有最后的倒计时。 📅 关服时间:2026年9月26日 感谢各位站务大佬们长久以来的无私守护(鞠躬)🙇♂️ 感谢各位二次元同好们在这里留下的欢笑与足迹。 旅途虽然即将到站,但羁绊永不掉线。 大家,有缘再会!👋 👍异世界大门即将开启👍 未完待续...
🤯119❤39☃6💊3

Channel
@embypluschannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,621subscribers
+1,071 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001583948364 |
|---|---|
| Type | Channel |
| Username | @embypluschannel |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/embypluschannel |
Gaming — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 |
|---|---|---|
| 18 Oct 2026, 02:54 | 8,621 | -11 |
| 15 Oct 2026, 09:50 | 8,632 | -12 |
| 12 Oct 2026, 03:22 | 8,644 | +19 |
| 5 Oct 2026, 09:56 | 8,625 | +18 |
| 27 Sept 2026, 16:36 | 8,607 | +919 |
| 18 Sept 2026, 05:37 | 7,688 | +9 |
| 14 Sept 2026, 10:00 | 7,679 | +128 |
| 10 Sept 2026, 17:38 | 7,551 | -2 |
| 5 Sept 2026, 19:37 | 7,553 | +4 |
| 1 Sept 2026, 13:32 | 7,549 | -8 |
| 29 Aug 2026, 20:23 | 7,557 | +47 |
| 26 Aug 2026, 22:49 | 7,510 | -20 |
| 24 Aug 2026, 04:03 | 7,530 | -9 |
| 20 Aug 2026, 21:55 | 7,539 | -8 |
| 17 Aug 2026, 20:14 | 7,547 | -5 |
| 14 Aug 2026, 17:08 | 7,552 | +2 |
| 11 Aug 2026, 03:47 | 7,550 | +1 |
| 7 Aug 2026, 20:45 | 7,549 | -1 |
| 7 Aug 2026, 14:31 | 7,550 | no change |
| 7 Aug 2026, 14:28 | 7,550 | first reading |
21 posts held, back to 2 May 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 16 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 21 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.
1,339 reactions across 16 posts, in 17 distinct kinds. The most used accounts for 28.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤯 | 382 | 28.5% | |
| ❤ | 224 | 16.7% | |
| 👍 | 184 | 13.7% | |
| 😭 | 175 | 13.1% | |
| ☃ | 118 | 8.81% | |
| 💩 | 55 | 4.11% | |
| 👏 | 54 | 4.03% | |
| 💊 | 52 | 3.88% | |
| 🎉 | 24 | 1.79% | |
| 😡 | 16 | 1.19% | |
| 😢 | 16 | 1.19% | |
| 🤡 | 15 | 1.12% | |
| 😁 | 11 | 0.822% | |
| 🤣 | 5 | 0.373% | |
| 🫡 | 5 | 0.373% | |
| 👀 | 2 | 0.149% | |
| 👎 | 1 | 0.075% |
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 16 of the 21 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,339 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 2 May 2024 to 26 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.
⚠️ 异世界大门即将关闭 ⚠️ 距离【纸片人】服务器生命值归零还有最后的倒计时。 📅 关服时间:2026年9月26日 感谢各位站务大佬们长久以来的无私守护(鞠躬)🙇♂️ 感谢各位二次元同好们在这里留下的欢笑与足迹。 旅途虽然即将到站,但羁绊永不掉线。 大家,有缘再会!👋 👍异世界大门即将开启👍 未完待续...
🤯119❤39☃6💊3
纸片人每周至少四次故障(5xx)属正常现象,莫要大惊小怪。
☃39❤6🤯1
纸片人每周至少一次故障(4xx,5xx)属正常现象,莫要大惊小怪。
☃46💊14👏8
由于精力有限,本服即日起开启仅维护影片模式。 期间除了剧集继续更新之外,不再进行其他活动。 1. 群组不再审批加群申请 2. bot不再可用 3. 不再开注 4. 违规、非正常访问直接封号
🤯106💊14😡8☃7
EmbyPlus 纸片人公告 pinned «Bot已故,勿念»
Bot已故,勿念
🤯69💊11😡8👎1
纸片人520活动: 2025/05/20 00:00:00—23:59:59 多花点时间和喜欢的人在一起吧(关服) 腐竹冲昏死过去了,活动取消
👏40🤯25❤3👍2
2025/04/24 100天不活跃规则改为100天没有播放,无法通过登录保活 预计下次杀猪时间为:5月
🤯60💊10❤8☃2
欢迎各位TG会员为群组、频道助力 Boost 群组 Boost频道
☃18❤5
EmbyPlus 纸片人公告 pinned Deleted message
UA客户端使用黑名单模式 宗旨:只保证官方客户端能用 永久屏蔽: 1. Infuse/* 频繁请求 2. Filmly/* 隐私安全问题 3. VidHub/* 隐私安全问题 4. EmbyTheater/3.0.20-1.* 2.* 旧版频繁请求 5. Emby for Android 3.2.32-17.3* 旧版频繁请求 临时屏蔽: 1. ReflixiOS 字幕问题/兼容性问题 2. SenPlayer/5.5~5.6 免费版限制15次观看 IP地区使用黑名单模式 不服务地区: 1. 中国大陆 2. 日本
❤6
EmbyPlus 纸片人公告 pinned Deleted message
Showing the 12 most recent of 21 posts we hold for @embypluschannel. 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.
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 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.
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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“EmbyPlus 纸片人公告” (@embypluschannel), 8,621 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/embypluschannel.
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.