📡 免费节点更新 · 30 个 2026-11-17 08:00 VLESS × 30 平均延迟:1352 ms · 平均速度:1.68 MB/s 🇺🇸_US_美国_IPV4 · 1167 ms · 22.388 Mbps 🇺🇸_US_美国_IPV4 · 879 ms · 38.942 Mbps 🇺🇸_US_美国_IPV4 · 916 ms · 9.003 Mbps 🇺🇸_US_美国_IPV4 · 1279 ms · 20.084 Mbps 🇺🇸_US_美国_IPV4 · 933 ms · 39.356 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/a5ae81e88a4d8230721c1331eab3a59e928f7e30f389d16c93d25edb745e2359/mihomo sing-box: https://nodebuf.com/node-sub/…

Channel
长风分享频道
@changfengchannel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
26,426subscribers
+966 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 | -1001516635885 |
|---|---|
| Type | Channel |
| Username | @changfengchannel |
| Description | 分享网络技术与科学上网方法 私聊:@changfeng2021 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/changfengchannel |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 06:51 | 26,426 | +18 |
| 11 Nov 2026, 10:46 | 26,408 | +14 |
| 9 Nov 2026, 12:40 | 26,394 | +3 |
| 6 Nov 2026, 21:16 | 26,391 | -1 |
| 5 Nov 2026, 20:45 | 26,392 | -7 |
| 4 Nov 2026, 18:28 | 26,399 | -9 |
| 3 Nov 2026, 17:41 | 26,408 | +1 |
| 2 Nov 2026, 19:39 | 26,407 | +43 |
| 31 Oct 2026, 19:20 | 26,364 | -2 |
| 30 Oct 2026, 18:38 | 26,366 | -1 |
| 29 Oct 2026, 18:28 | 26,367 | +10 |
| 28 Oct 2026, 19:40 | 26,357 | -9 |
| 27 Oct 2026, 16:36 | 26,366 | -9 |
| 26 Oct 2026, 15:51 | 26,375 | -4 |
| 25 Oct 2026, 16:29 | 26,379 | +9 |
| 24 Oct 2026, 13:16 | 26,370 | -2 |
| 23 Oct 2026, 13:21 | 26,372 | +5 |
| 22 Oct 2026, 12:05 | 26,367 | -10 |
| 21 Oct 2026, 05:31 | 26,377 | -7 |
| 20 Oct 2026, 01:09 | 26,384 | first reading |
Engagement
192 posts held, back to 28 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 156 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.88%
- avg views ÷ 26,426 subscribers
- Avg views / post
- 1,820
- 49 posts measured
- Reaction rate
- 0.085%
- reactions ÷ views · ER floor
- Posts in window
- 49
- of 192 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. It is computed over the 35 of 49 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 192 (28 July 2026 – 17 November 2026) |
| Views total | 89,080 |
| Reactions total | 55 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:17 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
- 20
- Videos
- 32
- Links
- 692
Lifetime counters from Telegram’s own channel header, read 17 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.
Reaction mix
166 reactions across 103 posts, in 5 distinct kinds. The most used accounts for 78.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 131 | 78.9% | |
| 👍 | 27 | 16.3% | |
| 😁 | 4 | 2.41% | |
| 🔥 | 3 | 1.81% | |
| 👏 | 1 | 0.602% |
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 129 of the 192 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 166 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 192 most recent posts we hold, published 28 July 2026 to 17 November 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
Telegram’s own ‘edited’ marker: 0 of 49 posts held from the last 30 days (0%) 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).
📡 免费节点更新 · 24 个 2026-11-16 20:00 SS × 11 / VLESS × 3 / HYSTERIA × 5 / VMESS × 4 / ANYTLS × 1 平均延迟:2181 ms · 平均速度:988.8 KB/s 🇩🇪_DE_德国_IPV4 · 1123 ms · 1.357 Mbps 🇳🇱_NL_荷兰_IPV4 · 2924 ms · 7.902 Mbps 🇩🇪_DE_德国->🇳🇱_NL_荷兰_IPV4 · 1199 ms · 28.865 Mbps 🇯🇵_JP_日本_IPV4 · 4343 ms · 1.641 Mbps 🇸🇨_SC_塞舌尔->🇳🇱_NL_荷兰_IPV4 · 7217 ms · 2.480 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/cd44d19ceb21a80ff78f084d57d298c0af7544cd6…
❤1
📡 免费节点更新 · 27 个 2026-11-16 08:00 TROJAN × 2 / HYSTERIA2 × 1 / VLESS × 3 / ANYTLS × 2 / VMESS × 4 / HYSTERIA × 6 / SS × 9 平均延迟:3429 ms · 平均速度:649.6 KB/s 🇨🇳_CN_中国->🇭🇰_HK_香港_IPV4 · 376 ms · 11.160 Mbps 🇺🇸_US_美国_IPV4 · 5698 ms · 1.118 Mbps 🇳🇱_NL_荷兰_IPV4 · 8575 ms · 1.432 Mbps 🇹🇼_TW_台湾->🇩🇪_DE_德国_IPV4 · 1662 ms · 0.412 Mbps 🇯🇵_JP_日本_IPV4 · 6962 ms · 3.568 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/3a92f10ffe21162…
❤3
📡 免费节点更新 · 30 个 2026-11-15 20:00 VMESS × 5 / TROJAN × 4 / SS × 8 / VLESS × 3 / HYSTERIA2 × 1 / HYSTERIA × 7 / ANYTLS × 2 平均延迟:2538 ms · 平均速度:927.0 KB/s 🇯🇵_JP_日本_IPV4 · 7998 ms · 12.583 Mbps 🇨🇳_CN_中国->🇭🇰_HK_香港_IPV4 · 341 ms · 12.237 Mbps 🇩🇪_DE_德国_IPV4 · 2701 ms · 12.646 Mbps 🇬🇧_GB_英国_IPV4 · 2647 ms · 2.208 Mbps 🇺🇸_US_美国_IPV4 · 1739 ms · 2.727 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/46c297f23c9cdf7ba04c64a…
📡 免费节点更新 · 29 个 2026-11-15 08:00 HYSTERIA2 × 1 / TROJAN × 3 / HYSTERIA × 7 / ANYTLS × 2 / VLESS × 2 / VMESS × 4 / SS × 10 平均延迟:2603 ms · 平均速度:854.3 KB/s 🇺🇸_US_美国_IPV4 · 1739 ms · 2.727 Mbps 🇸🇬_SG_新加坡_IPV4 · 1738 ms · 15.980 Mbps 🇩🇪_DE_德国->🇳🇱_NL_荷兰_IPV4 · 2328 ms · 29.777 Mbps 🇹🇼_TW_台湾->🇩🇪_DE_德国_IPV4 · 1532 ms · 1.736 Mbps 🇯🇵_JP_日本_IPV4 · 2996 ms · 3.162 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/3da05ac7155…
👍1
📡 免费节点更新 · 9 个 2026-11-14 20:00 VLESS × 6 / VMESS × 2 / HYSTERIA × 1 平均延迟:3763 ms · 平均速度:1.60 MB/s @DeltaKroneckerGithub_781_IPV4 · 6153 ms · 2.680 Mbps @DeltaKroneckerGithub_672_IPV4 · 2682 ms · 2.426 Mbps 🇨🇳_CN_中国_IPV4 · 1281 ms · 2.968 Mbps 🇺🇸 美国 | USA #21_IPV4 · 1880 ms · 8.477 Mbps 🇳🇱_NL_荷兰_IPV4 · 8574 ms · 7.023 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/94c31dcfbe4fbd237161c6ef4aa5d2872a25d64741a3994…
❤2👍1
📡 免费节点更新 · 24 个 2026-11-14 08:00 VMESS × 5 / VLESS × 2 / HYSTERIA × 6 / ANYTLS × 1 / SS × 10 平均延迟:2442 ms · 平均速度:746.4 KB/s 🇩🇪_DE_德国_IPV4 · 11123 ms · 14.953 Mbps 🇯🇵_JP_日本_IPV4 · 648 ms · 27.359 Mbps 🇸🇨_SC_塞舌尔->🇳🇱_NL_荷兰_IPV4 · 4085 ms · 7.072 Mbps 🇺🇸 机场推荐:dafei.de 美国 89_IPV4 · 2646 ms · 13.954 Mbps 🇺🇸_US_美国_IPV4 · 3567 ms · 1.526 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/cb3516bd5d01aafd320ae66d1698dca4eee…
👍1
📡 免费节点更新 · 22 个 2026-11-13 20:00 VLESS × 1 / VMESS × 4 / HYSTERIA × 6 / ANYTLS × 1 / SS × 10 平均延迟:2129 ms · 平均速度:573.9 KB/s 🇸🇨_SC_塞舌尔->🇳🇱_NL_荷兰_IPV4 · 4085 ms · 7.072 Mbps 🇺🇸 机场推荐:dafei.de 美国 89_IPV4 · 2646 ms · 13.954 Mbps 🇺🇸_US_美国_IPV4 · 3567 ms · 1.526 Mbps @DeltaKroneckerGithub_3021_IPV4 · 2962 ms · 0.789 Mbps 🇺🇸 机场推荐:dafei.de 美国 15_IPV4 · 3387 ms · 1.356 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/80f00…
👍2
📡 免费节点更新 · 21 个 2026-11-13 08:00 VMESS × 4 / VLESS × 1 / HYSTERIA × 6 / ANYTLS × 1 / SS × 9 平均延迟:2376 ms · 平均速度:667.1 KB/s 🇺🇸_US_美国_IPV4 · 2942 ms · 1.064 Mbps @meliproxy (3)_IPV4 · 5116 ms · 0.918 Mbps 🇺🇸_US_美国_IPV4 · 5321 ms · 3.988 Mbps @DeltaKroneckerGithub_3021_IPV4 · 4664 ms · 0.603 Mbps 🇺🇸 机场推荐:dafei.de 美国 15_IPV4 · 4198 ms · 9.095 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/8c74fd973792b4cb95de3189da…
📡 免费节点更新 · 21 个 2026-11-12 20:00 VMESS × 4 / VLESS × 1 / HYSTERIA × 6 / ANYTLS × 1 / SS × 9 平均延迟:2376 ms · 平均速度:667.1 KB/s 🇺🇸_US_美国_IPV4 · 2942 ms · 1.064 Mbps @meliproxy (3)_IPV4 · 5116 ms · 0.918 Mbps 🇺🇸_US_美国_IPV4 · 5321 ms · 3.988 Mbps @DeltaKroneckerGithub_3021_IPV4 · 4664 ms · 0.603 Mbps 🇺🇸 机场推荐:dafei.de 美国 15_IPV4 · 4198 ms · 9.095 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/8c74fd973792b4cb95de3189da…
📡 免费节点更新 · 28 个 2026-11-12 08:00 VLESS × 3 / VMESS × 6 / TROJAN × 2 / HYSTERIA × 6 / ANYTLS × 1 / SS × 10 平均延迟:2351 ms · 平均速度:867.8 KB/s 🇺🇸_US_美国_IPV4 · 886 ms · 17.150 Mbps 🇺🇸_US_美国_IPV4 · 1733 ms · 11.200 Mbps 🏁RELAY-104.17.77.77-1140_IPV4 · 6187 ms · 1.691 Mbps 🇺🇸_US_美国_IPV4 · 952 ms · 1.192 Mbps @meliproxy (3)_IPV4 · 2944 ms · 14.428 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/fb747b879dea471b4160ca579ee…
📡 免费节点更新 · 22 个 2026-11-11 20:00 VLESS × 1 / VMESS × 3 / TROJAN × 1 / HYSTERIA × 6 / ANYTLS × 1 / SS × 10 平均延迟:2293 ms · 平均速度:836.2 KB/s 🇺🇸_US_美国_IPV4 · 8770 ms · 5.060 Mbps 🇨🇳_CN_中国_IPV4 · 2100 ms · 0.622 Mbps @DeltaKroneckerGithub_3021_IPV4 · 4726 ms · 0.619 Mbps 🇩🇪_DE_德国_IPV4 · 8069 ms · 1.602 Mbps 🇺🇸 机场推荐:dafei.de 美国 15_IPV4 · 2001 ms · 8.689 Mbps Clash / Mihomo: https://nodebuf.com/node-sub/391887014cd74ff067…
Showing the 12 most recent of 192 posts we hold for @changfengchannel. 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 2 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.
Handles this channel named that no longer answer
- Dead references
- 5
- 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
- 5
- vacant every time we have ever looked
@changfengchannel named 5 handles 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 16 posts, 11 November 2026 – 15 November 2026
named in 6 posts, 14 November 2026 – 15 November 2026
named in 4 posts, 11 November 2026 – 15 November 2026
named in 1 post, 15 November 2026 – 15 November 2026
named in 1 post, 15 November 2026 – 15 November 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“长风分享频道” (@changfengchannel), 26,426 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/changfengchannel.
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.