Telegram RegisterThe public register of Telegram

Channel

灵眸三角洲解密通知频道

@lmodfm

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

20,359subscribers

+269 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004294335755
TypeChannel
Username@lmodfm
Description网页雷达共享,一人开挂全队共享 完全不动内存的,纯外部模拟解密 模型掩体陀螺仪自瞄,漏哪打哪
CreatedBetween 1 May 2026 and 4 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/lmodfm

Growth

20,09020,35920,224.56 Aug 2026, 22:47 — 20,090 subscribers6 Aug 2026, 23:04 — 20,098 subscribers7 Aug 2026, 20:00 — 20,359 subscribers6 Aug 2026, 22:477 Aug 2026, 20:00
3 measurements taken within a single day, net +269. 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 20,050–20,399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 20:0020,359+261
6 Aug 2026, 23:0420,098+8
6 Aug 2026, 22:4720,090first reading

Engagement

22 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
50.7%
avg views ÷ 20,359 subscribers
Avg views / post
10,300
22 posts measured
Reaction rate
1.59%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 7 August 2026
Posts held22 (4 August 20267 August 2026)
Views total227,130
Reactions total3,622
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:14 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
19
Videos
3
Links
38

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

3,622 reactions across 22 posts, in 23 distinct kinds. The most used accounts for 58.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🖕2,12558.7%
👍51014.1%
43412.0%
😡2797.70%
😭1082.98%
🍌942.60%
🕊100.276%
🤗90.248%
🤷90.248%
👌60.166%
🙏50.138%
🫡50.138%
👏40.11%
💯40.11%
🤓40.11%
30.083%
🌭30.083%
❤‍🔥20.055%
👾20.055%
💊20.055%
3 further kinds40.11%

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 22 of the 22 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 3,622reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 4 August 2026 to 7 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.

Recent posts

7 Aug 2026, 18:14 UTC≈2,380 views168 reactionsread 8 August 2026

解密和谐等待更新、 无需私信客服,修复好频道会通知

🖕86😡47👍264🍌4🤗1

7 Aug 2026, 08:12 UTC≈5,760 views199 reactionsread 8 August 2026

云更新3.0 重启APP即可 修复部分用户辅助兼容bug

🖕136👍23😡22😭115💘2

6 Aug 2026, 18:54 UTC≈7,530 views169 reactionsread 8 August 2026

邀请推荐朋友灵眸购卡成功的提供完整聊天记录,订单截图跟付款截图可以返卡给你 天卡=返四小时卡密 周卡=返一天卡密 月卡=返一周卡密 推荐满10人额外奖励40元现金 本活动限时三天,过时不返 大家可以去淋雨,嗯嗯这些聊天群找潜在用户推荐返卡 因为目前淋雨,嗯嗯这些公益内核解密几乎都没更新,并且稳定性因为公益的原因,目前经常特征十年,30天都是常态🌟 返卡联系: https://t.me/wsndnb

🖕13527🍌5💊2

6 Aug 2026, 14:13 UTC≈8,360 views215 reactionsread 8 August 2026
File

❤️灵眸三角洲公完美算法解密2.9更新日志 1.算法解密1,算法解密2均已更新最新 2.解密新增服务器校检,非频道购买的正版卡密解密验证失败我这边会随时下发格机 3.新增验证加密校检 真正的算法解密内核,绝不动内存,稳定航天绝密乱杀 需要注意,算法解密,不遁地,不漏人,不过会有轻微的闪框情况出现 ✅APP启动器不依赖mt管理器,完美规避终端检测 🍟物资显示,过滤高价值物资,精确寻包 🔌网页雷达共享,一人开挂全队共享 通知频道: https://t.me/lmodfm https://t.me/lmodfm 卡网下单: https://816.jytos.cn/shop/5E4LZ5CA 客服售后: https://t.me/wsndnb 双向联系机器人: https://t.me/sl_card_bot (解密失败的直接一对一售后解决)

🖕105👍5226😭19😡7👏42

6 Aug 2026, 13:18 UTC≈7,700 views176 reactionsread 8 August 2026

解密一解密二服务器全部关闭,外面的破解版包括正版,现在都没效果 预计10分钟后发布新版本

😡72🖕57👍36🍌53🤓3

6 Aug 2026, 12:48 UTC≈7,690 views158 reactionsread 8 August 2026
Photo

七只羊已经道歉, 大家买卡认准灵眸官方频道

👍67🖕5316🍌9🤷9💯4

6 Aug 2026, 12:40 UTC≈7,710 views81 reactionsread 8 August 2026
Photo

陈*亮,给你最后一次机会,两个小时内频道公开道歉

👍48🖕294

6 Aug 2026, 12:21 UTC≈7,110 views85 reactionsread 8 August 2026

解密2服务器先关了,解密1正常用, 晚点频道会发布最近恶意破解盗版程序进行售卖,的七只羊等人的大头信息以及家人信息 在这里提醒大家,不要玩盗版灵眸,也不要去买盗版卡密 三角洲加密,为千人千面,每次更新都需要用户提供自己的加密日志以及解密uid给我一对一解密,玩盗版根本没有这些售后服务,加密一更新就钱全白花 还有这个神烦狗也是盗版,晚点我会针对盗版进行校验,服务器下发格机验证,以及破解者的个人信息都会公布到频道

👍41🖕336🫡5

5 Aug 2026, 16:49 UTC≈8,920 views253 reactionsread 8 August 2026

这次更新比较快就不加时了🌟 不然有些人家加漏了,又得一个一个补,太麻烦🌟

🖕227😡19👍4🤗3

5 Aug 2026, 16:45 UTC≈27,100 views134 reactionsread 8 August 2026
File

❤️灵眸三角洲公完美算法解密2.8更新日志 1.修复算法解密1闪框 2.网页雷达,服务器被上级查封了,以后都用不了,等我去写局域网雷达吧🍟 3.新增算法解密2,人物绘制有轻微延迟( Um ) 真正的算法解密内核,绝不动内存,稳定航天绝密乱杀 需要注意,算法解密,不遁地,不漏人,不过会有轻微的闪框情况出现 ✅APP启动器不依赖mt管理器,完美规避终端检测 🔌物资显示,过滤高价值物资,精确寻包 🥹网页雷达共享,一人开挂全队共享 通知频道: https://t.me/lmodfm https://t.me/lmodfm 卡网下单: https://816.jytos.cn/shop/5E4LZ5CA 客服售后: https://t.me/wsndnb 双向联系机器人: https://t.me/sl_card_bot (解密失败的直接一对一售后解决)

🖕10720🍌6👍1

5 Aug 2026, 15:51 UTC≈8,820 views105 reactionsread 8 August 2026
Photo

嗯,拿下🌟 然后网页雷达,服务器被上级查封了,以后都用不了,等我去写局域网雷达吧🥹

🖕879👍9

5 Aug 2026, 14:02 UTC≈8,860 views168 reactionsread 8 August 2026

闪框框的不要私信了,马上就能修复,慢则两个小时,快则一个小时

🖕131😭12🍌8😡64👍3❤‍🔥21

Showing the 12 most recent of 22 posts we hold for @lmodfm. 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

Citation-graph rank — 207,645 of 1,151,006entries 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.

Forward network

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.

Mentions

Named by 15 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.

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.

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“灵眸三角洲解密通知频道” (@lmodfm), 20,359 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/lmodfm.

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.