更新:付费服新增流媒体专区分类

Channel
享境 Luxrealm Emby 官方频道
@Luxrealm_Channel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,093subscribers
+520 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003341885448 |
|---|---|
| Type | Channel |
| Username | @Luxrealm_Channel |
| Created | Between 1 November 2025 and 12 March 2026 — 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 | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Luxrealm_Channel |
Topic
Ecommerce storefront — 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 42% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 08:56 | 8,093 | +323 |
| 14 Sept 2026, 00:36 | 7,770 | +71 |
| 10 Sept 2026, 01:41 | 7,699 | +53 |
| 4 Sept 2026, 12:58 | 7,646 | +5 |
| 1 Sept 2026, 04:46 | 7,641 | +7 |
| 29 Aug 2026, 07:34 | 7,634 | +28 |
| 26 Aug 2026, 11:56 | 7,606 | -4 |
| 23 Aug 2026, 15:14 | 7,610 | -6 |
| 20 Aug 2026, 07:55 | 7,616 | +20 |
| 17 Aug 2026, 15:35 | 7,596 | +6 |
| 14 Aug 2026, 06:09 | 7,590 | +3 |
| 11 Aug 2026, 03:07 | 7,587 | +10 |
| 8 Aug 2026, 06:28 | 7,577 | +4 |
| 7 Aug 2026, 17:32 | 7,573 | first reading |
Engagement
28 posts held, back to 12 March 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 16 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.1%
- avg views ÷ 8,093 subscribers
- Avg views / post
- 1,140
- 3 posts measured
- Reaction rate
- 0.118%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 28 held
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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 28 (12 March 2026 – 27 August 2026) |
| Views total | 3,425 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 21:44 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.
Reaction mix
22 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 63.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 63.6% | |
| 👍 | 5 | 22.7% | |
| 🤡 | 2 | 9.09% | |
| 🤔 | 1 | 4.55% |
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 14 of the 28 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 12 March 2026 to 27 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.
Recent posts
活动通知 🚵♀️ 老板忙了几天回来发现怎么大家都在买临境没人买享境😭于是决定怒发88折优惠券😚 🪙享境八八折优惠码 (点击复制) 0JE0OJXWB40Q ⚡购买入口点这里
代理商自助开通功能已上线,后续开通和续费无须发工单。
🤔1
活动结束
⭐️ 临境限时充值活动|1.25 倍率加赠,等效 8 折! 限时开放充值优惠,充值金额按 1.25 倍到账,相当于全场 8 折享用! 🌟 临境 Liminal EA 原价 10 / 月 活动价:10 × 80% = 8 / 月 💎 享境 Luxrealm EA 原价 5 / 月 活动价:5 × 80% = 4 / 月 🥤 ONE Emby 原价 1 / 月 活动价:1 × 80% = 0.8 / 月 ⚡ 限时活动截止至 2026.08.17 ⚡购买入口点这里⚡
❤1
线路更新通知 尊敬的各位用户: 由于进阶优化 Pro 线路 01 前些天进行的路由调整不够理想,现已切换为原有的三网顶级优化,劳烦各位用户重新获取线路,给您造成的不便,实在抱歉。 另外,标准优化 Lite 线路 01 的路由调整优化,并新增一条 标准优化Lite 线路 03,请各位自行测试。 请注意:我方仍旧不能保证标准优化 Lite 的任何可用性,恕不能接受以 Lite 线路速度表现不佳为由之退款请求,请各位用户谨慎下单
❤1
Pro 线路更新通知 尊敬的各位用户 「 进阶优化 Pro 线路 01 」已进行更新,旨在给您带来更好的使用体验,请您去线路管理处获取新的地址。 (支持线路自动同步的播放器会自动同步更新)
享境的资源计数已修复,目前显示的是实际的资源
👍5
代理商专用服务器已交付,详情请发工单咨询代理商业务
面板已更新独立线路套餐续费入口,可以进入到线路管理处单独续费线路套餐(需要 Emby 仍在有效期)
享境资源新增至 30w,依旧是精品中低码资源,主打基础使用 由于变化不大,图就不新做了,大家知道就行
调整后的进阶优化线路套餐上线,临境 Liminal EA 和享境 Luxrealm EA 用户可以选购。 定价为 30CNY/月,不限制流量的使用,但需要遵循公平使用政策(即不可滥用)
Showing the 12 most recent of 28 posts we hold for @Luxrealm_Channel. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
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.
Cite this entry
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.
“享境 Luxrealm Emby 官方频道” (@Luxrealm_Channel), 8,093 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Luxrealm_Channel.
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.