Telegram RegisterThe public register of Telegram

Channel

机场测速/推荐/观察

@duang_speedtest

On this record: Growth · Engagement · Posts · Citations · Cite this entry

29,926subscribers

+291 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001296468941
TypeChannel
Username@duang_speedtest
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/duang_speedtest

Growth

29,63529,92629,780.57 August 2026 — 29,635 subscribers7 August 2026 — 29,635 subscribers7 August 2026 — 29,641 subscribers8 August 2026 — 29,686 subscribers9 August 2026 — 29,718 subscribers10 August 2026 — 29,775 subscribers11 August 2026 — 29,809 subscribers12 August 2026 — 29,871 subscribers13 August 2026 — 29,926 subscribers7 August 202613 August 2026
9 measurements spanning 6 days, net +291. 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 29,591–29,970 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 09:0829,926+55
12 Aug 2026, 11:5729,871+62
11 Aug 2026, 10:2229,809+34
10 Aug 2026, 13:3329,775+57
9 Aug 2026, 10:3229,718+32
8 Aug 2026, 08:1129,686+45
7 Aug 2026, 11:4629,641+6
7 Aug 2026, 08:0029,635no change
7 Aug 2026, 07:5629,635first reading

Engagement

15 posts held, back to 9 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.6%
avg views ÷ 29,926 subscribers
Avg views / post
6,750
13 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
13
of 15 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 12 August 2026
Posts held15 (9 July 202612 August 2026)
Views total87,805
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 21:41 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.

Recent posts

12 Aug 2026, 13:19 UTC836 viewsread 12 August 2026
Photo

#投稿 #NIVA Network #Vless #Shadowsocks 跳转官网 群组 频道 节点特色 • 多地区全球稳定节点:🇭🇰 香港 / 🇹🇼 台湾 / 🇯🇵 日本 / 🇸🇬 新加坡 / 🇺🇸 美国 / 🇬🇧 英国,带有部分家宽 三网优化,提升连接稳定性 套餐澜 一次性等提供额外专线节点,适合长期稳定生产力使用 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

12 Aug 2026, 12:18 UTC969 viewsread 12 August 2026
Photo

#超级飞鱼 #Vless 跳转官网 群组 频道 突击检查,感觉表现不行了,¥6/80G。 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

9 Aug 2026, 12:50 UTC≈3,030 viewsread 12 August 2026
Photo

#良心云 #直连 #Vless #Hysteria2 官网:https://良心云.com 频道:@liangxin_yun 群组:@liangxinyun_chat 建议特殊时期备用!落地全是aws,¥2/100GB,¥4/500GB,除了这2个套餐,其他都不用看了。 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

8 Aug 2026, 14:13 UTC≈3,500 viewsread 12 August 2026
File

#投稿 #便宜机场 #Vless #Hysteria2 点击跳转官网 频道 灵车机场,便宜是真便宜。¥1.02/100GB、¥4.67/500GB,适用于大流量、备用。 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

5 Aug 2026, 07:12 UTC≈5,920 viewsread 12 August 2026
Photo

#投稿 #nowhere #专线 #Vless 官网:https://dashboard.nowhere.lat/ 频道:@nowherenet_channel 群组:@nowherenet_group 之前投稿过的机场,好像被我漏掉了... 没想到还活着,查了一下是某个做的还挺大的IDC开的,18块一年,透传专线节点一倍率,直连节点0.6倍率,好像比大多数灵车直连机场阳间一点,需要的可以买着玩玩。 (机场圈还在卷,一块多一个月都能用上一倍率透传了...) 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

30 Jul 2026, 12:08 UTC≈8,760 viewsread 12 August 2026
Photo

喵的,上个月刚换的二手 GN850,这个月打游戏就开始黑屏重启。 本来想着二手捡个性价比电源,结果感觉像是直接踩雷。 狗都不碰二手电源了,下辈子绝对注意。

29 Jul 2026, 12:01 UTC≈8,100 viewsread 12 August 2026
Photo

接后续,OP Nikki配置的问题,机场私有DNS了,然后插件覆写,一堆BUG。同时M73的 I217-V 也是坑货断流,换 Debian13 裸跑singbox透明网关就解决,ping值和延迟也正常。 PS:这OP插件好喜欢覆写,就能给啥配置啥?怪不得好多机场封端不让用

22 Jul 2026, 12:52 UTC≈10,500 viewsread 12 August 2026

更新!分析日志貌似是扛不住并发数,先考虑换个企业级路由RG-N7205-E,桥接已拿到超级密码。 这两天实施,更换OP设备为M73,主打力大砖飞,还不行就换I7。

21 Jul 2026, 12:49 UTC≈10,300 viewsread 12 August 2026
Photo

#投稿 #Lumina #直连 #中转 #AnyTLS 跳转官网 频道 群组 优惠码:10%OFF(9折循环优惠) 开业时间不算太久,¥13.5/200G,不过节点普遍带倍率,低倍率节点相对较少,实际可用流量会缩水不少。 整体看下来,成本应该主要集中在 Gomami 线路上。 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

21 Jul 2026, 12:29 UTC≈8,430 viewsread 12 August 2026
Photo

#投稿 #lizione #专线 #Shadowsocks 官网:https://lizione.com 频道:https://t.me/lizioness 群组:https://t.me/LiZione_Chat 客服:https://t.me/sunxiaochuan202 新开的机场!老板要求的复测,晚高峰稳定跑2G,IEPL 机场导航|订阅转换 & Clash 订阅阅后即焚解决办法 ⚠️ 推荐所有机场月付

21 Jul 2026, 11:06 UTC≈7,760 viewsread 9 August 2026
Photo

今天遇到一个工作室的 BUG。 大概 70 台设备,网关是 OpenWrt,使用 Nikki。 现象: - 测延迟时延迟会飙升到 400ms+ - 打开网页明显转圈 2-4 秒 - 体感非常明显,但不确定具体瓶颈在哪 考虑方向: 1. OpenWrt 本身性能瓶颈? 2. Nikki 规则匹配或 DNS 问题? 3. 多设备并发导致连接数、CPU、内存压力? 4. 出口线路或 NAT 表资源不足? 5. 路由器性能问题,考虑更换企业级设备 有没有优化思路? 注:光猫未改桥接,使用的是电信送的路由器

Showing the 12 most recent of 15 posts we hold for @duang_speedtest. 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 — 802,225 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.

Mentions

Named by 5 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.

“机场测速/推荐/观察” (@duang_speedtest), 29,926 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/duang_speedtest.

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.