Telegram RegisterThe public register of Telegram
Telegram profile photo for 蓝点网订阅频道

Channel

蓝点网订阅频道

@landiansub

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

47,401subscribers

+4,426 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-1001125882855
TypeChannel
Username@landiansub
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/landiansub

Topic

Hacking & security — 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 92% 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

42,97547,40145,1886 August 202617 November 2026
67 measurements spanning 103 days, net +4,426. 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 42,311–48,065 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
17 Nov 2026, 03:4947,401+76
13 Nov 2026, 20:2847,325+183
11 Nov 2026, 01:2047,142+58
9 Nov 2026, 10:1047,084+86
8 Nov 2026, 00:5846,998+54
6 Nov 2026, 19:4846,944+65
5 Nov 2026, 17:3546,879+56
4 Nov 2026, 18:2746,823+64
3 Nov 2026, 21:4946,759+66
3 Nov 2026, 00:1046,693+61
1 Nov 2026, 23:3646,632+29
31 Oct 2026, 20:2846,603+55
30 Oct 2026, 19:3646,548+102
29 Oct 2026, 19:1946,446+88
28 Oct 2026, 16:4746,358+55
27 Oct 2026, 16:0846,303+50
26 Oct 2026, 15:0646,253+31
25 Oct 2026, 13:1946,222+36
24 Oct 2026, 11:0046,186+27
23 Oct 2026, 09:4546,159first reading

Engagement

1,040 posts held, back to 4 August 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 203 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.69%
avg views ÷ 47,401 subscribers
Avg views / post
3,640
397 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
400
of 1,040 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 17 November 2026
Posts held1,040 (4 August 2026 – 17 November 2026)
Views total1,446,990
Reactions total22,776
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 05:31 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
≈16,100
Videos
≈54
Links
≈14,400

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. 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
4m 56s
Average length
49s

Measured directly from 6 videos 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

64,209 reactions across 992 posts, in 51 distinct kinds. The most used accounts for 23.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁15,11923.5%
🤡13,64121.2%
👍8,19812.8%
👎4,7387.38%
🖕2,2833.56%
🤬1,9683.06%
❤1,6922.64%
🤯1,4952.33%
😱1,4872.32%
🤔1,2852.00%
🥱8851.38%
🤪8821.37%
👌7211.12%
🫡6921.08%
😇6521.02%
😭5970.93%
💊5570.867%
🎉5380.838%
🐳5330.83%
🥰5240.816%
31 further kinds5,7228.91%

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 992 of the 1,000 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 64,209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 10 August 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.

Telegram Stars

Stars received
21
across the posts below
Posts paid on
12
of 992 we hold a reading for · 1%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @landiansub. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 10 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 62 of 400 posts held from the last 30 days (15.5%) 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).

17 Nov 2026, 05:05 UTC640 views12 reactionsread 17 November 2026
Photo

#开源项目 一片动态海底世界装进不足 100KB 的 HTML 里:有开发者通过 Claude Fable 5.2 打造 3D 海底世界开源项目。 这个项目的特点是所有功能仅在不到 100KB 的 HTML 里,加载时的各种生成和渲染都由 GPU 实时生成。 也就是看起来文件很小,但你的 GPU 帮你承担了大部分伤害。 该项目已经开源,有兴趣的用户可以基于项目继续改造和添加更多元素。 以上为内容摘要,在线体验:https://ourl.co/128456 😁订阅 🤔解封 🥰推特 🎉低价VPS

🤡9😴3

17 Nov 2026, 04:34 UTC≈1,210 views25 reactionsread 17 November 2026
Photo

#软件资讯 终于等到你!开源密码管理器 Bitwarden 终于支持 Windows 11 原生通行密钥,其他应用可通过系统调用保险库中的通行密钥。 该功能可以解决的问题是,系统上安装的软件也可以请求通行密钥,此时 Windows 11 会弹出密钥选择框,用户可以从 Bitwarden 里选择密钥。 这个功能也支持配置密钥并保存到 Bitwarden 保险库,后续用户使用时可以直接用密钥登录,不需要复制密码、2FA 验证码。 以上为内容摘要,设置方法:https://ourl.co/128511 😁订阅 🤔解封 🥰推特 🎉低价VPS

👍18😭5❤2

17 Nov 2026, 04:06 UTC≈1,500 views35 reactionsread 17 November 2026
Photo

