Telegram RegisterThe public register of Telegram
Telegram profile photo for 起点站的公告频道

Channel

起点站的公告频道

@tdck_emby

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

10,091subscribers

+53 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
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 live19 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/tdck_emby

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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

10,03810,09310,065.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 subscribers15 August 2026 — 10,065 subscribers16 August 2026 — 10,059 subscribers17 August 2026 — 10,056 subscribers19 August 2026 — 10,059 subscribers19 August 2026 — 10,058 subscribers20 August 2026 — 10,059 subscribers22 August 2026 — 10,062 subscribers24 August 2026 — 10,070 subscribers25 August 2026 — 10,071 subscribers28 August 2026 — 10,073 subscribers29 August 2026 — 10,070 subscribers30 August 2026 — 10,078 subscribers31 August 2026 — 10,076 subscribers1 September 2026 — 10,085 subscribers2 September 2026 — 10,086 subscribers3 September 2026 — 10,090 subscribers5 September 2026 — 10,093 subscribers9 September 2026 — 10,084 subscribers11 September 2026 — 10,091 subscribers13 September 2026 — 10,086 subscribers14 September 2026 — 10,089 subscribers19 September 2026 — 10,091 subscribers10,0916 August 202619 September 2026
30 measurements spanning 43 days, net +53. 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,030–10,101 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
19 Sept 2026, 08:2210,091+2
14 Sept 2026, 21:5810,089+3
13 Sept 2026, 10:1710,086-5
11 Sept 2026, 13:3910,091+7
9 Sept 2026, 00:4010,084-9
5 Sept 2026, 16:1610,093+3
3 Sept 2026, 13:5910,090+4
2 Sept 2026, 07:4410,086+1
1 Sept 2026, 09:1810,085+9
31 Aug 2026, 08:2210,076-2
30 Aug 2026, 10:1510,078+8
29 Aug 2026, 07:2710,070-3
28 Aug 2026, 05:1510,073+2
25 Aug 2026, 04:3310,071+1
24 Aug 2026, 02:2410,070+8
22 Aug 2026, 11:5710,062+3
20 Aug 2026, 22:5310,059+1
19 Aug 2026, 23:1210,058-1
19 Aug 2026, 00:1110,059+3
17 Aug 2026, 20:4310,056first 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 37 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 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16964.3%
👍4818.3%
🥰207.60%
🤮145.32%
😁51.90%
🖕31.14%
🌚10.38%
👌10.38%
🔥10.38%
🤓10.38%

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 263 reactions 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≈4,560 views23 reactionsread 29 August 2026

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

👍149

8 May 2026, 02:28 UTC≈13,200 views0 reactionsread 29 August 2026

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

6 May 2026, 03:59 UTC≈13,500 views9 reactionsread 29 August 2026

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

9

5 May 2026, 16:48 UTC≈13,000 views23 reactionsread 29 August 2026

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

15👍8

4 May 2026, 21:32 UTC≈15,300 views48 reactionsread 29 August 2026

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

32👍15😁1

10 Apr 2026, 08:18 UTC≈9,960 views4 reactionsread 29 August 2026

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

😁21👍1

7 Apr 2026, 13:12 UTC≈10,700 views10 reactionsread 29 August 2026

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

👍81👌1

5 Apr 2026, 18:13 UTC≈8,760 views1 reactionsread 29 August 2026

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

👍1

4 Apr 2026, 04:38 UTC≈8,860 viewsread 29 August 2026

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

21 Mar 2026, 14:27 UTC≈17,200 views11 reactionsread 29 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,400 views19 reactionsread 29 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.

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

“起点站的公告频道” (@tdck_emby), 10,091 subscribers as measured 19 September 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.