Telegram RegisterThe public register of Telegram
Telegram profile photo for Project X Channel

Channel

Project X Channel

@projectXtls

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

29,942subscribers

+313 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001408690055
TypeChannel
Username@projectXtls
DescriptionDonation: https://github.com/XTLS/Xray-core/issues/3668 中文群组:https://t.me/projectXray Русский: https://t.me/projectVless Persian: https://t.me/projectXhttp GitHub: https://github.com/XTLS
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/projectXtls

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

29,62929,94229,785.56 August 2026 — 29,629 subscribers6 August 2026 — 29,629 subscribers7 August 2026 — 29,630 subscribers8 August 2026 — 29,632 subscribers9 August 2026 — 29,641 subscribers10 August 2026 — 29,652 subscribers11 August 2026 — 29,676 subscribers12 August 2026 — 29,681 subscribers13 August 2026 — 29,701 subscribers14 August 2026 — 29,716 subscribers16 August 2026 — 29,731 subscribers17 August 2026 — 29,735 subscribers18 August 2026 — 29,748 subscribers19 August 2026 — 29,758 subscribers20 August 2026 — 29,767 subscribers22 August 2026 — 29,775 subscribers24 August 2026 — 29,778 subscribers25 August 2026 — 29,793 subscribers26 August 2026 — 29,803 subscribers27 August 2026 — 29,822 subscribers28 August 2026 — 29,818 subscribers29 August 2026 — 29,826 subscribers30 August 2026 — 29,830 subscribers31 August 2026 — 29,849 subscribers1 September 2026 — 29,852 subscribers2 September 2026 — 29,850 subscribers3 September 2026 — 29,858 subscribers5 September 2026 — 29,900 subscribers9 September 2026 — 29,898 subscribers11 September 2026 — 29,903 subscribers13 September 2026 — 29,916 subscribers15 September 2026 — 29,924 subscribers17 September 2026 — 29,939 subscribers19 September 2026 — 29,941 subscribers26 September 2026 — 29,942 subscribers6 August 202626 September 2026
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)SubscribersChange
26 Sept 2026, 19:3729,942+1
19 Sept 2026, 17:1629,941+2
17 Sept 2026, 02:5729,939+15
15 Sept 2026, 05:3929,924+8
13 Sept 2026, 14:3629,916+13
11 Sept 2026, 15:5729,903+5
9 Sept 2026, 03:5429,898-2
5 Sept 2026, 20:3629,900+42
3 Sept 2026, 19:3829,858+8
2 Sept 2026, 11:3329,850-2
1 Sept 2026, 08:2529,852+3
31 Aug 2026, 07:4429,849+19
30 Aug 2026, 07:0429,830+4
29 Aug 2026, 05:2429,826+8
28 Aug 2026, 08:5329,818-4
27 Aug 2026, 06:2329,822+19
26 Aug 2026, 08:0529,803+10
25 Aug 2026, 05:4329,793+15
24 Aug 2026, 03:4329,778+3
22 Aug 2026, 09:0729,775first 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
WindowRolling 30 days · latest post in window 26 September 2026
Posts held49 (31 July 2026 – 26 September 2026)
Views total164,270
Reactions total1,530
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 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
ReactionCountShareShare, drawn
🤣93724.7%
👍87523.0%
😁62716.5%
🌭2346.16%
❤1905.00%
🍌1604.21%
👏1082.84%
😈681.79%
❤‍🔥481.26%
💯481.26%
🔥451.18%
💅441.16%
💘401.05%
🗿391.03%
🏆381.00%
🆒350.922%
🤩350.922%
🌚270.711%
🤯230.606%
😍200.527%
15 further kinds1574.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.

Recent posts

26 Sept 2026, 02:45 UTC≈3,290 views20 reactionsread 27 September 2026

