Telegram RegisterThe public register of Telegram
Telegram profile photo for ⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡

Channel

⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡

@appshub_channel

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

3,941subscribers

+130 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003273148890
TypeChannel
Username@appshub_channel
CreatedBetween 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/appshub_channel

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 15 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

4,100 average views per post against 3,941 subscribers — an engagement rate of 104.0%. Across the 2,385 registered channels in the same cohort — 3,164–9,986 subscribers, posting mainly in Chinese — the middle half sit between 2.60% and 18.1%, with a median of 7.87%.

What this was computed from
Window30 days (17 July 2026 16 August 2026)
Posts measured11 of 13 published in the window (0 exact, 11 rounded by Telegram)
Views totalled45,090
Mature posts only110.3% over 10 posts read at least 24h after publication
Subscribers3,941 measured 13 August 2026
Cohortb3162:zho · 2,385 channels · p10 0.758% · p25 2.60% · p50 7.87% · p75 18.1% · p90 36.0%
Position in cohort99.035th percentile · 13.2× the cohort median
Uncertainty±0.099% of the figure, from Telegram’s rounding
Post languageChinese · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 16 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

3,8113,9413,8766 August 2026 — 3,811 subscribers7 August 2026 — 3,837 subscribers10 August 2026 — 3,886 subscribers13 August 2026 — 3,941 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +130. 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 3,792–3,961 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:373,941+55
10 Aug 2026, 08:533,886+49
7 Aug 2026, 16:523,837+26
6 Aug 2026, 22:463,811first reading

Engagement

13 posts held, back to 28 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
104.0%
avg views ÷ 3,941 subscribers
Avg views / post
4,100
11 posts measured
Reaction rate
0.929%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 7 August 2026
Posts held13 (28 July 20267 August 2026)
Views total45,090
Reactions total419
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:02 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

Video runtime
8s
Average length
8s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

419 reactions across 11 posts, in 14 distinct kinds. The most used accounts for 40.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16840.1%
😁6315.0%
❤‍🔥409.55%
👍368.59%
🥰307.16%
🔥276.44%
👏194.53%
💯174.06%
🤔81.91%
🎉40.955%
🆒20.477%
😇20.477%
🤓20.477%
💔10.239%

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 11 of the 13 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 419reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 28 July 2026 to 7 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 11 we hold a reading for · 9%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @appshub_channel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 13 most recent posts we hold for this entry, published 28 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 06:21 UTC≈1,630 views70 reactionsread 8 August 2026
Photo

Bettbox官宣 - 今日我们正式确立了使命 恭喜中国开源大模型下载量荣登全球榜首 (以及Verge获得CCTV央视认证)!,今日,我们找到并正式确立了产品使命和愿景 - 为开源而连接,为创新而加速 - Connecting For Open Source, Accelerating Innovation 众所周知,Bettbox用户最多的使用场景就是访问Hugging Face等专业网站下载国产开源大模型,然后用AI来提升实质生产力以及技术创新等,这与我们整体的产品开发理念完全不谋而合 后续,我们将会继续稳扎稳打,不断更新和优化细节,给大家带来更好的连接开源,连接世界的加速体验,Respect~ 最后,新鲜热乎的Github最新Pre版 下载地址,以及 Bettbox群组

47😁18👍2🤔2🔥1

6 Aug 2026, 13:12 UTC≈1,730 views34 reactionsread 8 August 2026
Video

桌面端VS Code同款常用快捷键已悉数支持,现在,补全移动端最后一块拼图

🔥23💯8👍3

6 Aug 2026, 05:33 UTC≈2,170 views14 reactionsread 8 August 2026
Photo

超过三个档位会开始令人恶心 统一称之为资本的终极阳谋!

👏14

4 Aug 2026, 15:00 UTC≈2,570 views38 reactionsread 8 August 2026
Photo

手撸配置使用中转/专线类机场的正确姿势 现象:前几天推荐的百变小樱,以及今天群里在讨论的花云等,大家发现一种情况就是:如果没有使用机场的默认配置或者开启了DNS覆写,便会被分配到某些透传IP,而不是默认配置的BGP/专线入口 起因:当前大多中转/专线类机场为了防止通报,在Clash配置上也是用了多种方法,其中常见的例如私有DNS,例如花样的hosts映射等等,对于习惯了Providers引用的人,如果不花点心思看很容易被绕进去,其实解决办法也是很简单: 1.确保机场默认配置的私有DNS配置或者hosts字段被正确复制 如果还没正确解析,重点来了(几种方案任君选择,可逐一尝试): 2.1. 如果原机场配置没有proxy-server-nameserver,那么你也删除自己原有配置中的proxy-server-nameserver即可 2.2 保留自己原有的proxy-server-nameserver,把对应机场的私有

