Channel
@MedianBeta
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
99subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004332649073 |
|---|---|
| Type | Channel |
| Username | @MedianBeta |
| Created | 13 July 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/MedianBeta |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 21:37 | 99 | +1 |
| 9 Aug 2026, 11:45 | 98 | no change |
| 7 Aug 2026, 05:03 | 98 | first reading |
6 posts held, back to 13 July 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 July 2026 |
|---|---|
| Posts held | 6 (13 July 2026 – 17 July 2026) |
| Views total | 1,210 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 11:45 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.
5 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 100.0% |
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 2 of the 6 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 13 July 2026 to 17 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.
🥳🥳🥳新版本更新啦！！ 更新功能 极高自由度的主页自定义 在基础的调整上，加入了css自定义样式，甚至可以自主编入html样式 更新性能 - 优化标签页点击、关闭和长按固定逻辑 - 新增网站级兼容模式 - 优化广告过滤请求路径 - 减少 Cookie 和用户脚本数据的同步写入 - 改进 WebView 预热与渲染进程恢复 - 修复后台任务可能被静默丢弃的问题 此次虽然更新的功能不多，但是bug可是修了一堆又一堆，代码仍然压缩在kb级别。 github： https://github.com/bi-box/Median
❤5
Median性能模式下，在红米k30老旧机型上，由苹果发布的Jetstream3.0里，以4分整的成绩（约相差8per）遥遥领先via浏览器。 同一环境，同一内核，冷机实测。 由于开着vpn，此分数并非真实分数，真实分数会偏高。 这意味着，在重计算领域，median已经优于via浏览器。 Github https://github.com/bi-box/Median
当当当！ Medican浏览器已经出生拉！ 1.支持脚本，支持广告拦截。 2.有3个性能档位，这点极其实用，老旧手机使用低功耗档位，可以极大的减轻资源占用与压力，如果愿意牺牲电量，极限性能档位可以让你的老旧手机快到飞起来。 3.它拥有via没有的隐私浏览标签页。 4.纸面上的下载性能已经大于via …… 等等 它近乎是一种神级优化的浏览器，并且相对成熟，不是demo。 实际体验下来，最大的感受就是“轻快”。启动速度极快，后台挂载多个标签页也不怎么吃内存。对于不喜欢臃肿App的酷友来说，这绝对是个宝藏软件。 支持安卓8+ 目前产品已经开发完成，但缺乏大量实机测试，需要酷友帮忙bug反馈或者是性能反馈 github发布页：https://github.com/bi-box/Median
Channel photo removed
111
Channel created
Showing the 6 most recent of 6 posts we hold for @MedianBeta. 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 — 782,522 of 1,350,102entries 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.
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.
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.
“Median浏览器官方频道” (@MedianBeta), 99 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/MedianBeta.
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.