昨晚更新至今,有小伙伴提到这图失去了本身比较的意义,有点盲目吹捧 Telegram 的意思。 实际上是因为大家都在提 Telegram 的优点,我没有采集到竞品太多缺点,我只能以 Telegram 来写 QQ / 微信的对比,因此造成了一种吹捧 Telegram 的感觉。 凭我一个人的力量是很难合适和更新好这张对比图的,希望各位小伙伴能给我更多一些反馈,谢谢大家 (鞠躬 反馈与建议请联系 @AkaFeng

Channel
小黄蜂的广播站
@akafeng_broadcast
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
75subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001225527985 |
|---|---|
| Type | Channel |
| Username | @akafeng_broadcast |
| Created | 26 April 2018 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 5 September 2026 |
| On Telegram | t.me/akafeng_broadcast |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 05:15 | 75 | -1 |
| 22 Aug 2026, 12:32 | 76 | +1 |
| 9 Aug 2026, 21:17 | 75 | no change |
| 6 Aug 2026, 05:40 | 75 | first reading |
Engagement
6 posts held, back to 26 April 2018 — 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 page 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 6 posts for this entry, the most recent from 25 August 2018. An engagement rate over an empty window would be a number about nothing.
Recent posts
三大聊天工具 QQ、微信、Telegram 特性对比图 时隔 4 个月再次更新,感谢各位小伙伴们的帮助
Canonical 今天正式宣布推出 Ubuntu 18.04 LTS (Bionic Beaver) 操作系统。 https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
刚刚 @LetITFly 反馈了一些错误的地方,已重新修正校对,在此表示感谢 如有转载,建议同时转发此条消息做更新,以免误导他人
三大聊天工具 QQ、微信、Telegram 特性对比图 感谢 @cckn007 的帮助 提醒:我们的记者跑的没有香港的媒体快,故此图存在报道上的偏差,请以广播站后一条消息中的对比图为准
Channel created
Showing the 6 most recent of 6 posts we hold for @akafeng_broadcast. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@akafeng_broadcast named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 10 August 2026 – 10 August 2026
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“小黄蜂的广播站” (@akafeng_broadcast), 75 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/akafeng_broadcast.
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.