#行业资讯 神人!德国 Phantasialand 酒店泳池加氯系统靠 Outlook 邮件发警报,结果导致 15 名住户受影响,4 人直接进医院。 这家酒店的自动加氯设备持续向泳池加氯,而监测系统检查到故障后通过 Outlook 给员工发邮件。 上周 Outlook 全球故障,然后员工并未收到邮件通知,于是自动加氯设备就持续向泳池中加氯,直到住户游泳时感到不适才通知工作人员。 PS:这哪个大聪明想起来用 Outlook 来推送安全警报的。 以上为内容摘要,查看全文:https://ourl.co/128510 😁订阅 🤔解封 🥰推特 🎉低价VPS

😁26🤡6🕊2😇1

17 Nov 2026, 03:34 UTC≈1,650 views7 reactionsread 17 November 2026
Photo

#系统资讯 服务器系统 Windows Server 2016 将在明年 1 月结束 5 年免费扩展支持,微软开启 ESU 付费扩展更新。 对于符合条件的标准版和数据中心版,客户可以购买 ESU 许可证继续获得最长 3 年更新。 而 Essentials 和 MultiPoint Premium 版不支持购买许可证, 使用这些版本的企业应当尽快迁移。 以上为内容摘要,查看全文:https://ourl.co/128509 😁订阅 🤔解封 🥰推特 🎉低价VPS

😁6🤡1

17 Nov 2026, 03:03 UTC≈1,890 views24 reactionsread 17 November 2026
Photo

#人工智能 腾讯 WorkBuddy 上线混元 HY4 Flash 模型且免费使用,限免活动到 11 月 30 日结束。 该模型适合在深度搜索、文档处理、PPT 生成、简单前端展示以及 Computer Use 等多数日常任务中使用。 WorkBuddy 将每日向用户赠送免费额度,用户可以优先使用 HY4 Flash 免费额度这样不需要消耗付费积分。 以上为内容摘要,查看全文:https://ourl.co/128508 😁订阅 🤔解封 🥰推特 🎉低价VPS

👍15🤩5🕊1🤡1🥱1😁1

17 Nov 2026, 02:35 UTC≈1,980 views24 reactionsread 17 November 2026
Photo

#软件资讯 谷歌反重力将 3 款 Gemini 4 模型上下文压缩窗口翻倍,可以减少长程任务频繁触发压缩并缩短完成时间。 反重力产品负责人瓦伦莫汉称,反重力中的 Argon、Carbon 和 Hydrogen 上下文窗口翻倍,更新后预计每个用户回合压缩次数将减少 3.5 倍。 不过瓦伦莫汉并未说明压缩阈值具体是多少,也就是最终还是由服务器决定是否压缩。 以上为内容摘要,查看全文:https://ourl.co/128507 😁订阅 🤔解封 🥰推特 🎉低价VPS

🤡19👍3🤔1😁1

17 Nov 2026, 02:04 UTC≈2,350 views13 reactionsread 17 November 2026
Photo

#安全资讯 又是针对 iOS 18.x 的零点击攻击:荷兰广告公司 NextDay Media 被攻击,黑客篡改广告向 15 家网站读者投毒。 此次投毒大概率也与 DarkSword 攻击框架有关,因为同样是针对 iOS 18.x 旧版本的。 这家广告公司覆盖 150 家网站,每月访问者合计达到 1200 万。 只要用户访问包含恶意广告的网站就会自动感染,而将 iOS 升级到最新版是唯一解决办法。 以上为内容摘要,查看全文:https://ourl.co/128506 😁订阅 🤔解封 🥰推特 🎉低价VPS

😁9👍2🙏2

17 Nov 2026, 01:36 UTC≈2,660 views52 reactionsread 17 November 2026
Photo

#人工智能 埃隆马斯克还是依然非常与众不同:Grok API 文本输出盲水印政策已改成默认关闭。 此前 SpaceXSI 发布通知称将从 11 月 7 日开始部署文本输出盲水印机制,通过 SynthID Text 机制识别文本由模型生成。 不过现在政策已经调整为默认关闭,除非用户所在地有法律要求或用户主动开启。 很多用户并不喜欢盲水印机制,所以调整后倒是符合很多用户的心意。 以上为内容摘要,查看全文:https://ourl.co/128505 😁订阅 🤔解封 🥰推特 🎉低价VPS

👍47🤔3🥱1😁1

17 Nov 2026, 01:05 UTC≈2,630 views34 reactionsread 17 November 2026
Photo

#安全资讯 广告拦截插件都能有漏洞?uBlock Origin 被曝出高危跨站漏洞。 恶意网站可以利用漏洞诱导用户添加可信规则,然后在其他网站上运行恶意脚本。 安全研究员发现漏洞后立即通报给 uBlock Origin 项目,在 11 月 3 日 uBo 发布 1.75.4 修复主要漏洞,之后陆续发布 1.76.0 和 1.76.4 增加过滤器校验和其他限制。 对用户而言最好直接更新到 1.76.4 或更高版本,建议使用 uBo 的用户立即检查版本。 以上为内容摘要,查看全文:https://ourl.co/128504 😁订阅 🤔解封 🥰推特 🎉低价VPS

