反馈加时: @mol86888
👍3

Channel
@molaicn
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
22,543subscribers
-1,521 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001831893056 |
|---|---|
| Type | Channel |
| Username | @molaicn |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/molaicn |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 06:55 | 22,543 | -225 |
| 19 Sept 2026, 08:22 | 22,768 | -82 |
| 16 Sept 2026, 21:41 | 22,850 | -40 |
| 15 Sept 2026, 00:20 | 22,890 | -38 |
| 13 Sept 2026, 12:39 | 22,928 | -69 |
| 11 Sept 2026, 14:17 | 22,997 | -115 |
| 9 Sept 2026, 00:36 | 23,112 | -123 |
| 5 Sept 2026, 19:59 | 23,235 | -82 |
| 3 Sept 2026, 15:38 | 23,317 | -38 |
| 2 Sept 2026, 10:34 | 23,355 | -22 |
| 1 Sept 2026, 07:13 | 23,377 | -36 |
| 31 Aug 2026, 07:57 | 23,413 | -37 |
| 30 Aug 2026, 04:44 | 23,450 | -32 |
| 29 Aug 2026, 04:24 | 23,482 | -44 |
| 28 Aug 2026, 06:17 | 23,526 | -23 |
| 27 Aug 2026, 05:04 | 23,549 | -19 |
| 26 Aug 2026, 07:44 | 23,568 | -21 |
| 25 Aug 2026, 05:46 | 23,589 | -41 |
| 24 Aug 2026, 07:12 | 23,630 | -37 |
| 22 Aug 2026, 16:22 | 23,667 | first reading |
173 posts held, back to 3 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 63 pages of 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 29 September 2026 |
|---|---|
| Posts held | 173 (3 August 2026 – 29 September 2026) |
| Views total | 25,149 |
| Reactions total | 121 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 00:59 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 30 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.
593 reactions across 140 posts, in 7 distinct kinds. The most used accounts for 93.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 554 | 93.4% | |
| ⚡ | 17 | 2.87% | |
| ☃ | 9 | 1.52% | |
| 🍾 | 6 | 1.01% | |
| 🏆 | 4 | 0.675% | |
| 🎄 | 2 | 0.337% | |
| 🙏 | 1 | 0.169% |
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 140 of the 173 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 593 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 173 most recent posts we hold, published 3 August 2026 to 29 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.
反馈加时: @mol86888
👍3
👁️ 全场透视(ESP) 人物 —— 骨骼 / 方框 / 血量 / 距离 / 名字 / 手持武器 / 队伍识别 物资 —— 1190 项名称库,价值自动换算成「W」,品质分色(1~6 级可单独开关) 容器 —— 23 类:快递箱 / 医疗包 / 保险箱 / 大武器箱 / 弹药箱 / 服务器…… 威胁物 —— 36 类:手雷 / 箭矢 / 陷阱 / 无人机 / 巡飞弹,带名称 + 距离 + 颜色 雷达 —— 小地图 + 大地图双视角,含撤离点 / 拉闸点标记 盒子 —— 玩家尸体 / 容器内物品透视 🎯 自瞄系统 模式 原理 普通触摸 直接改相机角度,响应最快 触摸自瞄 虚拟手指拖视角,兼容性最好 陀螺仪自瞄 角速度注入,跟手丝滑 可调项 —— 平滑 X/Y、死区、自瞄范围、自瞄距离、部位选择(头/胸/自动)、压枪补偿、开镜自瞄、磁性扳机 💎 GT 解密版特色 断点模拟 —— 绕开常规内存检测 稳定性优先 —— 专项…
👍5⚡1
Photo, posted without a caption
👍2
Photo, posted without a caption
👍2
Photo, posted without a caption
👍1
外加进货一把
👍1
ZOM1.2.zip 已更新UDP解密 模型漏打 大地图小地图绘制 完美自瞄算法 解密大厅直接开启 检测到加密自动解密 本地模型漏打识别变色 绘制流畅丝滑 帧数稳定 全物资显示 敌人头甲 手持 血量等等 目前只支持三角洲国服 赞助地址: https://816.zidianidc.com/shop/77YR9GLP 任何问题反馈:@mol86888 官方频道:@ZOM1088
👍7
公益卡密: ZOMWW09200IMH8AE
🍾2
Photo, posted without a caption
👍2
Photo, posted without a caption
👍2
打了两天了新号打到28级没封过一次
👍4
Photo, posted without a caption
👍4
Showing the 12 most recent of 173 posts we hold for @molaicn. 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.
@molaicn edited 2 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.
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.
Named by 2 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Mol莹石-7.30已回归” (@molaicn), 22,543 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/molaicn.
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.