🖊🖊 AN手游功能全防 👑 ⭐️无运行特征 🌸兼容虚拟机 ✅三角洲 三服:子追外 功能全防 ✅和平/逆战/使命/失控:所有公益插件全防 ✅王者/cfm:全局解密 无视下发 ✅QQ飞车:自带防封、加速、无限小喷 🩵官方频道 😱①卡网地址 😍②卡网地址 ✉️反馈
👍3

Channel
@LsilentMod
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,944subscribers
-49 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001542291302 |
|---|---|
| Type | Channel |
| Username | @LsilentMod |
| Description | 客服联系 @QXhh521 Kimi王者顶尖算法解密 多线程绘制渲染,CPU占用极低 拒绝卡框、三方、网络波动 自带 全英雄触摸自瞄 调好配置嘎嘎准 自带王者全英雄皮肤美化 一键即用无需再买钱皮肤 0cpu占比无需担心发热卡顿 |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/LsilentMod |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 00:24 | 14,944 | -10 |
| 11 Aug 2026, 23:12 | 14,954 | -26 |
| 11 Aug 2026, 00:44 | 14,980 | -13 |
| 10 Aug 2026, 02:52 | 14,993 | +1 |
| 9 Aug 2026, 05:04 | 14,992 | -2 |
| 8 Aug 2026, 02:07 | 14,994 | +1 |
| 7 Aug 2026, 14:00 | 14,993 | no change |
| 7 Aug 2026, 13:54 | 14,993 | first reading |
17 posts held, back to 4 June 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 18 pagesof 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 10 August 2026 |
|---|---|
| Posts held | 17 (4 June 2026 – 10 August 2026) |
| Views total | 2,656 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 16:10 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 13 August 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.
66 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 72.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 72.7% | |
| 👍 | 15 | 22.7% | |
| 😱 | 3 | 4.55% |
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 14 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 66reactions 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 4 June 2026 to 10 August 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.
🖊🖊 AN手游功能全防 👑 ⭐️无运行特征 🌸兼容虚拟机 ✅三角洲 三服:子追外 功能全防 ✅和平/逆战/使命/失控:所有公益插件全防 ✅王者/cfm:全局解密 无视下发 ✅QQ飞车:自带防封、加速、无限小喷 🩵官方频道 😱①卡网地址 😍②卡网地址 ✉️反馈
👍3
来个能直播的dy号 @qxhh521
👍4❤2
物是人非
👍8😱3❤1
Kimi公益更新频道 pinned a photo
✨kimi6月17号反馈 👍点击获取Kimi Pro版
❤11
✨kimi6月17号反馈 👍点击获取Kimi Pro版
❤2
服务器崩溃问题修好了 全体加12h☺️
新卡网 https://816.jytos.cn/shop/kimiPro
✨kimi6月15号反馈 👍点击获取Kimi Pro版
❤2
✨kimi6月12号反馈 👍点击获取Kimi Pro版
❤3
✨kimi6月9号反馈 👍点击获取Kimi Pro版
❤5
✨kimi6月8号反馈 👍点击获取Kimi Pro版
❤4
Showing the 12 most recent of 17 posts we hold for @LsilentMod. 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.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Kimi公益更新频道” (@LsilentMod), 14,944 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/LsilentMod.
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.