Telegram RegisterThe public register of Telegram
Telegram profile photo for 墨州LEUS主频道

Channel

墨州LEUS主频道

@MZNBLEUS

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

6,156subscribers

-122 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002262258855
TypeChannel
Username@MZNBLEUS
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/MZNBLEUS

Growth

6,1566,2786,2177 August 2026 — 6,278 subscribers7 August 2026 — 6,278 subscribers8 August 2026 — 6,275 subscribers11 August 2026 — 6,247 subscribers14 August 2026 — 6,222 subscribers17 August 2026 — 6,204 subscribers20 August 2026 — 6,190 subscribers24 August 2026 — 6,170 subscribers27 August 2026 — 6,156 subscribers7 August 202627 August 2026
9 measurements spanning 20 days, net -122. 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 6,138–6,296 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 07:096,156-14
24 Aug 2026, 13:166,170-20
20 Aug 2026, 23:556,190-14
17 Aug 2026, 18:436,204-18
14 Aug 2026, 19:566,222-25
11 Aug 2026, 03:526,247-28
8 Aug 2026, 00:536,275-3
7 Aug 2026, 17:316,278no change
7 Aug 2026, 17:246,278first reading

Engagement

16 posts held, back to 27 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 14 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
34s
Average length
17s

Measured directly from 2 videos 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.

Reaction mix

11 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 81.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
981.8%
💩218.2%

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

Measured over the 16 most recent posts we hold, published 27 December 2025 to 14 June 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

14 Jun 2026, 00:10 UTC369 views2 reactionsread 12 August 2026
Forwarded from @KTVNB6Video

无畏契约 🫥 神罚 ✔️由国内顶尖技术团队打造而成 ✔️独家旁路(过检测技术) ✔️流畅的ESP+简洁好看的ui ✔️独家功能:蓝光绘制 自瞄 范围 ✔️高端项目瓦手直装市场独一无二 ✔️持续跟进检测稳定性毋庸置疑 ✔️纯读写绘制(吊打垃圾直装) ✔️全网直装唯一解决高段位封号 💥核心更新✔️ 持续优化ACE上报检测 添加一下鸭始皇骨骼 Pass掉所有系统检测 持续优化 已上传网盘🚀🚀 检测你跑我追 开开心心上大分 无需ROOT不拉顶破天行为 稳如磐石 无惧检测 无视举报🧁 🔰卡密购买地址👌: https://918.oioix.cn/links/29BA5806 ✅最新版本下载链接: https://1857785172.share.123pan.cn/123pan/VbhSvd-HwDBH 问题反馈联系 @webz3880 官方代理频道 @KTVNB6 演戏不要杀太多人不然导致举报→然后观察期 一定不要覆盖安

💩2

Signed 墨州

2 Jun 2026, 23:41 UTC204 viewsread 12 August 2026
Forwarded from @GCZPD

❤️三角洲HERO英雄解密内核上架 无任何三方追封拉闸问题 🔼 全网最稳定市场项目😃 不动任何内存 不追封 独家解密 非市场同款 超详细准确的物资绘制 专注于稳定性 拒绝拉闸 无需多言 懂行的自己清楚 🔰官方下单卡网↓ https://918.oioix.cn/links/29BA5806 卡密解绑链接: https://t3yanzheng.com/unbound.php?303C8A79903CDAD0 购买后会有下载链接和使用教程 批卡/售后 @webz3880 官方频道: https://t.me/GCZPD

Signed 墨州

28 May 2026, 12:08 UTC325 views0 reactionsread 12 August 2026
Forwarded from @GCZPD

❤️三角洲HERO英雄解密内核上架 无任何三方追封拉闸问题 🔼 全网最稳定市场项目😃 内核级陀螺仪自瞄 无视30天 10年 算法解密 非内存 拦截 断点 超详细准确的物资绘制 无需多言 懂行的自己清楚 🔰官方下单卡网↓ https://918.oioix.cn/links/29BA5806 卡密解绑链接: https://t3yanzheng.com/unbound.php?303C8A79903CDAD0 购买后会有下载链接和使用教程 批卡/售后 @webz3880 官方频道: https://t.me/GCZPD

Signed 墨州

2 Mar 2026, 00:55 UTC≈1,430 views1 reactionsread 12 August 2026
Forwarded from @JLQGFVideo

GC内核模块 👁 全能透视系统 • 方框 · 骨骼 · 射线 · 血条 · 名字 📊 智能信息面板 • 距离 · 人机 · 头甲 · 手持 · 盒子 【技术优势】 💎 纯解密不动内存 · 稳定MAX 不闪不延迟不遁地 💎 绘制不闪框 · 流畅无卡顿 💎 面具一键刷入 · 小白易用 💎 支持5/6系内核 Root ✔️可以联系专门售后一对一辅导 【使用说明】 1. 下载面具模块 2. 刷入面具模块 3. 执行面具模块 🔥 专业内核,品质保证! 最新网盘附带视频教学 https://www.123912.com/s/mPMjVv-6sp0v 官方提卡链接 https://918.oioix.cn/links/29BA5806

1

Signed 墨州

21 Jan 2026, 18:03 UTC≈1,610 views0 reactionsread 12 August 2026

也是有编写驱动的实力的吧

Signed 墨州

21 Jan 2026, 18:03 UTC≈1,580 views0 reactionsread 12 August 2026

盲猜一波,你和平的那个开发

Signed 墨州

17 Jan 2026, 09:58 UTC≈1,550 views3 reactionsread 12 August 2026
Forwarded from @MZGFZPD

😙大家进一下新频道 过几天就完全回归了 每个项目每天都送天卡 https://t.me/MZHZPD

3

Signed 墨州

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

Forward network

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

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

“墨州LEUS主频道” (@MZNBLEUS), 6,156 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/MZNBLEUS.

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.