💬 New comment on Xray-core#6810 MASQUE transport: Add HTTP/2 (Extended CONNECT, RFC 8441) by @RPRX 简单看了下代码,对 h2 而言 Chrome 指纹是 default(但 https://github.com/XTLS/Xray-core/pull/6807 的 h3 默认没开 ChromeParrot,~~没看能不能开~~),h2、h3 都默认不发 Chrome UA(这点与 XHTTP 以及 Xray-core 里其它 HTTP 请求相反)但支持那些特殊值,不过对于这些我暂不确定哪种默认值对 MASQUE 最合适所以等更多反馈后再调整,ALPN 决定 h2/h3 的逻辑也与 XHTTP 相反,毕竟 MASQUE 主场是 h3 说起来对于 XDRIVE 我还没细看指纹和 UA,设想是与 XHTTP 对齐吧,另外 MASQUE…

👍12❤5🤩3

26 Sept 2026, 01:57 UTC≈3,280 views14 reactionsread 27 September 2026

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

💘8💅3🆒3

25 Sept 2026, 19:20 UTC≈3,680 views56 reactionsread 27 September 2026

💬 New comment on BBS#44 墙的倒掉,已经进入按天的倒计时? by @RPRX 内容没看不过光这标题就已经很搞笑了,我早说过只要国内那些种类繁多的内容审查的法律法规存在着,墙就不会被撤掉,不然前者原地变成空气,举个例子比如你封杀了户子,然而人家直接跑境外平台开号,然后这境外平台又能无梯直连,这跟没封杀有啥区别?点到为止不要键政 因为说白了各种内容审查乃至各种墙的实质主要是两大阵营在争权,~~在各自的地盘里放对方的黑料、洗脑自己的民众什么的,同时通过各种手段封杀对自己不利的黑料、打压对对方有利的言论~~,没有绝对的对错毕竟你上你也干,那些二极管只能证明他智商过低或有利可图,别那么傻 不过必然的尴尬就是两大阵营实控的舆论地盘肯定是一大一小,所以为了势均力敌,~~小的那方必然显得得更极权、手段更直接一些比如动不动就 404、给你上个臭名昭著的 GFW,不然小的那方早就被吞并了,而大的那方手段可以隐蔽些比如收买…

👍31🤣12🌭8❤1🌚1🎄1💋1🆒1

25 Sept 2026, 18:24 UTC≈3,690 views26 reactionsread 27 September 2026

💬 New comment on BBS#46 CDN代理WebSocket时开启Early Data的风险 by @RPRX 虽然文章经 AI 润色了但风险确实存在,其实开 VLESS Encryption 就行了不用停用 ed,前者是因为不信任 CDN,后者是不想让 CDN 知道你在跑代理?~~然而 CDN 若想查的话都能查出来,停不停用 ed 没差~~,或者换 HTTPUpgrade,它的 ed 机制不是写 header 里、不会进专属 log,但那些 worker & page 不方便开 enc 或换 hu,但可以 XHTTP,再说 WS/HU 有 ALPN 问题本就不被推荐,**现在过 CDN 只推荐 XHTTP + VLESS enc** 总之就是 XHTTP 天生没有 ALPN、延迟等问题,另外过 CDN 最好开个 VLESS enc,~~虽然其实很多人在用 WARP,感觉都挺信任 Cloudflare 的~~…

🏆14❤4😁4👍2❤‍🔥1🌭1

24 Sept 2026, 05:21 UTC≈6,240 views45 reactionsread 27 September 2026

别笑了别笑了,既然要锐评就锐评完,事实上几天前我更新了 https://github.com/XTLS/Xray-core/issues/6477#issuecomment-5651846548 ,提到了 dyhkwong 的错误也是很重要的一点即 REALITY 旧版代码并没有“假定第一个 key share 必然是 X25519”,然后现在想想才发现“协议设计者在设计协议之初未考虑到 TLS 的潜在变化”的言论可能也是基于此,我说过根据我的设计的时间节点,REALITY 客户端直接切到含 X25519MLKEM768 的指纹并没有明显的兼容性问题,因为当时适合偷的网站都不怎么支持 X25519MLKEM768,仅此一条就已经杀死比赛,刚看了 dyhkwong 已经折叠那个 issue 的所有言论并 unpin 了,但是有一说一我还是会很感谢 dyhkwong 对 Xray-core 代码的审计,并希望他能继续这样做 不过至…

