Telegram RegisterThe public register of Telegram

Channel

蓝月亮通知频道

@Lyuelian

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

5,067subscribers

-18 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001867340059
TypeChannel
Username@Lyuelian
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Lyuelian

Growth

5,0675,0855,0768 August 2026 — 5,085 subscribers8 August 2026 — 5,085 subscribers12 August 2026 — 5,067 subscribers8 August 202612 August 2026
3 measurements spanning 4 days, net -18. 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 5,064–5,088 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:175,067-18
8 Aug 2026, 21:305,085no change
8 Aug 2026, 14:155,085first reading

Engagement

21 posts held, back to 25 March 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
4.17%
avg views ÷ 5,067 subscribers
Avg views / post
212
4 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
4
of 21 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 12 August 2026
Posts held21 (25 March 202612 August 2026)
Views total846
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 06:00 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.

Reaction mix

36 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 63.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2363.9%
🤡822.2%
👍25.56%
🤔25.56%
🍌12.78%

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

Measured over the 21 most recent posts we hold, published 25 March 2026 to 12 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

12 Aug 2026, 05:42 UTC18 views1 reactionsread 12 August 2026
Photo

哦丢雷楼谋

👍1

Signed 辰 风(直奔主题)

11 Aug 2026, 16:45 UTC115 views1 reactionsread 12 August 2026
Forwarded from @chenfengyaPhoto

新号好玩,航天黑屋

🤡1

Signed 辰 风(直奔主题)

10 Aug 2026, 15:48 UTC222 views3 reactionsread 12 August 2026

小米pad6pro12+256 1150rmb出 急出,我要买刀皮号 要的私信我 @chenfengya13 我咸鱼让这傻子官方限制了

🤔21

Signed 辰 风(直奔主题)

9 Aug 2026, 16:16 UTC491 views8 reactionsread 12 August 2026
Photo

瞧一瞧看一看

🤡7👍1

Signed 辰 风(直奔主题)

23 Jun 2026, 16:36 UTC≈6,420 views6 reactionsread 12 August 2026
Photo

EncryptBlitz 加密引擎 · 公测进度同步 当前定位: EncryptBlitz 正在建设面向 ARM64 Native 场景的高强度加密与函数级保护基础设施,覆盖 ELF / SO / SO-JNI 等目标形态。核心加密链路、Web/API/CLI 工作流和样本验证体系已完成多轮压测,目前进入兼容性攻坚阶段。 当前重点: 函数级虚拟化 VMP、VMP 强化、手选函数、运行时验证等能力正在持续优化。不同项目的编译器、函数结构、符号信息、入口形态差异很大,个别样本出现无法虚拟化、降级、任务异常或运行不一致,都属于我们当前重点收敛的问题。 遇到任何异常,请直接在群内反馈或私信管理。每一个真实 case 都会进入兼容性修复队列,是我们提升正式版质量的关键输入。 关于收费节奏: 安全产品零容忍。当前加密能力已经进入可公开测试阶段,但在兼容性体验和交付稳定性达到正式商业化标准前,我们会继续免费开放试用。我们宁愿晚一步收费

6

8 Jun 2026, 15:05 UTC≈1,190 views2 reactionsread 12 August 2026
Forwarded from @BlitzTrainer

EncryptBlitz 现已面向全网开放体验 访问地址: https://jm.byxly.vip/ EncryptBlitz 是面向 Native ARM64 目标的在线加固平台,支持 ELF、SO、SO-JNI 上传分析与保护配置。平台提供函数级选择、函数加密、函数混淆、函数 VMP、VMP 强化、Custom 自定义策略、任务进度、中文报告与加固产物下载,适合 SDK、游戏逻辑、授权校验、核心算法、风控模块等 Native 资产的上线前加固与交付测试。 本次开放免费体验卡密,每张卡额度 100 点。卡密无 IP 绑定,可自由登录使用;额度用完后仍可参与后续福利活动,更多免费额度、测试名额和优惠权益会陆续开放。 相比传统加固厂商,EncryptBlitz 更偏向“可控、透明、函数级”的 Native 保护体验: - 不只整包黑盒处理,支持函数级精确选择 - 不强制推荐策略,保护层由用户自行配置 - 不只给产物,也提

2

6 Jun 2026, 11:00 UTC994 views0 reactionsread 12 August 2026
Forwarded from @BlitzTrainer

