Channel
@SlagLAB
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
121subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003302563483 |
|---|---|
| Type | Channel |
| Username | @SlagLAB |
| Description | Slaglab.com SlagLAB/余烬实验室 |
| Created | 24 May 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/SlagLAB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 03:46 | 121 | no change |
| 7 Aug 2026, 14:38 | 121 | +3 |
| 6 Aug 2026, 14:52 | 118 | first reading |
17 posts held, back to 24 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 17 (24 May 2026 – 27 July 2026) |
| Views total | 96 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:46 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.
Lifetime counters from Telegram’s own channel header, read 9 August 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.
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.
5 reactions across 1 post, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 3 | 60.0% | |
| ❤ | 1 | 20.0% | |
| 😁 | 1 | 20.0% |
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 3 of the 17 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 24 May 2026 to 27 July 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.
*更新 OmnXT VPN 核心 SDK。 *新增 iOS Packet Tunnel 支持。 *修复 NPanel 支付方式解析兼容问题。 *修复支付跳转及空订阅数据处理。 *优化服务端真实错误信息展示。 *新增多订阅切换及节点自动刷新。 *新增套餐变更、升级购买及差额预览。 *优化默认品牌图标和启动页面。 *修复订单预览错误提示。 *新增客户自主关闭工单。 *新增纯邀请码分享，隐藏二维码和推广地址（可选） *新增APP内余额充值入口，支持外部浏览器跳转（可选）
Channel name was changed to «SlagLAB-VPN客户端订阅频道»
*新增节点假延迟功能（可选） *修复了客户自定DNS导致部分网站无法访问的BUG
*针对低端型号安卓机器性能优化 *现在地图支持更高的刷新率了
定制功能交付完毕 使用文档均标准化交付
*xiaov2board 新增试用账户APP显示功能 *xiaov2board 新增邮箱验证码登录，找回等功能 *优化app测速延迟逻辑 *修复若干安卓机兼容等问题
*修复 FakeIP 映射表刷新逻辑问题。 *支持 Trojan UDP 转发。 *地图改为离线渲染，解决部分地区无法加载在线地图资源的问题。 *新增托管地址获取域名 API 失败报错提示。
### 新增 * 新增根据节点标签自定义国家/地区图标覆盖功能。 * 新增对 V2Board 套餐扩展 JSON 格式的解析与展示支持。 ### 优化 * 优化多套餐场景下的套餐信息展示逻辑。 * 优化节点国家识别与显示机制，提高显示准确性。 ### 修复 * 修复多套餐情况下套餐显示被覆盖的问题。 * 修复 Windows 特定系统环境下界面边框显示异常的问题。
🤡3❤1😁1
购买任何授权版的顾客，例如先买年付授权再后续转买断，都只需要补差价即可哦～
之前定制版的老用户回访评价😁
欢迎各位加入订阅频道。 在市面上拥有如此众多客户端的情况下，为什么选择我们呢？ 1，我们目前拥有TG圈内，技术实力几乎最强的技术团队。 拥有能重构核心，能够开发独立协议支持的能力；可以任意定制添加任何您想要的功能 2，目前有与数家百万级机场的合作，可以解决任何你面临的技术难题 3，目前的客户端已经是经过N次迭代，无任何使用bug的状态，入手即用
SlagLAB出品，次时代VPN客户端为您呈现： 1，自研SlagCore©核心，Rust重构，无内存回收，极致轻量化与超强稳定性，全端小于40m，告别闪退 2，内嵌SlagPulse©节点地图，划时代的APP交互体验 3，第一款支持手机号注册（可选）的VPN客户端，为您带来巨量用户转化 4，v2board，x2board，SSP，PPANEL 等主流面板完美支持。 5，全端统一UI，可替换您自己的LOGO，大厂的审美设计，远超市面上的换壳产品 6，具备市面上其他客户端的所有功能，包括不限于 邀请/兑换码/工单/客服/oss托管等 7，开发组成员来自ExpressVPN等顶级大厂，拒绝技术拼凑 8，后续免费更新，全自助打包，不收任何其他费用 欢迎访问:Slaglab.com 获取客户端详细介绍以及三端DEMO下载 商务联系：@SlagAlex 技术支持：@SlagNeko 订阅频道 t.me/SlagLAB 群组 t.me…
Showing the 12 most recent of 17 posts we hold for @SlagLAB. 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 — 352,686 of 1,336,469entries 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.
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.
Named by 1 registered channel — 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“SlagLAB-VPN客户端订阅频道” (@SlagLAB), 121 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/SlagLAB.
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.