Telegram RegisterThe public register of Telegram

Channel

科学上网观察与机场测速

@jichangtj

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

133,300subscribers

+145 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001406690797
TypeChannel
Username@jichangtj
Description#机场推荐 #机场测速 #机场评测 /观察/点评,科学上网和科技相关新闻资讯; #机场推荐 : http://bit.ly/3fdHzbp Twitter: twitter.com/jichangtj 选机场要求很高!除非优秀否则不收。投稿要求:https://t.me/jichangtj/1014 投稿: @jichangtjBot 骚扰会ban
Created27 March 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/jichangtj

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 9 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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

133,155133,300133,227.56 August 2026 — 133,155 subscribers6 August 2026 — 133,155 subscribers7 August 2026 — 133,204 subscribers8 August 2026 — 133,217 subscribers9 August 2026 — 133,234 subscribers10 August 2026 — 133,239 subscribers11 August 2026 — 133,263 subscribers12 August 2026 — 133,250 subscribers13 August 2026 — 133,259 subscribers14 August 2026 — 133,300 subscribers6 August 202614 August 2026
10 measurements spanning 8 days, net +145. 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 133,133–133,322 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 12:56133,300+41
13 Aug 2026, 01:24133,259+9
12 Aug 2026, 00:41133,250-13
11 Aug 2026, 03:43133,263+24
10 Aug 2026, 02:02133,239+5
9 Aug 2026, 02:21133,234+17
8 Aug 2026, 00:08133,217+13
7 Aug 2026, 03:38133,204+49
6 Aug 2026, 04:15133,155no change
6 Aug 2026, 04:08133,155first reading

Engagement

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

ERR · 30 days
28.5%
avg views ÷ 133,300 subscribers
Avg views / post
38,000
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 18 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 14 August 2026
Posts held18 (2 April 202614 August 2026)
Views total75,900
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 07:15 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

Photos
411
Videos
3
Links
322

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

14 Aug 2026, 10:44 UTC≈15,900 viewsread 15 August 2026

谷歌今天推出Gemini 3.7 flash之后IP风控变严格,送中了大量IP,最明显表现为用不了Gemini。

29 Jul 2026, 14:54 UTC≈60,000 viewsread 15 August 2026

奈云老板被抓据说是因为收款链路出现了问题,建议有推广过这家机场的更换U收款地址。

6 Jul 2026, 08:26 UTC≈112,000 viewsread 15 August 2026

咨询了一些机场主后,了解到很多机场近几个月陆续转向 AnyTLS,主要是与通报/封锁机制有关。在今年 6 月之前,AnyTLS 基本不会因为相关原因被通报,而当时很多通报主要来自内鬼获取订阅后,然后通过程序模拟代理客户端定时拉取节点测活后再将 IP 提交导致封禁。 一种比较普遍的推测是:6 月之前,内鬼使用的测活的内核(比如xray)可能还不支持 AnyTLS,因此无法有效识别这类节点。随着 iOS 客户端陆续更新并支持 AnyTLS,越来越多机场在 5 月份开始大规模迁移到 AnyTLS,随后相关部门也在 6 月更新了测活内核(比如更换为了mihomo或singbox),因此从 6 月开始,AnyTLS 也逐渐出现了被通报的情况。 另外,目前很多机场使用的 AnyTLS 自签证书和打开跳过证书验证可能是与浙江江苏福建的SNI阻断有关系。

23 Jun 2026, 04:24 UTC≈124,000 viewsread 15 August 2026

谷歌邮箱可以修改前缀了: http://myaccount.google.com/google-account-email 旧邮箱不影响使用,会变为备用别名邮箱。

13 May 2026, 09:57 UTC≈144,000 viewsread 15 August 2026
Photo

