Telegram RegisterThe public register of Telegram
Telegram profile photo for Quantumult X News

Channel

Quantumult X News

@QuanXNews

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

40,479subscribers

+590 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001361573877
TypeChannel
Username@QuanXNews
Description此频道用于发布 Quantumult、Quantumult X相关资讯 下载: https://apps.apple.com/us/app/quantumult-x/id1443988620 反馈: [email protected] 群组: @QuanXApp
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/QuanXNews

Topic

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

39,88941,08240,485.540,4796 August 20267 November 2026
61 measurements spanning 93 days, net +590. 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,710–41,261 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
7 Nov 2026, 08:1440,479-21
6 Nov 2026, 07:5840,500-18
5 Nov 2026, 10:1940,518-10
4 Nov 2026, 06:3140,528-13
3 Nov 2026, 09:1640,541-9
2 Nov 2026, 10:1640,550-13
1 Nov 2026, 09:4640,563-44
31 Oct 2026, 12:0540,607-16
30 Oct 2026, 12:1740,623-25
29 Oct 2026, 10:1740,648-36
28 Oct 2026, 09:4840,684-9
27 Oct 2026, 06:1940,693-38
26 Oct 2026, 03:3540,731-19
25 Oct 2026, 03:0640,750-9
24 Oct 2026, 05:3740,759-24
23 Oct 2026, 02:4440,783-17
22 Oct 2026, 01:4040,800-59
20 Oct 2026, 19:5540,859-14
19 Oct 2026, 16:0440,873-23
18 Oct 2026, 13:4640,896first reading

Engagement

43 posts held, back to 11 May 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 177 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.0%
avg views ÷ 40,479 subscribers
Avg views / post
7,290
9 posts measured
Reaction rate
0.175%
reactions ÷ views · ER floor
Posts in window
9
of 43 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 6 November 2026
Posts held43 (11 May 2026 – 6 November 2026)
Views total65,630
Reactions total115
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 09:49 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
119
Videos
3
Links
113

Lifetime counters from Telegram’s own channel header, read 7 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

864 reactions across 43 posts, in 8 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤33338.5%
👍25529.5%
🎉22125.6%
💯222.55%
🥰161.85%
❤‍🔥70.81%
👏50.579%
🔥50.579%

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 43 of the 43 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 864 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 43 most recent posts we hold, published 11 May 2026 to 6 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: 4 of 9 posts held from the last 30 days (44.4%) 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).

6 Nov 2026, 05:52 UTC≈3,410 views10 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (960) is ready to test on iOS. What to Test - iPerf3: added a parallel streams option for client tests. - Improved compatibility when using the device as an HTTP proxy server. 群组: @QuanXApp 频道: @QuanXNews

🎉5👍2🥰2❤1

4 Nov 2026, 04:02 UTC≈4,740 views10 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (959) is ready to test on iOS. What to Test - On iOS, the iPerf page has been refined. The host row now keeps a list of hosts you have used, so you can pick one instead of retyping it. - On macOS, the HTTP proxy server is now available alongside the SOCKS5 server added in Build 958, matching iOS. It can be reached from other devices on the LAN and its port can be changed, so a NAS or …

👍7❤3

3 Nov 2026, 09:31 UTC≈5,410 views29 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (958) is ready to test on iOS. What to Test - TCP forwarding throughput is substantially higher. On an iPhone 17 Pro, iperf3 through the Quantumult X Tunnel now reaches about 15 Gbit/s downstream, up from roughly 4.5 Gbit/s in previous builds (the same ceiling applied on an iPhone 12 Pro). Power draw is largely unchanged: the old limit was never the CPU but the tunnel's memory policy,…

🎉19❤5👍5

28 Oct 2026, 13:15 UTC≈7,280 views8 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (957) is ready to test on iOS. What to Test - Fixed an issue related to MitM leaf certificate generation. 群组: @QuanXApp 频道: @QuanXNews

