竟然两周年了,真tm快啊,啥也不说了,少有的打折来袭当然伴随着新功能也在路上,加油干吧
👍4

Channel
@AfusektAndroid
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,567subscribers
+3 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002281981142 |
|---|---|
| Type | Channel |
| Username | @AfusektAndroid |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/AfusektAndroid |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 12:57 | 1,567 | +3 |
| 10 Aug 2026, 00:47 | 1,564 | first reading |
20 posts held, back to 16 February 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. It is computed over the 4 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (16 February 2026 – 8 August 2026) |
| Views total | 8,680 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 00:47 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.
31 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 74.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 74.2% | |
| 👍 | 8 | 25.8% |
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 16 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 31reactions 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 16 February 2026 to 8 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.
竟然两周年了,真tm快啊,啥也不说了,少有的打折来袭当然伴随着新功能也在路上,加油干吧
👍4
还是电话有效,给客服打了电话秒通过,目前115 直连已经可以正常使用了
👍2
由于115 身份认证原因,目前115无法正常使用,请等待重新认证完成,官方提示7个工作日之内,具体时间不清楚
❤1
征集一下 IOS 无法登录的 emby 服务,可以提供获取服务方式,或者私我你的服务给我做测试,将在下周一统一修复一次,当然那些把Af ban了服务就不用提了,顺便发布一个TV测试版本,3.0.6.3,增加了首页配置中媒体服务首页 简介版本开关
👍1
https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.2.3
https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.2.3-rc
https://play.google.com/store/apps/details?id=com.attempt.afusekt 最新测试版本3.2.1
❤1
Afusekt-3.2.0-beta2 https://play.google.com/store/apps/details?id=com.attempt.afusekt https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.2.0-beta2 AfusektV-3.0.6-beta4 https://github.com/AttemptD/AfuseKtV-release/releases/tag/AfuseKtV-3.0.6-beta4 Afusekt-desktop https://github.com/AttemptD/Afusekt-Desktop/releases/tag/0.1.1-beta
❤3
这是桌面端(win/mac)的首个版本,所以问题多多,可能会导致无法正常使用,闪退卡顿,播放失败等等问题,但是不用担心 我们将全力向前推进 @ranwow ,目前两个开发者都是上班维护,所以仅提供PRO用户内测,但是大家不要为了体验买PRO,目前来说并不值得,未来的桌面端价格也很便宜 https://github.com/AttemptD/Afusekt-Desktop/releases/tag/0.1.0-beta 具体相关事宜查看 https://github.com/AttemptD/Afusekt-Desktop https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.1.1 也带来 安卓端3.1.1正式版本,3.2.0也在同步进行中,tv端由于比较稳定目精力不足,将在不久发布第二个测试版本 顺便带来端午节的优惠 从0点开始 活动三天
❤7
Dandanplay目前已经开始Api限额了,所以目前遇到dandanplay搜索不到弹幕的情况,是属于正常的,后续将开发dandan api自定义key,因为弹幕属于免费功能且可以自定义弹幕服务器,所以没有去付费增加额度想法
❤1
https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.1.0-pre
❤2
https://github.com/AttemptD/AfuseKt-release/releases/tag/Afusekt-3.1.0-beta2
Showing the 12 most recent of 20 posts we hold for @AfusektAndroid. 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 — 946,964 of 1,160,990entries 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.
Named by 2 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“AfuseKt” (@AfusektAndroid), 1,567 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/AfusektAndroid.
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.