除 #ClashMi 外。一些免费的 #IOS #ClashMeta #mihomo 内核客户端,都无广告 #Nextin 给需要封端的机场收费,普通用户免费。进入页面就是导入订阅输入框,支持扫码导入等,小白友好。开发者之前让付费发广告,想着是普通用户免费就友情推广了。 🔧 支持 HTTPS 重写(Rewrite)功能 🔗 支持链式代理(Proxy Chain) 长按节点即可设置链式出口 🧩 兼容大部分小火箭(Shadowrocket)模块规则 ▶️ 支持 YouTube 去广告模块(实验性) 下载地址 #ClashLite 超简约,图标有点萌 下载地址 #LinkClashX UI挺好 下载地址 还有:connect now , #meow (rust写的,需iOS26) #choclite(clash-rs内核) 等

8 May 2026, 12:48 UTC≈129,000 viewsread 15 August 2026

由于防火墙本身的具体原理与策略外界难以得知,目前很多判断只能基于现象进行反推。因此,网络上流传的不少消息本质上都属于小道消息或个人猜测,也由此衍生出大量谣言与误读,容易误导用户,甚至引发不必要的恐慌。 建议大家保持理性判断,对相关信息尽量多方交叉验证,擦亮双眼,不轻信未经证实的传言。谣言止于智者。

8 May 2026, 12:47 UTC≈125,000 viewsread 15 August 2026

观察五一之后各大 IDC 的情况后发现,封锁相比前段时间有所减弱,市场上也开始重新出现国内中转线路出售。不过,目前很多机房都会安装“傲盾”软件,用于检测翻墙流量,据称连 VLESS 在内的一些新协议也具备识别能力。 同时,部分国内中转 VPS 的价格也出现了明显上涨。此外,一些中转上游要求“押一付一”,一旦线路被通报或出现问题,押金将会被直接扣除。 目前国内中转面临的不仅是 IDC 扫描,还包括运营商侧扫描以及管局下发的封锁与整治。因此,对于机场而言,国内中转依然处于高成本、高风险的状态。 也正因为目前中转封锁依然处于较高压状态,大部分机场已尽量避开国内中转方案,比如使用直连or透传(透传入口为香港ip)。

8 May 2026, 12:18 UTC≈114,000 viewsread 15 August 2026
Photo

快连官方推特 发公告说复活了。 但是公告里面有段: 快连面向全球用户恢复标准运营机制,并不代表所有地区的连接体验都已恢复正常。 目前,我们无法保证中国大陆地区的服务状态。 面向全球用户恢复,但是不保证中国大陆地区的,文字游戏。

1 May 2026, 05:16 UTC≈171,000 viewsread 15 August 2026

疑似 Apple 屏蔽了部分境外 App 的消息推送: iOS 上的 Telegram 、Instagram和X 均出现无法接收推送的情况。其中 X 已持续多日,TG昨日开始出现,解决办法: 1.Telegram 可使用第三方客户端(如 Swiftgram、Nicegram) 2.让 Apple push走代理,参考 ,需要打开包括APNs(比如小火箭的设置--隧道--包括APNs) 小火箭教程:https://jichangnew.com/iostuisong

28 Apr 2026, 06:36 UTC≈126,000 viewsread 15 August 2026

所有.icu域名被无差别污染,包括备案域名,甚至是不存在的域名。是防火墙首次墙整个顶级域名,可能是防火墙DNS污染新策略。--已恢复,可能是能力测试。 同时今天有部分机场官网也被污染了。

28 Apr 2026, 00:10 UTC≈186,000 viewsread 15 August 2026
Photo

著名机场VPN商家——快连,倒闭了。这次 VPN 封锁潮中,它也是目前跑路商家里最大的一家。过去半个月官方公告一直表示“正在修复中”,但实际上服务始终处于不可用状态。体量如此之大的平台都能倒闭,确实让很多人感到非常意外。此前很多人一度怀疑,快连广告打得如此猖狂,背后是否有特殊背景。现实已经说明,在 VPN 这种灰色行业里,低调发展尚且艰难,过于高调往往难以长久。

Showing the 12 most recent of 18 posts we hold for @jichangtj. 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 — 189,291 of 1,478,351entries 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

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

“科学上网观察与机场测速” (@jichangtj), 133,300 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jichangtj.

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.