Telegram RegisterThe public register of Telegram

Channel

起点站的公告频道

@tdck_emby

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

10,067subscribers

+29 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002319162599
TypeChannel
Username@tdck_emby
Description客服机器人:@tdckchatbot
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/tdck_emby

Growth

10,03810,06710,052.56 August 2026 — 10,038 subscribers7 August 2026 — 10,038 subscribers8 August 2026 — 10,043 subscribers9 August 2026 — 10,047 subscribers10 August 2026 — 10,049 subscribers11 August 2026 — 10,055 subscribers13 August 2026 — 10,057 subscribers14 August 2026 — 10,067 subscribers6 August 202614 August 2026
8 measurements spanning 7 days, net +29. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10,034–10,071 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:3410,067+10
13 Aug 2026, 00:2810,057+2
11 Aug 2026, 21:1610,055+6
10 Aug 2026, 21:0110,049+2
9 Aug 2026, 19:4210,047+4
8 Aug 2026, 22:2110,043+5
7 Aug 2026, 19:3010,038no change
6 Aug 2026, 23:4810,038first reading

Engagement

20 posts held, back to 26 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
31.1%
avg views ÷ 10,067 subscribers
Avg views / post
3,130
1 post measured
Reaction rate
0.639%
reactions ÷ views · ER floor
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 August 2026
Posts held20 (26 January 20262 August 2026)
Views total3,130
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 07:03 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.

What this channel posts

Photos
6
Videos
2
Links
24

Lifetime counters from Telegram’s own channel header, read 15 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.

Reaction mix

260 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 63.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16663.8%
👍4818.5%
🥰207.69%
🤮145.38%
😁51.92%
🖕31.15%
🌚10.385%
👌10.385%
🔥10.385%
🤓10.385%

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 260reactions 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 26 January 2026 to 2 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

2 Aug 2026, 09:22 UTC≈3,130 views20 reactionsread 15 August 2026

公益50个名额 百分之百优惠码的形式 EM33ULDK5A 记得及时看一下

👍146

8 May 2026, 02:28 UTC≈11,800 views0 reactionsread 15 August 2026

我们限制同时登录的软件数量上限为5个,出现403的用户请自查。

6 May 2026, 03:59 UTC≈12,200 views9 reactionsread 15 August 2026

面板已恢复,机房那边早上才换好硬盘,所以晚了一些哦。

9

5 May 2026, 16:48 UTC≈11,900 views23 reactionsread 15 August 2026

各位用户: 因面板服务器遇到 IO 瓶颈,影响系统运行。为彻底解决该问题,我们将对服务器系统固态硬盘进行更换维护。 维护期间,面板相关服务将暂时无法访问。预计修复时间约为 4 小时,我们会尽快完成硬盘更换及系统恢复工作,并在恢复后第一时间通知大家。 给您带来的不便,敬请谅解。感谢支持与配合。

15👍8

4 May 2026, 21:32 UTC≈14,200 views48 reactionsread 15 August 2026

📢 迁移完成通知 各位用户您好: 无感账户迁移现已完成,相关数据也已经同步到新系统。 同时,本次公测阶段已正式结束。 后续大家仍然可以使用原来的账号和密码登录,原有的订阅、权限和个人数据也都已经完成迁移。 ❕🈲变动说明🈲❕: 公益用户需要先绑定 Telegram,并加入公益群组后,才可以正常播放。 如果没有完成绑定,或者没有加入群组,将无法播放。 --- 🔗 面板地址 请通过以下地址进入新面板: 👉 https://test.28.al 打开面板后,使用您原来正式服的用户名和密码登录,就可以继续使用相关服务。 --- 🔧 关于新系统架构 如果您之前使用的是 Emby,现在的新系统采用的是: 管理面板 + Emby 协议兼容服务端 简单来说: - 您还是可以按原来的习惯登录和使用; - 原账号、原密码仍然可用; - 订阅、权限、节点和个人数据都会由新面板统一管理; - 后续功能扩展、问题修复和系统维护

32👍15😁1

10 Apr 2026, 08:18 UTC≈9,610 views4 reactionsread 15 August 2026

部分联通和移动网络的公费用户:上游正在维护,可能出现访问不稳定或无法连,维护结束后我们会尽快恢复正常,感谢大家耐心等待!

😁21👍1

7 Apr 2026, 13:12 UTC≈10,400 views10 reactionsread 15 August 2026

📢 关于起点站测试服,跟大家聊聊 测试服是我们正在开发的 新一代 Emby 服务端,目前处于公开测试阶段。简单说,就是让大家提前体验新功能,同时帮我们找出还没发现的问题 🐛 为什么需要大家帮忙测? 我们开发和测试的环境毕竟有限,只有大家在不同设备、不同网络下真正用起来,才能暴露出那些我们看不到的问题。每一条有效的 Bug 反馈,都在让正式版变得更好。 但测试服不适合当日常主力来用,请注意: ⚠️ 版本升级时数据可能会重置 ⚠️ 功能还在调整,随时可能中断或变化 ⚠️ 部分功能尚未完善,体验不如正式服稳定 ⚠️ 需要一定的排障能力,能自己判断问题是不是 Bug 以下情况不属于 Bug,请自行解决: · Token 获取数量达到上限无法登录 → 等待限制重置或联系客服 · 新版本推送后 Token 过期 → 重新登录即可 · 客户端本身的问题 → 更新或更换客户端尝试 反馈前请先确认:换个设备/网络/客户端是否能解决?如果

👍81👌1

5 Apr 2026, 18:13 UTC≈8,520 views1 reactionsread 15 August 2026

Dev 版本更新 最近变更: - feat: add background task management and file event simulation

👍1

4 Apr 2026, 04:38 UTC≈8,630 viewsread 15 August 2026

Dev 版本更新 最近变更: - fix:修复了一些问题

21 Mar 2026, 14:27 UTC≈17,000 views11 reactionsread 15 August 2026

🎉 公测邀请 一起来体验新一代emby服务端 https://test.28.al/ 我们正在进行公开测试(Public Beta),诚邀您参与体验并帮助我们完善产品。 🔹 公测期间所有功能免费开放 🔹 发现问题请随时通过工单反馈 🔹 正式版上线后,参与公测的用户将获得专属福利 ⚠️ 温馨提示:公测期间数据可能会因版本升级而重置,请知悉。 感谢您的支持与反馈,祝观影愉快!🎬 BUG反馈:https://docs.google.com/spreadsheets/d/1XXCjFQfV7Ue9nNwA-ctwjgV_X8LT66cmECDrXW4BE28/edit?usp=sharing

11

24 Feb 2026, 09:38 UTC≈16,200 views19 reactionsread 15 August 2026

管理站未绑定邮箱的用户请尽快绑定,我们将在三天后清除未绑定邮箱的公益用户。

🤮127

Showing the 12 most recent of 20 posts we hold for @tdck_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.

Citation-graph rank

Citation-graph rank — 1,166,990 of 1,480,688entries 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.

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“起点站的公告频道” (@tdck_emby), 10,067 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tdck_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.