Channel
@jichangtj
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
135,372subscribers
+2,217 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001406690797 |
|---|---|
| Type | Channel |
| Username | @jichangtj |
| Description | #机场推荐 #机场测速 #机场评测 /观察/点评，科学上网和科技相关新闻资讯； #机场推荐 : http://bit.ly/3fdHzbp Twitter: twitter.com/jichangtj 选机场要求很高！除非优秀否则不收。投稿要求：https://t.me/jichangtj/1014 投稿： @jichangtjBot 骚扰会ban |
| Created | 27 March 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/jichangtj |
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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 01:08 | 135,372 | +36 |
| 5 Nov 2026, 00:38 | 135,336 | +52 |
| 3 Nov 2026, 23:45 | 135,284 | +51 |
| 2 Nov 2026, 22:51 | 135,233 | +65 |
| 1 Nov 2026, 23:09 | 135,168 | +61 |
| 31 Oct 2026, 23:45 | 135,107 | +162 |
| 30 Oct 2026, 23:26 | 134,945 | +305 |
| 29 Oct 2026, 23:39 | 134,640 | +152 |
| 28 Oct 2026, 22:40 | 134,488 | +314 |
| 27 Oct 2026, 18:19 | 134,174 | +129 |
| 26 Oct 2026, 14:49 | 134,045 | +10 |
| 25 Oct 2026, 17:08 | 134,035 | -4 |
| 24 Oct 2026, 20:29 | 134,039 | +2 |
| 23 Oct 2026, 18:09 | 134,037 | +8 |
| 21 Oct 2026, 15:29 | 134,029 | +26 |
| 20 Oct 2026, 11:36 | 134,003 | +12 |
| 19 Oct 2026, 11:27 | 133,991 | +4 |
| 18 Oct 2026, 14:41 | 133,987 | +19 |
| 17 Oct 2026, 13:37 | 133,968 | +15 |
| 16 Oct 2026, 14:46 | 133,953 | first reading |
28 posts held, back to 2 April 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 187 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 28 (2 April 2026 – 6 November 2026) |
| Views total | 235,210 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 15:34 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.
Lifetime counters from Telegram’s own channel header, read 6 November 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.
Telegram’s own ‘edited’ marker: 5 of 6 posts held from the last 30 days (83.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
发现不少高校的校园网有特殊的墙： 不少校园网不允许第三方公共加密dns，这意味着必须使用学校网络的dns，会导致学校能看到你访问了哪些网站。这是校园网检测你是否在翻墙的方法之一。 同时近期不少高校在宣传强调禁止翻墙。如果高校强调了不允许翻墙且可能有处罚，则建议使用手机蜂窝数据翻比较安全。 如果强制了使用校园网DNS且不担心：使用mihomo内核的客户端，可以把配置文件里面的dns配置项的： 1)把enable改为flase 或 2)增加nameserver: - system Flclash设置页面可一键开启追加系统DNS功能
一直在墙TCP端口，但是强度整体低了很多。不少人反馈开会封的TCP端口被放出来了。
以往遇到重要会议，GFW 通常只会在首日加强封锁，短期“刷一波存在感”。但这次会议结束后，封锁仍在持续，至今已达 5 天，不排除常态化的可能。如果持续下去，对直连和海外中转机场都将是沉重打击。 4 月份是重点打击是国内中转，那么现在则轮到直连和海外中转。 至于识别方式，一种猜测是：GFW 可能借助 AI 提升了对 翻墙流量的识别能力，从此前依赖人工购买订阅、测活后封锁，进一步转向直接识别流量并实施封锁。
观察发现，从昨天开始一直在持续封锁中，每小时37分封锁一波，流量大的更容易检测到，影响了很多海外中转机场。
这两天北京开会，GFW探测功率拉满了，对海外ip不是直接封锁ip, 而是墙TCP端口，阻断被检测到翻墙的海外ip所有端口的TCP连接，而ICMP(Ping) 和UDP则正常。之前4月份中国移动蜂窝移动出现过类似现象，可能是之前是测试，现在大范围应用。
#灯塔加速器 Vless（reality）海外中转+专线机场。第三方客户端订阅是海外中转。 老板肉身：海外 注册有试用，试用只能使用机场专属客户端。 支持24小时无条件退款，流量超过10%不退 推荐购买人群： 担心跑路，可周付 需要按量付费 想找不满意可退款的 可接受使用官方客户端 套餐：套餐： 入门套餐：年付120，60G/月，限速100M 轻量套餐：月付30，120G/月，限速200M VIP套餐：周付28,月付68，300G/月，限速300M SVIP套餐：周付66,月付138，800G/月，限速500M 支持按量计费模式，用多少扣多少，最低10元起充，流量价格为0.85/G 观察了挺久，端内的稳定性还可以。建议买VIP套餐和SVIP套餐（季付起），使用有问题找官网客服。 官网地址 测速大图
由于香港一著名一级T1运营商（HGC）路由配置错误，导致部分网段BGP路由泄露和污染，导致全球部分网络路由混乱和大规模网络故障(主要是香港、日本、新加坡)，运营商正在抢修。 路由泄露是运营商发错了“网络导航”，其他运营商信了它，导致大量用户的流量被带到错误的地方。 20点20分左右部分地区已恢复
https://x.com/fndroid/status/2098834537866514582 Clash for Windows作者Fndroid对近期出现的“Clash经典回归”App的回应。相关解释
https://huarun.win 收录代理客户端，相关开发者，内核，代理协议，翻墙历史等。得花不少时间。
📡 AWS 面向中国大陆移动、联通的网络表现较好，因此不少机场使用 AWS 作为海外中转。 自 9 月 4 日起，多家使用 AWS 中转的机场出现异常：节点在未使用时测延迟正常，TCPing 也正常，但一旦实际连接使用，该节点便会超时；Hy2 协议或ipv6目前表现正常。 有猜测认为，这可能与防火墙针对 AWS 流量的阻断有关，但也有可能是AWS路由绕路，因为以往每年AWS都会出现持续绕路几天的情况。 此外，自 8 月底起，江苏、浙江、福建部分地区的部分机场的用户反馈，使用海外 IP 中转的节点会突然长时间超时，大概率是省墙阻断。
谷歌今天推出Gemini 3.7 flash之后IP风控变严格，送中了大量IP，最明显表现为用不了Gemini。
奈云老板被抓据说是因为收款链路出现了问题，建议有推广过这家机场的更换U收款地址。
Showing the 12 most recent of 28 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.
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.
Named by 14 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“科学上网观察与机场测速” (@jichangtj), 135,372 subscribers as measured 6 November 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.