Telegram RegisterThe public register of Telegram

Channel

Yamby Release

@yamby_release

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

36,303subscribers

+106 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-1002117424923
TypeChannel
Username@yamby_release
DescriptionYet Another Emby Client!
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/yamby_release

Growth

36,19736,30336,2506 August 2026 — 36,197 subscribers6 August 2026 — 36,198 subscribers7 August 2026 — 36,212 subscribers8 August 2026 — 36,241 subscribers9 August 2026 — 36,248 subscribers10 August 2026 — 36,259 subscribers11 August 2026 — 36,273 subscribers12 August 2026 — 36,287 subscribers13 August 2026 — 36,293 subscribers14 August 2026 — 36,303 subscribers6 August 202614 August 2026
10 measurements spanning 8 days, net +106. 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 36,181–36,319 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:0536,303+10
13 Aug 2026, 11:2336,293+6
12 Aug 2026, 12:2436,287+14
11 Aug 2026, 11:0336,273+14
10 Aug 2026, 13:2336,259+11
9 Aug 2026, 15:1336,248+7
8 Aug 2026, 16:2936,241+29
7 Aug 2026, 13:0336,212+14
6 Aug 2026, 15:4236,198+1
6 Aug 2026, 08:1836,197first reading

Engagement

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

ERR · 30 days
43.5%
avg views ÷ 36,303 subscribers
Avg views / post
15,800
1 post measured
Reaction rate
0.671%
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 22 July 2026
Posts held20 (19 September 202522 July 2026)
Views total15,800
Reactions total106
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 01:28 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
22
Links
20

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

2,779 reactions across 18 posts, in 28 distinct kinds. The most used accounts for 47.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,32247.6%
👍74927.0%
🫡31311.3%
👏1405.04%
🎉953.42%
🥰933.35%
🔥140.504%
🎄70.252%
🤩40.144%
🆒30.108%
👎30.108%
👻30.108%
💩30.108%
🗿30.108%
😁30.108%
😇30.108%
🙏30.108%
🤓30.108%
❤‍🔥20.072%
🍾20.072%
8 further kinds110.396%

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 2,779reactions 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 19 September 2025 to 22 July 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

22 Jul 2026, 02:28 UTC≈15,800 views106 reactionsread 15 August 2026
File

What's New: - basic support for music library Optimize: - improve the scrolling effect on the homepage Fixes: - Jellyfin 12.0 compatibility - crashes in certain cases PS: The 32-bit version will be uploaded to the comments. 新增: - 音乐媒体库的基础支持 优化: - 优化首页的滚动效果 修复: - Jellyfin 12.0 的兼容支持 - 播放时偶发的crash PS: 32位的版本会上传在评论区 Google Play

81👍21👏2🥰2

16 Jun 2026, 10:48 UTC≈31,700 views119 reactionsread 15 August 2026
File

What's New: - FSR 1.0 support for mpv - Redesigned downloads: Added support for poster display, episodic grouping, and background downloading. Fixes: - Fixed several issues that caused crashes PS: The 32-bit version will be uploaded to the comments. 新增: - 为 mpv 增加 FSR1.0 支持 - 下载改版: 支持海报显示, 支持按剧集分组, 支持后台下载 修复: - 一些导致crash的问题 PS: 32位的版本会上传在评论区 Google Play

82👍18🫡7👏6🥰5💩1

14 May 2026, 02:58 UTC≈44,600 views108 reactionsread 15 August 2026
File

Optimization: - focus handling in the login dialog - actor page in landscape mode Fixes: - UI not responding in certain scenarios - UI errors in the portrait player PS: The 32-bit version will be uploaded to the comments. 优化: - 登陆对话框的焦点处理 - 横屏时演员页的背景 修复: - 部分场景下UI未响应的问题 - 竖屏播放器部分ui错误 PS: 32位的版本会上传在评论区 Google Play