👍27🌭5🆒4❤3😁3☃2👏1

24 Sept 2026, 05:13 UTC≈5,720 views90 reactionsread 27 September 2026

哎surge能和singbox、mihomo平起平坐了

😁57🤣24🗿5🌭1🏆1👏1💯1

24 Sept 2026, 04:55 UTC≈5,780 views56 reactionsread 27 September 2026

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

👍39😁8🆒4💅2🌭1💯1😍1

24 Sept 2026, 04:45 UTC≈5,650 views31 reactionsread 27 September 2026

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

👍14🏆7❤3🔥3👌2💋1🆒1

21 Sept 2026, 04:44 UTC≈8,020 views100 reactionsread 27 September 2026

💬 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…

👍58😁27⚡3❤3🆒3🎄2❤‍🔥1💋1

20 Sept 2026, 21:28 UTC≈7,590 views51 reactionsread 27 September 2026

💬 New comment on Xray-core#6748 XDRIVE transport: Add the Google Drive and "template" backend by @RPRX @Risaro 之前讨论过,“利用聊天/邮箱等服务”这类直接并入 XDRIVE 就行,区别是这些服务可能有主动推送而不用自己去扫 list ~~不过对于聊天软件,审查者本来就严管,比如中国就把境外的全封了,即使用境内的,比如微信语音会检查语言数据是否合理~~ XDRIVE 目前需改为默认 h2+uTLS(若 ALPN 仅 h1 那么只在内层用),以及基于魔改版 quic-go 库引入 h3 https://github.com/XTLS/Xray-core/pull/6754#issuecomment-5751585906 另外需加上配置检测:强制 VLESS Mux 以及 VLESS Encryption,后者是因为…

❤‍🔥25👍18❤4💋3🕊1

19 Sept 2026, 09:18 UTC≈9,140 views145 reactionsread 27 September 2026

Xray-core 已合并 XDRIVE 进 main,第 2000 个 commit,对于俄罗斯、伊朗用户,需先配置好 Google Drive API,记得开 mux.cool,并将 SNI 设为 www.google.com,若某地访问不了 Google,可以试试 template XDRIVE 不仅无视 IP 白名单,还能白名单 SNI domain fronting,至于速度,Google Drive 看起来还不错,其它服务看你们能不能找到快的 评论区有说国内的,额不要自作多情,这协议延迟略高且吞吐量略低,对于国内而言大概永远也成不了主力,除非你追求非常别致的隐蔽翻墙

👍98😁18👏14🤣4🆒3🏆2😈2❤1

14 Sept 2026, 03:35 UTC≈12,100 views154 reactionsread 27 September 2026

💬 New comment on Xray-core#6477 Xray-core v26.7.11 与 mihomo v1.19.28 REALITY 不兼容,连接全部提示 authentication failed by @RPRX > ~流窜AI那边准备一年内接管互联网了,人类开发者还在争论指纹~ 能不能别搞笑了这争论的是指纹吗?分明就是某些人看我不爽又干不掉我所以只能天天拿些鸡毛蒜皮的小事/张冠李戴来攻击我以及 Xray 的事 反正所有问题就必须是我的问题、大问题,不如让我们回顾一下今年我和哪些傻逼对线过: 1. Sukka 看到 REALITY 仓库 maxUselessRecord 是 16 就直接高潮,甚至给我写了七千字小作文,然而我早就给它改成 32 了,16 是别人误改 2. 刘某人韭菜割多了自信心爆棚,竟敢说我不了解 ShadowTLS 的实现细节,结果发现尴尬的是自己,被我喷到退休、连 Surge …

👍94😁23💯12❤10⚡6🕊3🌭2💋2

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

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.

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.

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.

