#频道互推 #群组推荐 图书杂志资源免费分享 墨理破解软件免费翻墙节点分享社 (NSFW)mmd分享 小新の资源库|实用软件工具 txt爽文小说 APPDO的互联网记忆 安卓软件游戏破解资源分享 今日有羊毛 纵享丝滑(丝袜精选) 电报频道&群组索引

Channel
某咕咕的 机场 & VPN 测评站
@AAAMouGuGuVPN2026
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,375subscribers
-2,279 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 | -1002868525831 |
|---|---|
| Type | Channel |
| Username | @AAAMouGuGuVPN2026 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/AAAMouGuGuVPN2026 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 09:39 | 4,375 | -220 |
| 15 Sept 2026, 00:57 | 4,595 | -199 |
| 11 Sept 2026, 18:56 | 4,794 | -186 |
| 7 Sept 2026, 03:57 | 4,980 | -313 |
| 2 Sept 2026, 01:47 | 5,293 | -54 |
| 30 Aug 2026, 08:05 | 5,347 | -250 |
| 27 Aug 2026, 01:44 | 5,597 | -315 |
| 23 Aug 2026, 15:24 | 5,912 | -253 |
| 20 Aug 2026, 06:35 | 6,165 | -172 |
| 17 Aug 2026, 12:46 | 6,337 | -114 |
| 14 Aug 2026, 03:28 | 6,451 | -81 |
| 10 Aug 2026, 12:41 | 6,532 | -89 |
| 7 Aug 2026, 20:27 | 6,621 | -33 |
| 6 Aug 2026, 21:16 | 6,654 | first reading |
Engagement
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 11 pages 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 3 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 2 reactions 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 9 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.
Recent posts
#频道推荐 #互推 ● Fang的资源分享群 ● 书屋 电子书 📚 𝑻𝑮𝒆𝑩𝒐𝒐𝒌 ● 影视软件 电视 TVBox ● 资源分享客栈-Applnn ● 免费节点|梯子|代理|VPN ● 𝕎𝔼电报频道精选推荐 ● 某咕咕的 机场 & VPN 测评站 参加互推: @pindaohutui123bot
关于频道迁移的通知 各位订阅者大家好: 因频道运营安排调整,某咕咕机场测评 将正式迁移至新的 Telegram 频道。 后续频道内容也将以新的运营方式持续更新。今后的内容包括:机场测评、优惠活动整理、使用体验分享、避坑提醒与建议,都会在新频道继续发布。 请大家及时加入: 测评频道: @MiaoMiaoGuGa 测评群组: @MiaoMiaoGuGuGu 新增功能: 历史测评查询机器人: @MouGuGu_Bot 欢迎大家使用机器人查询历史测评内容。 后续也欢迎大家加入群组交流讨论;如有机场希望投稿送测,也欢迎联系。 旧频道将在过渡期后停止维护,请大家互相转告,以免错过后续更新。 感谢各位一直以来对 某咕咕机场测评 的关注与支持。 测评频道 测评群组 投稿送测
✈️名称: Becky Network ✈️官网: https://853873.xyz ✈️频道: https://t.me/BeckyNetworkChannel ✈️群组: https://t.me/BeckyNetworkGroup ✈️开业时间: 🚀测速节点: 广州电信、佛山联通、广州移动 ✈️机场类型: 直连机场 ✈️节点类型: AnyTLS 优惠码 暂无 #直连机场 #AnyTLS #新疆支持 个人总结 这家机场采用AWS入口,三网测速表现比较一般,实际体验没有太多亮点。流媒体解锁能力也比较弱,很多时候只能说勉强能用,稳定性和成功率都不算高。虽然付费套餐价格不贵,但整体服务质量也确实对得起这个价位,属于便宜但体验普通。如果只是偶尔上网凑合用一下还能接受,但对速度、稳定性和流媒体需求稍微高一点的用户,基本不太推荐。 特别注意 1. 所有机场都建议月付 套餐和价格 : 🤧🤧🤧 延迟和速度…
❤1
✈️名称: 小飞机VPN ✈️官网: https://xfj2.ww01.cc ✈️频道: https://t.me/xfj288 ✈️群组: https://t.me/xiaofeiji288 ✈️开业时间: 2025年 🚀测速节点: 广州电信、佛山联通、广州移动 ✈️机场类型: 直连机场 ✈️节点类型: Trojan VLESSReality 优惠码 暂无 #直连机场 #Trojan #VLESSReality #新疆支持 个人总结 机场入口主要为 Akamai、AWS 和 GOMAMI,三网测速表现一般,流媒体解锁能力也只能算勉强可用。注册后赠送 1 天 10G 流量,另有公益套餐可订购,0 元 100G。付费套餐价格不算贵,但考虑到整体速度和解锁表现都比较一般,建议谨慎购买。 特别注意 1. 所有机场都建议月付 套餐和价格 : 🤧🤧🤧 延迟和速度 : 🤧🤧 流媒体解锁 : 🤧🤧🤧 测评频…
✈️名称: 坨坨云 ✈️官网: https://tootooyun.vip/ ✈️频道: https://t.me/tuotuoyun ✈️群组: https://t.me/tuotuoyun1 ✈️开业时间: 2026年4月 🚀测速节点: 广州电信、佛山联通、广州移动 ✈️机场类型: 直连机场 ✈️节点类型: VLESSReality AnyTLS 优惠码 暂无 #直连机场 #VLESSReality #AnyTLS #新疆支持 个人总结 之前测过的一家机场,节点比较精简但覆盖了主流地区,每个地区都配有家宽节点,三网速度表现都还不错,流媒体和AI解锁也能满足日常需求。另外注册就送1天1G的体验套餐,可以先试试水。 特别注意 1. 所有机场都建议月付 套餐和价格 : 🤧🤧🤧 延迟和速度 : 🤧🤧🤧 流媒体解锁 : 🤧🤧🤧 测评频道 测评群组 投稿送测 机场测评时间: 2026年7月14日
❤1
Showing the 6 most recent of 6 posts we hold for @AAAMouGuGuVPN2026. 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.
Mentions
Named by 7 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@AAAMouGuGuVPN2026 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 15 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“某咕咕的 机场 & VPN 测评站” (@AAAMouGuGuVPN2026), 4,375 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/AAAMouGuGuVPN2026.
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.