😱30❤2😁2

17 Nov 2026, 00:33 UTC≈2,440 views13 reactionsread 17 November 2026
Photo

#系统资讯 继续修修补补:微软发布 OOB 带外更新解决 KMS 激活问题,该问题由上周发布的 11 月更新引起。 这个问题主要影响使用 KMS 激活的企业和云数据中心,当然如果有些用户使用的激活工具基于 KMS 那也受影响。 遇到 KMS 激活出现 0x80041008 的用户请下载安装最新 OOB 更新,安装后再激活即可。 以上为内容摘要,下载地址:https://ourl.co/128503 😁订阅 🤔解封 🥰推特 🎉低价VPS

🤡12😁1

16 Nov 2026, 08:26 UTC≈4,250 views118 reactionsread 17 November 2026
Photo

Codex这算翻车么 口碑一下子差了这么多 😁订阅 🤔解封 🥰推特 🎉低价VPS

😁97🎉17🍾3👏1

16 Nov 2026, 08:17 UTC≈4,020 views26 reactionsread 17 November 2026
Photo

#行业资讯 一次正常的故障切换怎么引发 Microsoft 365 全球范围内宕机? 微软发布 11 月 12 日事件初步调查报告。 问题根源是 7 月份部署的代码有缺陷,但由于测试环境与生产环境不同,微软并未发现问题。 在事故发生前 15 小时,Teams 故障切换叠加网关服务器部分容量下线,触发代码缺陷进而造成级联故障。 另外微软也强调故障与 AI 或网络攻击无关。 以上为内容摘要,查看全文:https://ourl.co/128502 😁订阅 🤔解封 🥰推特 🎉低价VPS

😁25🎉1

Showing the 12 most recent of 1,040 posts we hold for @landiansub. 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

@landiansub edited 19 posts 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
10 August 2026
Most recent edit
10 November 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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 36 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

风向旗参考快讯
@xhqcankao · 174,698
#1
在花🎗️科技圈
@zaihuapd · 290,717
#2
LoopDNS资讯播报
@DNSPODT · 73,367
#3
每日消费电子观察
@CE_Observe · 77,903
#4
Yummy 😋
@GodlyNews1 · 71,283
#5
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,536
#6
VPS信号旗播报
@vps_xhq · 50,960
#7
Solidot
@solidot · 48,880
#8
层叠 - The Cascading
@outvivid · 9,324
#9
Newlearnerの自留地
@NewlearnerChannel · 68,327
#10
APPDO的互联网记忆
@appdopic · 16,990
#11
QQ/TIM Update Log
@qq_updatelog · 6,993
#12
YoshinoDaily
@Yoshino0721 · 1,228
#13
 Apple Nuts
@AppleNuts · 37,728
#14
灵车漂移
@Hearse_Drifting · 10,896
#15
少数派sspai
@sspai · 39,190
#16
Telegram Info 中文
@tginfocn · 5,879
#17
Sukka's Notebook
@SukkaChannel · 6,942
#18
卖动的摸鱼日常
@MaiTungTM_Notes · 2,671
#19
硬件观察 VER3.0 With HOMOLAB
@SUPERNAND · 6,884
#20
折腾啥
@zhetengsha · 54,462
#21
APPDO 数字生活指南
@AppDoDo · 41,000
#22
QQ Updates
@QQUpdates · 10,269
#23
竹新社
@tnews365 · 167,438
#24
每日沙雕墙
@woshadiao · 114,465
#25
2.5次元日常 🍉
@acgdaily · 17,363
#26
橘橘橘子汁 & 🍊
@microblock_pub · 16,078
#27
LetITFly News
@LetITFlyW · 9,741
#28
rvalue的生草日常
@rvalue_daily · 8,823
#29
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,403
#30
Android Weekly Update ⚡️
@update4weekly · 5,238
#31
Project X Channel
@projectXtls · 30,596
#32
gledos Lia green 的微型博客
@gledos_microblogging · 6,609
#33
企业级欢乐花园
@MaterialDesign3 · 9,211
#34
新·世界观察日志
@NewWorldObservationLog · 7,072
#35
简中互联网废物大赏
@fucku_idiot · 41,945
#36
心灵魔法站
@personal_hub · 11,586
#37
Faker的个人频道
@wtfbugtoday · 3,185
#38
希特乐乐
@NyarimeW · 6,029
#39
今天abc看了啥🤔
@abcthoughts · 7,149
#40
kMBRjund/0 🧊
@MBRjunDaily · 2,093
#41
品测
@SIM_CN · 9,976
#42
凯露酱的朋友圈
@HakureiKyaru · 2,466
#43
Soha 的日常
@sohadays · 4,831
#44
Office Tool Plus 📰
@otp_channel · 7,258
#45
RandomFree
@c001apk · 6,492
#46
Voyager HyperOS Update
@VoyagerMIUIUpdate · 22,359
#47
Arch Linux Chinese Messages
@archlinuxcn · 11,277
#48
咕谷の小窝 | 咕
@Goo_nest · 3,486
#49
5ec1cff
@real5ec1cff · 40,324
#50
你有一个打折需要了解
@SteamNy · 16,262
#51
Appinn Feed|小众软件
@appinnfeed · 35,004
#52
LSPosed
@LSPosed · 202,184
#53
<NullPointerException> 二周目
@NullPointerA · 893 (as read 28 August 2026)
#54
机场稽查局
@VPN_Police · 8,338
#55
青鸟的频道
@bluebird_channel · 7,946
#56
平壤卫视
@pingrangTV · 29,375
#57
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,633
#58

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.

