Channel
@crosswall_knowledge
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,852subscribers
+103 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002516534198 |
|---|---|
| Type | Channel |
| Username | @crosswall_knowledge |
| Created | Between 1 March 2025 and 23 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/crosswall_knowledge |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:34 | 2,852 | +33 |
| 10 Aug 2026, 00:29 | 2,819 | +58 |
| 6 Aug 2026, 20:55 | 2,761 | +12 |
| 6 Aug 2026, 05:17 | 2,749 | no change |
| 6 Aug 2026, 04:08 | 2,749 | first reading |
14 posts held, back to 23 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 18 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
126 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 62.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 79 | 62.7% | |
| 🤪 | 23 | 18.3% | |
| 😢 | 9 | 7.14% | |
| 👍 | 8 | 6.35% | |
| 😁 | 4 | 3.17% | |
| ☃ | 3 | 2.38% |
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 12 of the 14 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 126reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 23 May 2025 to 18 May 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.
🚀 CrossWall (克洛斯) 高速大流量机场 每天一毛钱，看遍全世界 💰 超级实惠 48元/年 → 每月285GB 132元/年 → 每月1200GB ⚡️ 闪电速度 国际高速优质线路 高清视频/下载，告别卡顿 ⚙️ 智能调度 独家DNS算法平衡负载 人多不卡顿！ 🌐 全球畅行 13地域30+节点 解锁Netflix/Tiktok/Disney+等平台 📍 特殊地区支持 新疆/河南/江苏/福建等地稳定可用！ 📱 多端支持 手机、电脑、平板，一键搞定 💎 高端品质，平民价格。一键开启全球化人生。 🔗 官网 | 💬 群组 | 🚀 测速 | 💰定价
❤10
紧急通知。近几个版本的clash verge的ip显示卡片由于开发bug导致对以下几个域名的疯狂请求。近乎于对这几个网站发起ddos攻击。 ipapi.co ipapi.is ipwho.is ip.sb 我们已经发现此问题，并将近期检测到的疑似发起攻击行动的用户解除封禁处理。 在clash verge开发者修复此bug前 如您使用clash verge客户端，请按照图片操作暂时停止ip卡片的显示。
❤2
IOS ClashMi 开启ipv6支持 核心设置 —> IPv6 选择不覆写或者启用 本站订阅已默认启用ipv6的支持，如您使用了三方订阅转换请选择启用
PC端 windows/MAC Flclash开启ipv6的支持 工具 -> 基本配置 -> 常规 -> IPv6 选中开启 另外确保 工具 -> 基本配置 -> DNS --> 覆写DNS 保持未选中关闭状态
什么是“分流”？如何让国内 App 不走节点？ 很多用户担心：开了 CrossWall，刷抖音、用支付宝会不会变慢？甚至导致国内账号异地登录异常？ 核心技术：分流（Split Tunneling）。 工作原理： 客户端内置了一张“地图”。访问百度、微信时，直接走本地网络（直连）；访问 Google、YouTube 时，才自动切换到 CrossWall 节点。 实用操作： 1. 将路由模式设置为 “绕过局域网及大陆地址” (Bypass Mainland China) 。 2. clash verge 等使用 规则模式 3. 小火箭全局路由使用配置 这样你既能流畅刷 YouTube，国内 App 依然保持原生网速，两不误。
❤1
五一我要流量自由第二弹 回复此消息发送 “五一我要流量自由第二弹” →全场85折优惠码 5月7日23:59 抽奖自动开启 共计200份。不限套餐，年付及以下周期均可用。
❤2👍1
PC端 windows / MAC ClashVerge开启ipv6的支持 设置—> ipv6 按钮选中开启 并确保 设置 -> DNS覆写 为关闭状态
❤1
shadowrocket 小火箭的一个小知识。在iphone充电温度较高时可能shadowrocket会自己中断连接。可以在设置—>其他—>提醒 打开vpn断开时提醒。
❤13☃3
关于tg使用转圈的问题。如果你使用tg而且群或者频道比较多，特别是使用手机流量带宽有限的时候。关闭群和频道的自动下载往往是有效的做法。 您可以根据网络环境（移动数据、Wi-Fi）分别关闭图片、视频和文件的自动下载选项 手机在 设置>数据和存储>自动下载媒体。 pc版在 设置>高级 >自动下载媒体
❤18
12.21 最新节点测速
🤪23❤14😢9👍6😁4
今天早上5:50-6:20,著名公共dns 1.1.1.1发生故障。由于节点全部采用此dns解析。节点都受到影响。目前所有节点都添加了多个dns备份。
套餐更新增加 "超值24" 套餐 年付24 152G/月
❤7
Showing the 12 most recent of 14 posts we hold for @crosswall_knowledge. 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.
Citation-graph rank — 123,951 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 10 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“CrossWall (克洛斯)知识库” (@crosswall_knowledge), 2,852 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/crosswall_knowledge.
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.