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 9 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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
35 measurements spanning 51 days, net +313. 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 29,582–29,989 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
26 Sept 2026, 19:37
29,942
+1
19 Sept 2026, 17:16
29,941
+2
17 Sept 2026, 02:57
29,939
+15
15 Sept 2026, 05:39
29,924
+8
13 Sept 2026, 14:36
29,916
+13
11 Sept 2026, 15:57
29,903
+5
9 Sept 2026, 03:54
29,898
-2
5 Sept 2026, 20:36
29,900
+42
3 Sept 2026, 19:38
29,858
+8
2 Sept 2026, 11:33
29,850
-2
1 Sept 2026, 08:25
29,852
+3
31 Aug 2026, 07:44
29,849
+19
30 Aug 2026, 07:04
29,830
+4
29 Aug 2026, 05:24
29,826
+8
28 Aug 2026, 08:53
29,818
-4
27 Aug 2026, 06:23
29,822
+19
26 Aug 2026, 08:05
29,803
+10
25 Aug 2026, 05:43
29,793
+15
24 Aug 2026, 03:43
29,778
+3
22 Aug 2026, 09:07
29,775
first reading
Engagement
49 posts held, back to 31 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 76 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
28.9%
avg views ÷ 29,942 subscribers
Avg views / post
8,650
19 posts measured
Reaction rate
0.931%
reactions ÷ views · ER floor
Posts in window
19
of 49 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 26 September 2026
Posts held
49 (31 July 2026 – 26 September 2026)
Views total
164,270
Reactions total
1,530
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Sept 2026, 05:41 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
≈208
Videos
≈3
Links
≈1,060
Lifetime counters from Telegram’s own channel header, read 27 September 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.
Video runtime
1m 05s
Average length
1m 05s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
3,798 reactions across 49 posts, in 35 distinct kinds. The most used accounts for 24.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
937
24.7%
👍
875
23.0%
😁
627
16.5%
🌭
234
6.16%
❤
190
5.00%
🍌
160
4.21%
👏
108
2.84%
😈
68
1.79%
❤🔥
48
1.26%
💯
48
1.26%
🔥
45
1.18%
💅
44
1.16%
💘
40
1.05%
🗿
39
1.03%
🏆
38
1.00%
🆒
35
0.922%
🤩
35
0.922%
🌚
27
0.711%
🤯
23
0.606%
😍
20
0.527%
15 further kinds
157
4.13%
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 49 of the 49 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 3,798 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 49 most recent posts we hold, published 31 July 2026 to 26 September 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.
Telegram Stars
Stars received
4
across the posts below
Posts paid on
4
of 49 we hold a reading for · 8%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @projectXtls. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 49 most recent posts we hold for this entry, published 31 July 2026 to 26 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💬 New comment on Xray-core#6828 Burst observatory: Cancel pending HTTP checks
by @RPRX
~~搞得我开始怀疑是不是有人给 AI 下达了自动给 Xray PR 的指令~~
这三个 Burst observatory 的 PR 先合为一个吧不然有点刷屏,~~XHTTP 的那俩可能也能合一起~~,然后先讨论下哪些修改能接受吧
Reply to this message to post a comment on GitHub.
💬 New comment on BBS#44 墙的倒掉,已经进入按天的倒计时?
by @RPRX
内容没看不过光这标题就已经很搞笑了,我早说过只要国内那些种类繁多的内容审查的法律法规存在着,墙就不会被撤掉,不然前者原地变成空气,举个例子比如你封杀了户子,然而人家直接跑境外平台开号,然后这境外平台又能无梯直连,这跟没封杀有啥区别?点到为止不要键政
因为说白了各种内容审查乃至各种墙的实质主要是两大阵营在争权,~~在各自的地盘里放对方的黑料、洗脑自己的民众什么的,同时通过各种手段封杀对自己不利的黑料、打压对对方有利的言论~~,没有绝对的对错毕竟你上你也干,那些二极管只能证明他智商过低或有利可图,别那么傻
不过必然的尴尬就是两大阵营实控的舆论地盘肯定是一大一小,所以为了势均力敌,~~小的那方必然显得得更极权、手段更直接一些比如动不动就 404、给你上个臭名昭著的 GFW,不然小的那方早就被吞并了,而大的那方手段可以隐蔽些比如收买…
💬 New comment on Xray-core#6807 Proxy: Add MASQUE outbound & transport (IETF CONNECT-IP, RFC 9484)
by @RPRX
再多说一点其实就是,有死要面子活受罪的比如 Surge 刘某人,还有“只要 RPRX 支持的就必须是错的”比如 sing-box 世某人的 CDN 是滥用等言论,还有可能是为了兼容性而“把选择权交给用户”的 Mihomo,他们当初还说我批评面板呢,**真给我整笑了机场专用内核的白得不能再白的用户自己竟然有选择的能力说是,我说过历史会证明我推的一系列默认/强制的安全策略是正确的**
Reply to this message to post a comment on GitHub.
💬 New comment on Xray-core#6807 Proxy: Add MASQUE outbound & transport (IETF CONNECT-IP, RFC 9484)
by @RPRX
> 让AI把usque缝进去也就几分钟的事情
说得对但是其实吧我对 AI 写的代码没有任何偏见,我说白了我不懂隔壁那些内核那么喜欢搞功能性代码有什么用,AI 时代只要想的话任何功能都是一天就能搞出来,而真正有价值的其实是维护者的正确的理念,以及天马行空的想法以及把它们固化为标准的执行力 https://github.com/XTLS/Xray-core/pull/6773#issuecomment-5755516423 ,隔壁那些内核最近看我很不爽但我无所谓,**因为我知道只要我想,任何时候都能直接取而代之**
Reply to this message to post a comment on GitHub.
💬 New comment on Xray-core#6773 proxy/tun: configure system DNS on Linux TUN inbound
by @RPRX
~~Xray-core 可以更名 Xray-vibe 了,不是,我看隔壁 3x-ui 天天 vibe 也是挺香的,AI 越来越强了,要不拿赞助费充 GPT-6 Astra~~
AGI 时代 Xray 的核心价值大概是理念:“CDN、网盘等不算滥用”以及各种默认/强制的安全策略等,这些还是得靠维护者来决定
以及 VLESS 相关协议标准:将天马行空的想法设计为标准,并提供两端可互联的预构建 core,下载就能直接运行、节点可分享
还有 VLESS Encryption 这种最好是由人来写、相对一劳永逸的核心加密,~~至于其它的非核心代码,说实话 vibe 一个月要啥有啥~~
Reply to this message to post a…
Showing the 12 most recent of 49 posts we hold for @projectXtls. 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
@projectXtls 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
20 August 2026
Most recent edit
20 August 2026
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 5 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 8 September 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.
Github_2dust @github_2dust · 91,529 Telegram ranks this channel #3 of 71 here — alongside 70 others — read 17 August 2026
LINUX DO Channel @linux_do_channel · 37,311 Telegram ranks this channel #12 of 34 here — alongside 33 others — read 1 September 2026
在花🎗️科技圈 @zaihuapd · 283,183 Telegram ranks this channel #15 of 40 here — alongside 39 others — read 12 August 2026
Surfboard News @surfboardnews · 28,438 Telegram ranks this channel #19 of 64 here — alongside 63 others — read 9 September 2026
每日沙雕墙 @woshadiao · 115,194 Telegram ranks this channel #19 of 52 here — alongside 51 others — read 14 August 2026
Faker | iKun聚集地 @scriptalking · 28,134 Telegram ranks this channel #21 of 41 here — alongside 40 others — read 10 September 2026
风向旗参考快讯 @xhqcankao · 163,238 Telegram ranks this channel #24 of 45 here — alongside 44 others — read 12 August 2026
Matsuridayo GitHub @MatsuriDayo · 45,413 Telegram ranks this channel #29 of 58 here — alongside 57 others — read 30 August 2026
蓝点网订阅频道 @landiansub · 45,199 Telegram ranks this channel #32 of 58 here — alongside 57 others — read 28 August 2026
Shadowrocket News @ShadowrocketNews · 46,826 Telegram ranks this channel #32 of 60 here — alongside 59 others — read 27 August 2026
Legado|开源阅读|频道 @Legado_Channels · 93,002 Telegram ranks this channel #33 of 61 here — alongside 60 others — read 17 August 2026
LSPosed @LSPosed · 194,124 Telegram ranks this channel #33 of 57 here — alongside 56 others — read 17 August 2026
Clash Verge Rev Channel @clash_verge_re · 81,375 Telegram ranks this channel #35 of 64 here — alongside 63 others — read 19 August 2026
竹新社 @tnews365 · 164,267 Telegram ranks this channel #35 of 59 here — alongside 58 others — read 12 August 2026
【李老师不是你老师】官方电报 @lilaoshibushinilaoshi · 48,585 Telegram ranks this channel #36 of 60 here — alongside 59 others — read 26 August 2026
CMLiussss 技术干货分享 @CMLiussss_channel · 67,933 Telegram ranks this channel #37 of 47 here — alongside 46 others — read 21 August 2026
Ruters乳透社🐻 @Ruters0615 · 25,532 Telegram ranks this channel #38 of 40 here — alongside 39 others — read 14 September 2026
QAuxiliary @QAuxiliary · 44,820 Telegram ranks this channel #38 of 58 here — alongside 57 others — read 12 September 2026
LoopDNS资讯播报 @DNSPODT · 72,064 Telegram ranks this channel #38 of 59 here — alongside 58 others — read 20 August 2026
VPS信号旗播报 @vps_xhq · 49,725 Telegram ranks this channel #39 of 57 here — alongside 56 others — read 26 August 2026
每日消费电子观察 @CE_Observe · 75,036 Telegram ranks this channel #39 of 62 here — alongside 61 others — read 19 August 2026
Iyouport @iyouport · 27,814 Telegram ranks this channel #40 of 55 here — alongside 54 others — read 10 September 2026
Nexitally Official Channel @Nexitally_Official · 20,790 Telegram ranks this channel #41 of 44 here — alongside 43 others — read 26 September 2026
NapsternetV @npvchannel · 34,653 Telegram ranks this channel #43 of 43 here — alongside 42 others — read 18 September 2026
This channel appears in 38 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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Project X Channel” (@projectXtls), 29,942 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/projectXtls.
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.