不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,536
Telegram ranks this channel #2 of 54 here — alongside 53 others — read 23 September 2026
Clash Verge Rev Channel
@clash_verge_re · 86,759
Telegram ranks this channel #3 of 64 here — alongside 63 others — read 19 August 2026
nmBot 频道
@nmbotchannel · 35,295
Telegram ranks this channel #5 of 42 here — alongside 41 others — read 12 September 2026
Yummy 😋
@GodlyNews1 · 71,283
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 20 August 2026
树洞🌳群友问❓有点意思🗳
@qunyouwen · 88,948
Telegram ranks this channel #5 of 67 here — alongside 66 others — read 17 August 2026
LoopDNS资讯播报
@DNSPODT · 73,367
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 20 August 2026
在花🎗️科技圈
@zaihuapd · 290,717
Telegram ranks this channel #6 of 40 here — alongside 39 others — read 12 August 2026
少数派sspai
@sspai · 39,190
Telegram ranks this channel #7 of 58 here — alongside 57 others — read 31 August 2026
油油の科技软件资源分享
@youyousharechannel · 92,483
Telegram ranks this channel #7 of 43 here — alongside 42 others — read 17 August 2026
风向旗参考快讯
@xhqcankao · 174,698
Telegram ranks this channel #7 of 45 here — alongside 44 others — read 12 August 2026
Solidot
@solidot · 48,880
Telegram ranks this channel #8 of 59 here — alongside 58 others — read 28 August 2026
VPS信号旗播报
@vps_xhq · 50,960
Telegram ranks this channel #8 of 57 here — alongside 56 others — read 26 August 2026
黑科技软件资源分享
@kkaifenxiang · 261,888
Telegram ranks this channel #8 of 39 here — alongside 38 others — read 19 August 2026
极客分享
@geekshare · 65,687
Telegram ranks this channel #9 of 44 here — alongside 43 others — read 21 August 2026
每日消费电子观察
@CE_Observe · 77,903
Telegram ranks this channel #9 of 62 here — alongside 61 others — read 19 August 2026
FlClash Channel
@FlClash · 55,108
Telegram ranks this channel #10 of 53 here — alongside 52 others — read 28 August 2026
Newlearnerの自留地
@NewlearnerChannel · 68,327
Telegram ranks this channel #12 of 62 here — alongside 61 others — read 21 August 2026
Widget🏂软件工具资源分享
@WidgetChannel · 108,310
Telegram ranks this channel #12 of 44 here — alongside 43 others — read 17 August 2026
APPDO 数字生活指南
@AppDoDo · 41,000
Telegram ranks this channel #13 of 57 here — alongside 56 others — read 30 August 2026
Shadowrocket News
@ShadowrocketNews · 47,299
Telegram ranks this channel #13 of 60 here — alongside 59 others — read 27 August 2026
秀儿の科技软件|资源分享社🎀
@jianjiaoPD · 134,043
Telegram ranks this channel #14 of 42 here — alongside 41 others — read 4 September 2026
黑洞资源笔记
@piracy6 · 78,112
Telegram ranks this channel #14 of 61 here — alongside 60 others — read 19 August 2026
Real Nullptr
@nullptr_dev · 21,505
Telegram ranks this channel #15 of 54 here — alongside 53 others — read 28 September 2026
ChatGPT / AI新闻聚合
@AI_News_CN · 23,405
Telegram ranks this channel #15 of 45 here — alongside 44 others — read 22 September 2026

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

“蓝点网订阅频道” (@landiansub), 47,401 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/landiansub.

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.