Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
65 measurements spanning 97 days, net +12,668. 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 39,734–56,202 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
11 Nov 2026, 02:08
54,302
+247
9 Nov 2026, 08:59
54,055
+184
8 Nov 2026, 03:01
53,871
+180
6 Nov 2026, 20:17
53,691
+199
5 Nov 2026, 18:29
53,492
+244
4 Nov 2026, 18:59
53,248
+229
3 Nov 2026, 16:09
53,019
+167
2 Nov 2026, 19:40
52,852
+156
1 Nov 2026, 21:46
52,696
+164
31 Oct 2026, 18:58
52,532
+239
30 Oct 2026, 15:30
52,293
+69
29 Oct 2026, 17:38
52,224
+189
28 Oct 2026, 17:36
52,035
+188
27 Oct 2026, 17:56
51,847
+185
26 Oct 2026, 16:49
51,662
+229
25 Oct 2026, 14:36
51,433
+188
24 Oct 2026, 15:30
51,245
+138
23 Oct 2026, 18:55
51,107
+130
22 Oct 2026, 20:21
50,977
+203
21 Oct 2026, 17:47
50,774
first reading
Engagement
40 posts held, back to 23 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 195 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
35.9%
avg views ÷ 54,302 subscribers
Avg views / post
19,500
13 posts measured
Reaction rate
0.652%
reactions ÷ views · ER floor
Posts in window
13
of 40 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
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
40 (23 July 2026 – 4 November 2026)
Views total
253,500
Reactions total
1,653
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Nov 2026, 12:38 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
Links
≈164
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
4,385 reactions across 40 posts, in 42 distinct kinds. The most used accounts for 45.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
2,012
45.9%
❤
1,563
35.6%
💩
152
3.47%
🥰
133
3.03%
👎
108
2.46%
😨
70
1.60%
🔥
51
1.16%
😱
40
0.912%
🗿
37
0.844%
⚡
34
0.775%
👏
30
0.684%
🤩
24
0.547%
🫡
18
0.41%
😁
16
0.365%
😍
15
0.342%
🐳
9
0.205%
🏆
7
0.16%
❤🔥
5
0.114%
💯
5
0.114%
🙊
5
0.114%
22 further kinds
51
1.16%
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 40 of the 40 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 4,385 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 23 July 2026 to 4 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 13 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).
v0.9.3
https://github.com/chen08209/FlClash/releases/tag/v0.9.3
Features
• Merged requests and connections; quick edit lists
• iOS 27 transitions, press and text selection; smoother pages
• Download and install updates in the app
• One delay test timeout; VPN crash and startup fixes
Bug Fixes
• Auto-select leaves an unusable first node at once
• Keep selections a filter hides
v0.9.3-pre.3
https://github.com/chen08209/FlClash/actions/runs/41611483666
Features
• Merged requests and connections; quick edit lists
• iOS 27 transitions, press and text selection; smoother pages
• Download and install updates in the app
• One delay test timeout; VPN crash and startup fixes
Bug Fixes
• Auto-select leaves an unusable first node at once
• Keep selections a filter hides
v0.9.3-pre.2
https://github.com/chen08209/FlClash/actions/runs/41326915735
Features
• Merged requests and connections; quick edit lists
• iOS 27 transitions, press and text selection; smoother pages
• Download and install updates in the app
• One delay test timeout; VPN crash and startup fixes
Bug Fixes
• Auto-select leaves an unusable first node at once
• Keep selections a filter hides
v0.9.3-pre.1
https://github.com/chen08209/FlClash/actions/runs/41310164789
Features
• Merged requests and connections; quick edit lists
• iOS 27 transitions, press and text selection; smoother pages
• Download and install updates in the app
• One delay test timeout; VPN crash and startup fixes
Bug Fixes
• Keep selections a filter hides
v0.9.2
https://github.com/chen08209/FlClash/releases/tag/v0.9.2
Features
• Access control state shown in a bar at the bottom
• Optional general overrides; settings apply sooner
• IP quality cached for 3 days; simpler Android dashboard
• Update the core to mihomo v1.19.33
• Colored tray status icons; monochrome option on macOS
• Sidebar blur; Windows fixes; keeps system proxies FlClash didn't set
• Profile QR codes,…
v0.9.2-pre.2
https://github.com/chen08209/FlClash/actions/runs/39921025613
Features
• Access control state shown in a bar at the bottom
• IP quality cached for 3 days; simpler Android dashboard
• Update the core to mihomo v1.19.33
• Colored tray status icons; monochrome option on macOS
• Sidebar blur; Windows fixes; keeps system proxies FlClash didn't set
• Profile QR codes, phone-to-TV links, more proxy fields
• A…
v0.9.2-pre.1
https://github.com/chen08209/FlClash/actions/runs/39748575294
Features
• Update the core to mihomo v1.19.33
• Access control state shown in a bar at the bottom
• IP quality cached for 3 days; simpler Android dashboard
• Colored tray status icons; monochrome option on macOS
• Sidebar blur; Windows fixes; keeps system proxies FlClash didn't set
• Profile QR codes, phone-to-TV links, more proxy fields
• A…
v0.9.1
https://github.com/chen08209/FlClash/releases/tag/v0.9.1
Breaking Changes
• Desktop TUN keys follow the profile unless picked; changed values carry over
Features
• French, Spanish and Korean translations
• No more Firebase analytics or crash reporting
• Per-key desktop TUN settings; system proxy and tray fixes
• Redesigned theme colors and color styles
• A redesigned dashboard around the current exit
• Prof…
v0.9.1-pre.4
https://github.com/chen08209/FlClash/actions/runs/38993037504
Breaking Changes
• Desktop TUN keys follow the profile unless picked; changed values carry over
Features
• French, Spanish and Korean translations
• No more Firebase analytics or crash reporting
• Per-key desktop TUN settings; system proxy and tray fixes
• Redesigned theme colors and color styles
• A redesigned dashboard around the current …
v0.9.1-pre.3
https://github.com/chen08209/FlClash/actions/runs/38920548655
Breaking Changes
• Desktop TUN keys follow the profile unless picked; changed values carry over
Features
• French, Spanish and Korean translations
• No more Firebase analytics or crash reporting
• Per-key desktop TUN settings; system proxy and tray fixes
• Redesigned theme colors and color styles
• A redesigned dashboard around the current …
v0.9.1-pre.2
https://github.com/chen08209/FlClash/actions/runs/38876333596
Breaking Changes
• Desktop TUN keys follow the profile unless picked; changed values carry over
Features
• French, Spanish and Korean translations
• Per-key desktop TUN settings
• Redesigned theme colors and color styles
• A redesigned dashboard around the current exit
• Manage external resources from profile details
• Proxy groups as cards…
v0.9.1-pre.1
https://github.com/chen08209/FlClash/actions/runs/38544959335
Features
• French, Spanish and Korean translations
• A redesigned dashboard around the current exit
• Manage external resources from profile details
• Proxy groups as cards, group tabs as chips
• Sortable tables for connections, requests and DNS
• Optional Liquid Glass and slide-to-pick menus
• Fill-based surfaces and iOS-style text sizes
B…
😨70👍61❤27💩4🥰3😁2👀1🔥1
Showing the 12 most recent of 40 posts we hold for @FlClash. 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.
Forward network
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.
Mentions
Named by 3 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.
Channels Telegram recommends alongside this one
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 28 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.
Appears in Telegram’s recommendations for other channels
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.
Nagram Tips @NagramTips · 52,085 Telegram ranks this channel #1 of 49 here — alongside 48 others — read 30 August 2026
Matsuridayo GitHub @MatsuriDayo · 45,738 Telegram ranks this channel #1 of 58 here — alongside 57 others — read 30 August 2026
Clash Verge Rev Channel @clash_verge_re · 86,158 Telegram ranks this channel #1 of 64 here — alongside 63 others — read 19 August 2026
Surfboard News @surfboardnews · 28,395 Telegram ranks this channel #3 of 64 here — alongside 63 others — read 9 September 2026
冲浪小贴士 @Gfwpro · 20,940 Telegram ranks this channel #4 of 33 here — alongside 32 others — read 28 September 2026
哔哩漫游 @biliroaming · 56,376 Telegram ranks this channel #7 of 50 here — alongside 49 others — read 12 September 2026
LuckyTool @LuckyTool · 31,335 Telegram ranks this channel #8 of 56 here — alongside 55 others — read 12 September 2026
Github_2dust @github_2dust · 93,000 Telegram ranks this channel #10 of 71 here — alongside 70 others — read 17 August 2026
科学上网观察与机场测速 @jichangtj · 135,732 Telegram ranks this channel #11 of 54 here — alongside 53 others — read 15 August 2026
HyperCeiler | Release & Notice @cemiuiler_release · 28,046 Telegram ranks this channel #12 of 51 here — alongside 50 others — read 12 September 2026
Yamby Release @yamby_release · 37,388 Telegram ranks this channel #13 of 29 here — alongside 28 others — read 1 September 2026
QAuxiliary CI Builds @QAuxiliary_CI · 19,689 Telegram ranks this channel #14 of 56 here — alongside 55 others — read 1 October 2026
重生之我在 TG做内置代理 @chongshengvpn · 69,411 Telegram ranks this channel #14 of 35 here — alongside 34 others — read 20 August 2026
QAuxiliary @QAuxiliary · 44,485 Telegram ranks this channel #15 of 58 here — alongside 57 others — read 12 September 2026
翻墙世界的梯子 @wxgqlfx · 34,229 Telegram ranks this channel #15 of 37 here — alongside 36 others — read 5 September 2026
折腾啥 @zhetengsha · 54,121 Telegram ranks this channel #15 of 50 here — alongside 49 others — read 26 August 2026
Nexitally Official Channel @Nexitally_Official · 21,098 Telegram ranks this channel #16 of 44 here — alongside 43 others — read 26 September 2026
FunProject @QToolCI · 50,216 Telegram ranks this channel #16 of 51 here — alongside 50 others — read 12 September 2026
Loon News @LoonNews · 48,288 Telegram ranks this channel #19 of 49 here — alongside 48 others — read 27 August 2026
便宜机场 @cheapairport_channel · 26,358 Telegram ranks this channel #20 of 30 here — alongside 29 others — read 15 September 2026
֍可莉日常֎ @ibilibili · 49,570 Telegram ranks this channel #20 of 40 here — alongside 39 others — read 14 September 2026
免费vpn梯子机场翻墙技术 @FreeVPN8 · 43,329 Telegram ranks this channel #20 of 30 here — alongside 29 others — read 30 August 2026
免费高速订阅节点 @freeVPNjd · 24,027 Telegram ranks this channel #21 of 31 here — alongside 30 others — read 19 September 2026
海豚机场测评|用户侧体验|测速频道 @haitun_channel · 39,058 Telegram ranks this channel #22 of 39 here — alongside 38 others — read 1 September 2026
This channel appears in 36 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this
entry's latest reading, not the date you are reading this.
“FlClash Channel” (@FlClash), 54,302 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/FlClash.
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.