在花🎗️科技圈
@zaihuapd · 283,183
#1
AKILE NOTICE
@akile_notice · 18,623
#2
COALCLOUD(NEW)
@coalcloud · 6,007
#3
港新日美雲服務裸金屬 - 牛彼☁️
@KuaiCheDao_Info · 7,074
#4
2.5次元日常 🍉
@acgdaily · 16,665
#5
每日消费电子观察
@CE_Observe · 75,036
#6
Nanase的随记
@nanaselog · 4,071
#7
SaltyFish.IO
@SaltyFishIO · 3,844
#8
[24H现场直播] PoloCloud的通知
@polocloud_notification · 3,403
#9
折腾啥
@zhetengsha · 49,675
#10
风向旗参考快讯
@xhqcankao · 163,238
#11
VPS信号旗播报
@vps_xhq · 49,725
#12
LoopDNS资讯播报
@DNSPODT · 72,064
#13
NodeSeek官方频道
@nodeseekc · 36,870
#14
主机补货监控 | vps补货监控
@vps_track_share · 3,485
#15
V2Fly - Notification and Updates, V2Ray the second new
@v2fly · 6,357
#16
竹新社
@tnews365 · 164,267
#17
Github_2dust
@github_2dust · 91,529
#18
爆発試験室 | Network & AI | TechNews & LifeStyle
@boomtechreviews · 6,007
#19
Yummy 😋
@GodlyNews1 · 69,298
#20
蓝点网订阅频道
@landiansub · 45,199
#21
zrj766的频道
@zrj96 · 17,202
#22
Faker的个人频道
@wtfbugtoday · 3,018
#23
BestVM公告栏
@BestVmCloud · 2,878
#24
特价VPS分享
@Tjjcfx · 17,854
#25
DMIT Inc - NOC工作日志
@DMIT_INC_CN · 10,839
#26
NodeSeek新帖推送
@hostloc2tg · 4,425
#27
Solidot
@solidot · 47,568
#28
机场稽查局
@VPN_Police · 8,148
#29
V.PS Official Channel
@v_ps_channel · 4,899
#30
Hysteria Releases
@hysteria_releases · 9,833
#31
HyperNAT 通知频道
@hypernat_channel · 2,177
#32
层叠 - The Cascading
@outvivid · 9,009
#33
学习强国公告
@UOVZNEWS · 5,061
#34
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 21,690
#35
希特乐乐
@NyarimeW · 5,909
#36
Arch Linux Chinese Messages
@archlinuxcn · 11,175
#37
Sukka's Notebook
@SukkaChannel · 6,841
#38
YxVM‘s NOTICE
@yxvmcom · 2,466
#39
Newlearnerの自留地
@NewlearnerChannel · 67,412
#40
LetITFly News
@LetITFlyW · 9,586
#41
灵车漂移
@Hearse_Drifting · 10,576
#42
wap.ac
@wap_ac · 3,238
#43
哇沃主机
@wawowiki · 2,728
#44
每日🐔juan迷惑大赏
@damm_it · 819
#45
哪吒监控公告板
@nezhanews · 3,543
#46
PT风向旗
@Ptfxq · 17,196
#47
Surge TestFlight Feed
@SurgeTestFlightFeed · 12,909
#48
Yet Another Public Notification Channel
@yapnc · 7,517
#49
Xray UI
@XrayUI · 36,776
#50
IRCF | اینترنت آزاد برای همه
@ircfspace · 96,110
#51
مرزبان نامه
@Marzban_Nameh · 6,322
#52
/var/log/DMIT-NOC.log
@DMIT_INC · 6,426
#53
XRay Channel
@Gozar_Xray · 8,429
#54
OP™ CluB© 🔒💡
@OPIran_official · 6,008
#55
آموزش VPN
@X2RayNG · 978
#56
iAghapour | Digital Freedom 🎯
@iaghapour · 51,539
#57
V2rayirani
@v2rayiranioriginal · 8,146
#58

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.