👍5❤3

28 Oct 2026, 08:01 UTC≈7,240 views4 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (956) is ready to test on iOS. What to Test - The JS persistent data list now supports adding and editing entries, alongside viewing and deleting. Tap the add button to create a new key-value pair, or swipe an existing entry (v2) to edit its value in a plain-text editor. 群组: @QuanXApp 频道: @QuanXNews

❤2🎉2

27 Oct 2026, 03:44 UTC≈7,190 views11 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (955) is ready to test on iOS. What to Test - Built with Xcode 27.2. - Patched the bundled Brotli decoder for CVE-2026-111497. Malformed Brotli responses are now rejected instead of stalling the decoder. This only affects Quantumult X's own decoding for rewrites of Brotli-encoded responses; traffic from other apps passing through the tunnel without such rewrites is forwarded untouche…

❤8👍3

23 Oct 2026, 06:02 UTC≈8,060 views16 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (954) is ready to test on iOS. What to Test - Refined the appearance of the navigation and tab bars on systems earlier than iOS 26. - Streamlined the installation of the self-signed CA root certificate on iOS and macOS. On iOS, Safari no longer needs to be the default browser and the "Not Secure Connection Warning" no longer needs to be turned off. On macOS, the certificate is now ins…

❤11💯2🥰2👍1

13 Oct 2026, 00:28 UTC≈11,000 views16 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (953) is ready to test on iOS. What to Test - Static address mappings for the same domain pattern now stack as well, instead of only the first one taking effect. All mapped addresses are returned together, and connections race them the same way multiple DNS results are handled. A domain can now map to both IPv4 and IPv6 addresses at once; previously the second line was silently ignore…

❤14❤‍🔥2

8 Oct 2026, 13:34 UTC≈11,300 views11 reactionsread 7 November 2026

#TestFlight Quantumult X 1.9.0 (952) is ready to test on iOS/tvOS/macOS. What to Test - Domain-specific DNS settings for the same domain pattern now stack and are queried concurrently, instead of only the first one taking effect. This matches how multiple global DNS servers (DoH / DoQ included) have always worked. - Filter and rewrite rules can carry a leading note: {# note #}. Notes appear in lists and detail page…

❤11

7 Oct 2026, 12:05 UTC≈9,090 views21 reactionsread 7 November 2026

Quantumult X for iOS 正式版更新 1.8.1 商店链接 更新时间: 2026-10-07 更新说明: - Optimized for iPhone Duo. 群组: @QuanXApp 频道: @QuanXNews

👍17❤3👏1

7 Oct 2026, 00:15 UTC≈8,500 views3 reactionsread 7 November 2026

#TestFlight Quantumult X 1.8.1 (951) is ready to test on iOS. What to Test - Built with Xcode 27.1. UI layouts have been adjusted to prepare for the upcoming iPhone Duo. - Local and iCloud resource paths now treat "#" the same way as HTTP/HTTPS URLs, so resource-parser parameters after "#" work the same whether the resource is a file path or a URL. 群组: @QuanXApp 频道: @QuanXNews

❤3

29 Sept 2026, 06:45 UTC≈37,300 views25 reactionsread 7 November 2026

#TestFlight Quantumult X 1.8.1 (950) is ready to test on iOS. What to Test - Built with Xcode 27.1. UI layouts have been adjusted to prepare for the upcoming iPhone Duo. - Domain-specific DNS settings for the same domain pattern now stack and are queried concurrently, instead of only the first one taking effect. This matches how multiple global DNS servers (DoH / DoQ included) have always worked. Unencrypted DNS s…

👍20❤3🔥2

Showing the 12 most recent of 43 posts we hold for @QuanXNews. 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.

Posts edited after publishing

@QuanXNews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
18 September 2026
Most recent edit
18 September 2026

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 19 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.

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.

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

“Quantumult X News” (@QuanXNews), 40,479 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/QuanXNews.

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.