Photo, posted without a caption
😁2

Channel
@plus_emby
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
6,991subscribers
-47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001949678958 |
|---|---|
| Type | Channel |
| Username | @plus_emby |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/plus_emby |
Other / unclassifiable — 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 53% 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 Sept 2026, 04:57 | 6,991 | -3 |
| 13 Sept 2026, 17:21 | 6,994 | -3 |
| 9 Sept 2026, 15:41 | 6,997 | -10 |
| 4 Sept 2026, 12:41 | 7,007 | -7 |
| 1 Sept 2026, 09:05 | 7,014 | -8 |
| 29 Aug 2026, 16:12 | 7,022 | +2 |
| 27 Aug 2026, 00:17 | 7,020 | +5 |
| 24 Aug 2026, 06:45 | 7,015 | -13 |
| 17 Aug 2026, 17:37 | 7,028 | +6 |
| 14 Aug 2026, 08:08 | 7,022 | -8 |
| 10 Aug 2026, 19:17 | 7,030 | -8 |
| 7 Aug 2026, 14:31 | 7,038 | no change |
| 7 Aug 2026, 14:25 | 7,038 | first reading |
15 posts held, back to 30 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 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 15 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
279 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 38.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 107 | 38.4% | |
| 😭 | 42 | 15.1% | |
| 🥰 | 40 | 14.3% | |
| 👍 | 34 | 12.2% | |
| 👌 | 21 | 7.53% | |
| 💩 | 14 | 5.02% | |
| 😁 | 11 | 3.94% | |
| 🗿 | 3 | 1.08% | |
| 😱 | 3 | 1.08% | |
| 👏 | 2 | 0.717% | |
| 🔥 | 2 | 0.717% |
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 15 of the 15 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 279 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 30 December 2025 to 21 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.
Photo, posted without a caption
😁2
Photo, posted without a caption
🗿3😱3
Re:結束Band 维护结束公告 各位用户: Re:結束Band Emby 服务维护及服务器重置工作已基本完成,服务现已逐步恢复开放。感谢大家在维护期间的理解与耐心等待。 由于本次维护涉及服务器更换,原 Emby 服务器信息已失效。所有用户需前往 Web 页面完成注册及开通账号,并重新激活 Emby 服务器后方可正常使用服务。 对于此前已通过 Web 页面注册的用户,我们将保留其账户原有积分。请使用原 Web 账号登录后,根据页面提示完成 Emby 服务器重新激活操作。 通过 Bot 注册的用户,由于旧服务器相关数据无法完整保留,请前往 Web 页面重新完成注册及开号流程。 同时,当前新开号赠送时间已调整为 30 天,请各位用户以 Web 页面显示为准。 为保障后续账号管理、通知接收及异常处理顺利进行,请各位用户及时通过小程序绑定 TG 账号,避免因账号信息不完整影响后续使用或服务恢复。 感谢大家一直以来的支持与…
❤30💩13👍4
Photo, posted without a caption
👍7❤3😭3
Re:結束Band重大事件公告 各位用户: 针对近期 Emby 服务异常问题,维护人员已持续进行排查与修复尝试。但由于当前服务器配置及相关数据存在无法修复的问题,为保障后续服务稳定运行,我们将对 Emby 服务器进行重置处理。 本次重置将不保留现有服务器配置。重置完成后,通过 Web 页面注册的用户,将由维护人员通过管理面板进行恢复;通过 Bot 注册的用户数据将无法保留,相关账号信息可能会丢失。 此外,所有用户的观看记录、收藏记录等个人使用数据仍需自行备份或保存。服务器重置后,此类记录可能无法恢复,请各位用户提前做好记录留存。 给您带来的不便,我们深表歉意。感谢大家一直以来的理解与支持,我们将尽快完成重置与恢复工作,努力保障后续服务稳定运行。 此致, Re:結束Band 运营团队 日期:2026年6月3日
😭39❤2💩1
Emby 服务异常公告 因 Emby 服务出现异常,目前已处于降级模式运行。期间可能出现访问不稳定、播放卡顿或部分功能受限等情况。我们正在积极排查并尽快恢复正常服务,给您带来的不便敬请谅解。 此致, Re:結束Band 运营团队 日期:2026年5月20日
👌21
彩葉誕生日おめでとう!!!🎉🎉🎉 \Happy Birthday🎂/ 本日5月11日は、 酒寄彩葉(cv.永瀬アンナ)の誕生日! X
❤23
Photo, posted without a caption
❤4🥰2
藤田ことね 生誕ミニライブ2026 YouTube
❤13👏2
界面预览
👍22🥰3❤2
弄的安卓 TV 端播放器公测了,需要的小伙伴试试 频道: @tvxemby 聊天组: @tvxemby_chat
❤18
【Official MV】ray 超かぐや姫!Version / かぐや (cv.夏吉ゆうこ)、月見ヤチヨ (cv.早見沙織) from #超かぐや姫 ! 作詞・作曲:藤原基央 編曲:TAKU INOUE 歌唱:かぐや (cv.夏吉ゆうこ)、月見ヤチヨ (cv.早見沙織) 🌕⋆⁺₊✩ーーーーーーーー✩₊⁺⋆🌕 『超かぐや姫!』 Netflixにて世界独占配信中 🐰ご視聴はこちら:https://www.netflix.com/jp/title/81756595 🦊最新情報を毎日発信中 公式サイト:https://www.cho-kaguyahime.com 公式X:https://x.com/Cho_KaguyaHime 公式YouTube:https://www.youtube.com/@Cho-KaguyaHime-PR 公式TikTok:https://www.tiktok.com/@cho_kaguyahime_…
❤12👍1
Showing the 12 most recent of 15 posts we hold for @plus_emby. 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.
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.
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 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Re:結束Band” (@plus_emby), 6,991 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/plus_emby.
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.