9 Jun 2021, 03:59 UTCviews —
Channel created
Channel
Emby 学习小秘
@EmbyNoisyX
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
37,700subscribers
-1,305 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001230326605 |
|---|---|
| Type | Channel |
| Username | @EmbyNoisyX |
| Created | 9 June 2021 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/EmbyNoisyX |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 13:46 | 37,700 | -12 |
| 5 Nov 2026, 12:05 | 37,712 | -17 |
| 4 Nov 2026, 14:17 | 37,729 | -24 |
| 3 Nov 2026, 16:17 | 37,753 | -12 |
| 2 Nov 2026, 14:16 | 37,765 | -15 |
| 1 Nov 2026, 12:37 | 37,780 | -17 |
| 31 Oct 2026, 12:20 | 37,797 | -15 |
| 30 Oct 2026, 13:16 | 37,812 | -19 |
| 29 Oct 2026, 11:48 | 37,831 | -27 |
| 28 Oct 2026, 09:01 | 37,858 | -14 |
| 27 Oct 2026, 11:09 | 37,872 | -22 |
| 26 Oct 2026, 12:59 | 37,894 | -23 |
| 25 Oct 2026, 16:10 | 37,917 | -11 |
| 24 Oct 2026, 17:16 | 37,928 | -23 |
| 23 Oct 2026, 16:27 | 37,951 | -9 |
| 22 Oct 2026, 14:55 | 37,960 | -16 |
| 21 Oct 2026, 07:28 | 37,976 | -24 |
| 20 Oct 2026, 05:58 | 38,000 | -17 |
| 19 Oct 2026, 08:50 | 38,017 | -9 |
| 18 Oct 2026, 05:30 | 38,026 | first reading |
Engagement
1 post held, back to 9 June 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 173 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 1 post for this entry, the most recent from 9 June 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 1 most recent of 1 post we hold for @EmbyNoisyX. 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.
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 12 registered channels — 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.
Emby影视资源发布
@Plus_Movie_Best · 27,96444 postsEmby Client
@sharereback · 7,9427 postsBaisi公费服须知
@Baisio · 1121 postEmby自定义Css及JavaScript
@embycustomcssjs · 1,3421 postEmby不完全指针
@EmbyGuide · 8241 post光速云频道
@gsycloud · 7131 postHaochi Emby
@hcEmby · 1,0711 post红杏云知识库📖
@hongxingknow · 3,1511 post🌸iMovieTVShare
@iMovieTVShare · 1241 post茶馆的机场收藏夹
@jfeiorjufi · 4,5161 postEmby-Tseb 通知站
@TsebEmby · 371 post落樱/Fallen sakura
@xxluoxx · 6011 post
@Plus_Movie_Best · 27,96444 postsEmby Client
@sharereback · 7,9427 postsBaisi公费服须知
@Baisio · 1121 postEmby自定义Css及JavaScript
@embycustomcssjs · 1,3421 postEmby不完全指针
@EmbyGuide · 8241 post光速云频道
@gsycloud · 7131 postHaochi Emby
@hcEmby · 1,0711 post红杏云知识库📖
@hongxingknow · 3,1511 post🌸iMovieTVShare
@iMovieTVShare · 1241 post茶馆的机场收藏夹
@jfeiorjufi · 4,5161 postEmby-Tseb 通知站
@TsebEmby · 371 post落樱/Fallen sakura
@xxluoxx · 6011 post
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Emby 学习小秘” (@EmbyNoisyX), 37,700 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/EmbyNoisyX.
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.