今天直播打了40把地铁测试内透➕自瞄 没有任何情况 还是一句话演戏=稳定
👍34🤣10🤔4
Signed 帝 天

Channel
@MDMHZS
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
47,560subscribers
+2,354 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002757208760 |
|---|---|
| Type | Channel |
| Username | @MDMHZS |
| Description | 明帝项目下载官网: 明帝.cn 明帝端口官方①频道: @MDMHZS 明帝端口官方②频道: @mdtgck 明帝端口反馈频道: @MDMHFK |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/MDMHZS |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 29% 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 |
|---|---|---|
| 18 Sept 2026, 02:56 | 47,560 | -23 |
| 15 Sept 2026, 22:19 | 47,583 | -17 |
| 14 Sept 2026, 04:59 | 47,600 | +67 |
| 12 Sept 2026, 16:01 | 47,533 | +73 |
| 10 Sept 2026, 12:19 | 47,460 | -96 |
| 7 Sept 2026, 09:59 | 47,556 | +148 |
| 4 Sept 2026, 17:42 | 47,408 | -54 |
| 3 Sept 2026, 00:07 | 47,462 | +2 |
| 1 Sept 2026, 22:24 | 47,460 | -26 |
| 1 Sept 2026, 01:38 | 47,486 | +23 |
| 31 Aug 2026, 00:34 | 47,463 | +122 |
| 30 Aug 2026, 03:46 | 47,341 | +22 |
| 29 Aug 2026, 01:53 | 47,319 | +48 |
| 28 Aug 2026, 04:24 | 47,271 | +64 |
| 27 Aug 2026, 03:44 | 47,207 | +101 |
| 26 Aug 2026, 00:35 | 47,106 | +82 |
| 25 Aug 2026, 03:56 | 47,024 | +116 |
| 23 Aug 2026, 21:44 | 46,908 | +199 |
| 22 Aug 2026, 06:06 | 46,709 | +174 |
| 20 Aug 2026, 21:28 | 46,535 | first reading |
62 posts held, back to 23 May 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 87 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 22 September 2026 |
|---|---|
| Posts held | 62 (23 May 2026 – 22 September 2026) |
| Views total | 165,239 |
| Reactions total | 1,703 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 17:12 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 24 September 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.
Measured directly from 1 video 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.
3,856 reactions across 58 posts, in 30 distinct kinds. The most used accounts for 74.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,868 | 74.4% | |
| ❤ | 450 | 11.7% | |
| 😱 | 96 | 2.49% | |
| 🖕 | 75 | 1.95% | |
| 🤣 | 40 | 1.04% | |
| 🤮 | 40 | 1.04% | |
| 😍 | 38 | 0.985% | |
| 🤓 | 36 | 0.934% | |
| 🤡 | 30 | 0.778% | |
| 👎 | 28 | 0.726% | |
| 🕊 | 17 | 0.441% | |
| 😎 | 17 | 0.441% | |
| 😁 | 15 | 0.389% | |
| 🥰 | 15 | 0.389% | |
| 🤔 | 13 | 0.337% | |
| 🍌 | 11 | 0.285% | |
| 🤩 | 11 | 0.285% | |
| 🔥 | 10 | 0.259% | |
| 🤬 | 9 | 0.233% | |
| 🤯 | 6 | 0.156% | |
| 10 further kinds | 31 | 0.804% |
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 58 of the 62 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,856 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 62 most recent posts we hold, published 23 May 2026 to 22 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.
今天直播打了40把地铁测试内透➕自瞄 没有任何情况 还是一句话演戏=稳定
👍34🤣10🤔4
Signed 帝 天
目前是没有问题的 部分人客户端 请你们认真观看上面的消息 美化现在有部分人无论是配置端口还是配置原版 游戏结束就客户端30分钟 这种是强标 封太多次了 这种没有办法 有的人没有开美化正常玩都会这样30分钟
👍21🤮5😱3❤2
Signed 帝 天
目前明帝公益端口 基本上做到了 不需要原版 也不会客户端了 部分人客户端的原因: 1.突然断开网络 或者突然网络卡了 导致游戏心跳断开了导致封号 因为数据发送突然中断 2.就是先导入文件 提前打开了和平精英 后面在链接的端口 这种也是会封的 因为没有用端口数据上号 没有处理到大厅客户端数据 进游戏就会封客户端问题 或者游戏打一半就客户端的原因 3.部分人十年 基本上是玩大范围演都不演打绿洲导致或者其他地图 现在绿洲也是有检测的 很多人一直以为没有 只是检测没有那么快 后续会追封的
👍40❤9🤮4🤔3😱1
Signed 帝 天
还有一个假明帝私端 大家一定要认准明帝官方频道买 说的是破解明帝私端 其实是什么 他做了一个一模一样的APP 验证跟我搞的一样 很多人以为是明帝私端 其实就是空壳 就搞了一个映射html 卡密都是通过云数据 根本破解不了 不是本地卡密验证
👍34😱8
Signed 帝 天
目前网络上很多人说 明帝端口规则开源 基本上是没有任何用的 很多小白以为把规则开了就是真的牛逼 数据处理修改都在服务器里面靠的封包修改 规则都是差不多的规则 搭建端口必须用的一条基础规则 端口不是拦截那种靠的是规则阻止所有域名链接IP 端口是通过数据修改数据包头
👍32😱3
Signed 帝 天
设备黑一般封:开游戏就数据重新登录就要人脸 或者打一个人就隔离或者人脸 或者刚刚开游戏就数据重新登录显示隔离期一天 这种大部分是设备黑 还有一个就是范围目前不好说 我也不敢保证百分百稳定 因为和平针对范围➕这个加速特别严重 范围建议文件玩0.45 其他大于0.45的封十年几率很高 还是一句话 端口只是止痛药
👍39❤2🤮2
Signed 帝 天
看了反馈 很多人说人脸端口问题 我也是醉了 不知道怎么说你们😂
👍23❤6
Signed 帝 天
没人反馈 那就关闭公益端口?😢
👍158😱52🖕26🤮10🙉5❤2🍌2🕊1
Signed 帝 天
任何问题带截图反馈即可 你就说封了 你就说不稳 我也不知道你到底玩的什么 我也不知道怎么解决 说要说清楚 @MDKFZX
👍48❤8🕊3🤡1
Signed 帝 天
目前新赛季 不会换检测 过几天看看会不会换检测值 任何问题反馈就好了 兄弟们 不忘初心 一直公益
👍46❤5🕊2🤡1
Signed 帝 天
解决网络异常 严重问题 解决了部分人客户端问题 各位记得反馈 公益才有动力 稳定一个人也没有反馈 不稳定一个个反馈 不用切换离线 免白一直玩就行
👍25❤5
Signed 帝 天
你们自己认真投票 我看看数据 在决定调整 可以吧
👍69🖕14👎4
Signed 帝 天
Showing the 12 most recent of 62 posts we hold for @MDMHZS. 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.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
有时候网络异常10分钟但是不会客户端 另外一种就是不会网络异常 但是有可能会客户端需要原版
Shares as published. No per-option vote count is published by Telegram, so none is shown.
玩明帝端口你一般配置什么项目
Shares as published. No per-option vote count is published by Telegram, so none is shown.
准备想开发另外一个端口 投票决定吧
Shares as published. No per-option vote count is published by Telegram, so none is shown.
前几天端口稳一点 还是今天稳一点
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 62 most recent posts we hold, published 23 May 2026 to 22 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“明帝端口官方频道” (@MDMHZS), 47,560 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/MDMHZS.
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.