👍6033🥰5🫡5🔥4🤩1

20 Apr 2026, 02:14 UTC≈53,500 views134 reactionsread 15 August 2026
File

What's New: - refactored remaining pages using Compose. - support for adjustable background blur radius - support for displaying "last played" timestamp - quick navigation for the Season page - option for disable predictive back animation - random playback - sorting in search - enhance server management PS: The 32-bit version will be uploaded to the comments. 新增: - 其余页面使用compose重构 - 支

109🥰12👍7❤‍🔥2👏2👎1😨1

19 Mar 2026, 03:11 UTC≈60,400 views134 reactionsread 15 August 2026
File

Fixes: - fix various bugs 修复: - 一些已知问题

🫡85👍2517🥰6😁1

17 Mar 2026, 09:15 UTC≈52,200 views55 reactionsread 15 August 2026
File

Fixes: - played media source did not match the selected one in certain cases PS: The 32-bit version will be uploaded to the comments. 修复: - 某些情况下播放的版本和选择的版本不一致 PS: 32位的版本会上传在评论区;

36👍15🫡4

12 Mar 2026, 10:04 UTC≈49,700 views118 reactionsread 15 August 2026
File

What's New: - remake with Compose UI; If you encounter any issues, you can temporarily switch back to the classic UI in Settings. - ui adaptation for landscape mode, tablets, and foldables - support for Predictive Back gestures Fixes: - multi-line SRT rendering PS: The 32-bit version will be uploaded to the comments. Quest devices may fail to open due to system issues. You can download the installation

94🎉13👍7👏3🔥1

9 Feb 2026, 11:03 UTC≈72,200 views196 reactionsread 15 August 2026
File

What's New: - support for displaying Douban links - support for viewing detailed information of loaded danmaku - toggle for fanart/thumb in the "Continue Watching" section on the home page - search for icon packs - server path Optimizations: - layout of the playback page - danmaku match - volume gain applies to all players; adjust volume gain in real-time during playback - button readabili

155👍33🎉6🍾2

15 Jan 2026, 10:17 UTC≈54,400 views166 reactionsread 15 August 2026
File

What's New: - support for reorder tabs in the collections page - option for force dpad support" - display title for selected audio/subtitle track - more information for multi-version items - adding and switch alternative addresses - full season/episode download support - quick reset when filtering - support server selection when manually searching for danmaku - manual danmaku search and sel

137👍11🥰9🔥5😇3🤯1

23 Dec 2025, 10:50 UTCviews —

Yamby Release pinned «🎄 Giveaway Time ✨ Prizes: 10 Reedem Codes for Yamby Pro Lifetime 🎁 How to Enter: Join this channel and click the link below 📅 Deadline: December 25, 2025 20:00 (GMT+8) *All codes valid for 3 months. Please redeem ASAP. PARTICIPATE 点击参与 Draw completed…»

23 Dec 2025, 10:48 UTC≈64,100 views193 reactionsread 15 August 2026

🎄 Giveaway Time ✨ Prizes: 10 Reedem Codes for Yamby Pro Lifetime 🎁 How to Enter: Join this channel and click the link below 📅 Deadline: December 25, 2025 20:00 (GMT+8) *All codes valid for 3 months. Please redeem ASAP. PARTICIPATE 点击参与 Draw completed / 已开奖

139👍34🥰10🎄7👎1🔥1🤔1

23 Dec 2025, 10:48 UTC≈50,400 views23 reactionsread 15 August 2026
Sticker

Sticker, posted without a caption

🥰194

Showing the 12 most recent of 20 posts we hold for @yamby_release. 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 — 104,281 of 1,478,351entries 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.

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 18 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

科技圈🎗在花频道📮
@zaihuapd · 275,374
Telegram ranks this channel #40 of 40 here — alongside 39 others — read 12 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“Yamby Release” (@yamby_release), 36,303 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/yamby_release.

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.