想要免费提前体验满血版EncryptBlitz(免费防御全开,有函数级VMP等超强加密)加密 可联系企鹅:2987303932 目前支持:APK 安装包,AAB 应用包,APKS 分包集,ELF 可执行文件,SO / 普通共享库,SO-JNI / JNI 动态库,Shell 脚本,Script 脚本,EXE / Android ARM64 可执行文件

6 Jun 2026, 10:44 UTC950 viewsread 12 August 2026
Forwarded from @BlitzTrainerFile

开源一下三角洲的过内存检测的一个思路 里面自带4个功能,露娜,无后,据点,范围 不100%保证稳定性 思路:“sub_4DEC14 负责维护一个全局 Patch 跳过池 qword_568F90`。该池采用 32 槽位的环形缓冲结构,每条记录占 24 字节,数据结构为 {uint64_t 绝对地址, uint32_t 长度, uint32_t 保留位(0), uint64_t 堆副本指针}`。 扫描链入口 `sub_4E0834` 首先调用 sub_4DED68 遍历此池,执行纯区间交集判定(`rec.start < scan_end && rec.start + rec.size > scan_start`)。若命中,则将匹配记录逐条拷贝至临时输出向量,输出指针每命中一条即推进 0x18 字节。需注意,`sub_4DED68` 固定返回 0,实际的命中信号完全通过输出指针的偏移量来传递。 控制流回到 sub_4E0834 后,

6 May 2026, 15:46 UTC≈1,210 views1 reactionsread 12 August 2026
Forwarded from @BlitzTrainer

EncryptBlitz加密项目预告 自研DEX、Native VMP及白盒密钥体系,解密难度对标Virbox、爱加密、360加固等头部企业,后续持续迭代优化。 项目开发周期近1个月,核心开发4-5人,协作支持团队共4-20人,累计代码量达100万行。新版本将重点优化兼容性、强化主动攻击防御能力以及新增自研DEX、Native VMP及白盒密钥体系,1-2周内上线网页端,主打极致高性价比实用加密,不做冗余虚标。

1

1 May 2026, 07:59 UTC≈1,470 viewsread 12 August 2026

EncryptBlitz AI —— Android ARM64 商业级加固平台 一次接入,保护四种目标 APK / ELF / SO动态库 / Shell脚本 免费试用 7天全功能测试版,到期自动失效,无需付费即可验证效果 付费模式 一键开启 Max(VM High、完整反调试、防Hook、防Dump、运行时自防御) 安全设计 - 本地引擎执行,不上传客户代码 - Web后端管理额度与任务,不内置联网卡密 - 输出文件自带合规提示与到期检测 👉 立即使用:https://jm.byxly.vip/

30 Apr 2026, 20:58 UTC≈1,160 viewsread 12 August 2026
Forwarded from @BlitzTrainerPhoto

EncryptBlitz AI 是一套面向商业交付的多目标加密保护平台,专注 APK、ELF、SO/JNI 与 Shell 四类核心目标的一站式加固。系统采用 CLI/Web-only 架构,网页端负责用户、额度、任务、上传下载与发布审计,服务端私有调用加固引擎完成保护流程。支持免费 7 天测试版与付费 Max / VM High / 深度 RASP 模式,覆盖 anti-debug、anti-hook、anti-dump、anti-tamper、完整性校验、运行时自保护、功能开关、报告输出与 release gate 验证,帮助开发者在发布前完成更可靠、更可解释的安全加固。 使用链接:https://jm.byxly.vip/

26 Apr 2026, 00:18 UTC≈1,250 views2 reactionsread 12 August 2026

C/C++ LLVM混淆加固 适配 Android NDK、PC Clang 双版本 全量成熟功能: 字符串加密、间接调用混淆、间接跳转混淆、基本块切割、Switch降级、控制流平坦化、VM扁平化控制流、MBA算术混淆、虚假控制流、函数包装、常参特化克隆、别名访问混淆、AMA延时偏移加载、PAO参数结构化、函数分片 纯C/C++专属,强效防逆向,支持商用授权 购买联系QQ:2987303932

2

Showing the 12 most recent of 21 posts we hold for @Lyuelian. 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 — 18,328 of 1,480,688entries 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.

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.

Mentions

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.

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

“蓝月亮通知频道” (@Lyuelian), 5,067 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Lyuelian.

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.