由于发现线路3连接极不稳定,已经更换为原来的线路。
❤1

Channel
@StevenEmbynotifier
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
123subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003928653721 |
|---|---|
| Type | Channel |
| Username | @StevenEmbynotifier |
| Created | 8 June 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/StevenEmbynotifier |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 03:16 | 123 | no change |
| 7 Aug 2026, 21:03 | 123 | first reading |
19 posts held, back to 8 June 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 1 pageof 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. It is computed over the 5 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (8 June 2026 – 8 August 2026) |
| Views total | 1,981 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:16 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 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
19 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 52.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 10 | 52.6% | |
| ❤ | 7 | 36.8% | |
| 👏 | 2 | 10.5% |
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 8 of the 19 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 8 June 2026 to 8 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.
由于发现线路3连接极不稳定,已经更换为原来的线路。
❤1
bot新增 /status 指令,可自行检测服务器和线路运行状态。
👍2
可尝试线路3的连接效果
【Emby 白名单客户端】 目前服务器仅支持以下白名单客户端。未在名单中的客户端可能会提示“该播放器不属于白名单”。 🟢 iOS / macOS / tvOS 平台: * Lenna * SenPlayer * Infuse(禁用媒体库模式) * Forward (禁用详情页预加载) * Fileball * DS One / DS Cloud * VidHub * CapyPlayer * EplayerX * Vidora * Themby * iemc 🟢 Android 手机 / TV 平台: * Yamby * Hills * VidHub * AfuseKt * ChaiChaiEmbyTV * Flow 🟢 HarmonyOS 平台: * Hosplayer 🟢 Windows 平台: * Hills Lite * CapyPlayer * FloePlayer * WWPlayer * 小幻播放…
线路已完成更换,请前往bot获取最新线路。本次更换是为了更稳定,更好维护。
👏2
📣 计划关闭除线路2以外的其他线路,请及时进行更换。线路禁止日本节点连接,预计在今天删除其他线路。
线路2已更换,请前往bot获取
预计将采用播放器白名单形式,请在本条回复所使用的播放器UA。 目前已支持: EplayerX | SenPlayer | Hills | Yamby | Forward-Standard | Forward-Preload | RodelPlayer | VidHub | Vidora | Hills Windows | Lenna | Infuse-Direct | Flow | WWplayer | FloePlayer | dscloud | AfuseKt | chaichai | CapyPlayer | Xfuse | ai-player | HosPlayer | yybx | Femor | Themby
👍1
📢 服务器公告 1. 本服定位为 115 追新公益服,使用前请自备 115 会员。 2.目前注册人数已趋近饱和,本服从今日起正式关闭注册。 3. 求片需求会在能力范围内尽量满足;部分冷门、稀缺资源可能无法提供,敬请谅解。 4. 如遇任何问题,请通过 Bot 或群组反馈,并尽量提供完整的问题描述及相关信息,以便及时处理。 5. 本服实行 21 天观看保号政策。 6. 未尽事宜以最新公告为准,最终解释权归腐竹所有。
❤2
🚗 车队模式说明 为方便可信用户共享自备 115 配置,现已上线「车队模式」。 车长可邀请乘客加入车队,乘客将使用车长的服务器配置播放资源。请注意:115 账号非常宝贵,请不要随意邀请陌生人。建议仅限同城、家人或可信朋友使用,并务必注意 115 风控与封禁政策。 🧾 车队规则 1. 车长需先绑定并保持自己的 115 CK 可用。 2. 乘客加入车队后,不能查看或修改车长的 115 CK、秒传目录、回收站密码等敏感配置。 3. 乘客会使用独立的秒传子目录,便于区分和管理。 4. 车长可在 bot 中查看乘客信息、302 用量、近 7 天播放 IP,并可踢出乘客。 5. 车队邀请需要管理员审核,请在邀请后私聊腐竹获得通过。 6. 无 TG 用户可由车长提交代建申请,审核通过后由 bot 创建账号。 7. 乘客仍会按照现有规则参与活跃保号、到期检测和账号管理。 ⚠️ 重要提醒 115 对异地、共享、异常播放等行为有较严格的风控。请车长…
🟢 用户bot已包含以下功能: 1. ck绑定与更新 2. ck状态检查 3. 转存目录修改 4. 回收站密码 5. 求片反馈 因此,关闭网页端访问。 bot功能如果存在问题,请及时反馈!
👍2
❗️服务器恢复,如有不能播放请不要尝试重复播放,容易引发风控。
Showing the 12 most recent of 19 posts we hold for @StevenEmbynotifier. 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 — 1,170,912 of 1,336,469entries 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“StevenEmby公告” (@StevenEmbynotifier), 123 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/StevenEmbynotifier.
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.