23🥰6👍4🤓2🆒2🤔1

3 Aug 2026, 02:06 UTC≈3,140 views19 reactionsread 8 August 2026
Photo

百变小樱 第二波福利来了 之前简单介绍了一下百变小樱🌸,老板看到群里关于初始带宽的反馈,主打听劝然后默默进后台把群友在售套餐调都调高了..(关于带宽这个事,回头可以多聊几句) 由于前面的VIP兑换码很快被抢光,所以这次又送来30个(不过好像是笔误?我看图片写的是100个),依旧如下: 1.Bettbox新用户独享:首充6.8折,优惠码: bettbox68 2.专享兑换码: bettboxbest100 注:如图所示,VIP套餐一个月兑换码(如果兑换不了就说明兑完了) 3.注册专享链接:百变小樱

11🤔4👏2👍1😁1

2 Aug 2026, 09:38 UTC≈3,050 views52 reactionsread 8 August 2026
Photo

大家好,我的新项目 TaskMonitor 已在 CNB / GitHub 发布,这是一款运行在 Windows 11,可在任务栏常驻监测系统负载并从进程维度追踪负载情况的小工具。欢迎下载支持一下,也欢迎多点点 Star,谢谢! https://cnb.cool/linesoft2/TaskMonitor https://github.com/linesoft2/TaskMonitor

❤‍🔥38👍93👏2

1 Aug 2026, 16:26 UTC≈2,970 views26 reactionsread 8 August 2026
Photo

试了一下DS4 Flash正式版,确实很强 梁圣:大家尽管用,不用担心我们的财务健康问题,左手大A,右手纳斯达克,除了法定休息日,每天九点半,补贴自然会到账~

🥰24😁2

1 Aug 2026, 05:59 UTC≈2,830 views22 reactionsread 8 August 2026

简单杂谈 - v2ray与Clash 当前Clash(Mihomo)系客户端如雨后春笋一般出来,除了AI编程和机场喜欢适配等原因以外,我觉得和分流需求本身也有密不可分的关系,个人之前并无分流/流媒体等需求,同时也是坚定的自建/Ray系(服务端Xray),针对GPT等,即使是垃圾节点也只需要在服务端分流到WARP即可解锁 但是随着AI本身的火爆发展,以及越来越多的精细化控制DNS和流量的需求,Clash系的优势逐渐更加明显,这也是一年半之前我转到Clash(注: 原Clash内核当时已删库,由Mihomo Meta接任)的主要原因之一,因为能分流和精细化分流是两回事 回过头来看,其实早期的v2ray( https://github.com/v2fly/v2ray-core ),现任xiaokangwang依然还有持续不断的Commits(以及新协议?),但是似乎已经被人慢慢遗忘,几个月前我也彻底退出了群聊,想到了长者的一句名

👍174👏1

31 Jul 2026, 03:20 UTC≈18,600 views78 reactions1 Starread 8 August 2026
Photo

#Bettbox v1.18.8 正式版本发布! https://github.com/appshubcc/Bettbox/releases/tag/v1.18.8 主要更新: - 新增代理页面自定义代理组UI开关 - 新增JS脚本覆写可视化开关适配API - 完善code-forge编辑器/查看MRS支持 - 完善针对macOS自动设置系统DNS恢复流程 - 修复macOS/rust后端问题导致的编辑器灰屏 - Android端应用列表现支持长按复制包名 - Windows版本正式OV数字签名已上线 - 针对DUFS等特殊形式的WebDAV支持 - 更新依赖,关于页面和其他细节调整 - Telegram群组/频道切换至Bettbox - 增加更多外文语言支持 对于Bettbox来说,v1.18.8正式版是一个近里程碑式的版本,不仅是因为Windows的OV签名证书已装载(以及项目源码通过了SignPath的二次人工安全审

59💯9🎉4🔥3❤‍🔥2🤔1

31 Jul 2026, 03:16 UTCviews —

Channel name was changed to «⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡»

30 Jul 2026, 05:04 UTC≈2,760 views45 reactionsread 6 August 2026
Photo

果然是A畜,就偶尔用用网页版,前几天的官方漏洞也没去薅它,今天一看邮件,这特么都能被封?

😁42😇2💔1

Showing the 12 most recent of 13 posts we hold for @appshub_channel. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 277,482 of 1,481,346entries 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 3 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.

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

“⬇️ 𝘽𝙚𝙩𝙩𝙗𝙤𝙭 𝘾𝙝𝙖𝙣𝙣𝙚𝙡” (@appshub_channel), 3,941 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/appshub_channel.

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.