来自速搜推荐 @SSOU 📢寸止-媚黑 📢捡尸,醉酒,KTV 📢bgc修车 bgc上门 ... 📢皇冠平台 皇冠真人 利博... 📢皇冠足球 皇冠体育 欧博... 📢飞投 TG最强博彩平台-... 📢抖音快手直播裸舞-头条-... 📢网贷数据|助贷数据|群呼... 📢今日亚洲|亚洲新闻大事件 📢欧博百家乐 亚星百家乐 ... 📢捡尸,醉酒,KTV 📢百家乐/真人电子/新盛博... 📢大富翁 -银河国际 -超... 📢一对一 爱心聊交友 📢反差女友福利社 👉流量互推规则介绍💥 以下是广告推荐 📢💹567U时代火爆上线!招收玩家/代理,匿名开户,放心娱乐! 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢⚽️注册送138🧧百家乐/棋牌/电竞体育信誉平台 🇨🇳 简体中文包 —————————-- 🔥将 @T…

Channel
经典动漫|热门动漫|动漫影视
@dongmanzhuliu
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
74subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002026417340 |
|---|---|
| Type | Channel |
| Username | @dongmanzhuliu |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/dongmanzhuliu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 11:28 | 74 | -1 |
| 9 Aug 2026, 21:15 | 75 | no change |
| 6 Aug 2026, 20:04 | 75 | first reading |
Engagement
20 posts held, back to 6 April 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 16.2%
- avg views ÷ 74 subscribers
- Avg views / post
- 12.0
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 20 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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (6 April 2026 – 9 August 2026) |
| Views total | 48 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 21:15 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.
Recent posts
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
Showing the 12 most recent of 20 posts we hold for @dongmanzhuliu. 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 — 646,721 of 1,481,217entries 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.
Mentions
Named by 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@agao5588 · 101 post百度
@baiduyixia00 · 91 post🏅速搜官方🏅|🔥福利吃瓜1️⃣3️⃣群🔥
@chiguagroups · 1541 posttelsa 塔尔萨
@collection_beautie · 241 post欧博私网 亚星私网 欧博包杀 亚星包杀
@fanyibaoanzhuang · 2111 post鸿腾集团-百家乐-棋牌-彩票-博彩-外汇-usdt
@hand896 · 61 post足球,世俱杯体育赛事
@hc8858_hc8858 · 91 post芊芊
@hopping_hope · 111 post皇冠平台 皇冠真人 利博平台 利博真人
@huangguanla · 51 post色情及性爱故事网站
@llbaeb · 4261 postTDS走向数据科学
@nvxingai · 601 postPA代理 PA官网 PA百家乐 PA私网
@ouboff · 71 post万利代理 万利官网 万利百家乐 万利私网
@oubogfa · 41 post水瑶
@shuiyao1 · 141 post2026世界杯足球-欧洲杯
@tvtv520_TVTV520 · 91 post新盛赌场-伯爵娱乐-棋牌游戏-环球娱乐-奥博体育-非凡国际
@wanbiaoge2 · 51 post万利平台 PA平台 万利真人 PA真人
@wanlipingtai · 81 post五件小事
@wujianxiaoshi · 161 post新盛娱乐|线上赌博|网赌平台|缅甸赌场
@xsddggr4 · 101 post欧博百家乐 亚星百家乐 线上百家乐 利博百家乐
@yaxing11w · 31 postUG环球平台 UG环球真人 环球平台 环球真人
@yaxing5c · 51 post百家乐代理 欧博百家乐 亚星百家乐 利博百家乐
@yaxingddo · 51 postUSDT兑换-换U-回U-洗白-娱乐赌场
@yzh1133_1 · 91 post皇冠招商 欧博招商 亚星招商 利博招商
@zhongwenbaoma · 51 post
Names
Channels on the register whose handles appear in this channel's posts.
@TeleTopOrg · 33,08819 posts速搜
@ssou · 209,3172 posts速搜❤️🔥流量互推/广告交易
@TonAdNews · 8,6202 posts一对一 爱心聊交友
@a78p71 · 281 postbgc修车 bgc上门 bgc外围
@bgcyuenanshangmen · 1121 post抖音快手直播裸舞-头条-抖音-抖音网红-反差婊福利-抖音美女
@bnryd75u64y · 361 post速搜官方频道-TON中文索引🇨🇳
@cn123 · 8,9481 post世俱杯--世界球会冠军杯--欧洲杯
@ji_jisou · 111 post大富翁 -银河国际 -超凡贵宾会 -新盛赌场-博彩
@KTV338_8 · 91 post☁️开云体育官方🏆开云招商 匡
@kyzsklz · 48,0761 post依依不舍
@lianlianbs · 191 postMaxPanel - 社媒增粉平台🚀
@MaxpanelCC · 17,6281 post腾龙赌场|菲律宾马尼拉赌场
@Miller33ss · 111 post球速体育 赌王之王-PG电子/麻将胡了/AG捕鱼
@pg56984 · 16,4171 postZOL中关村在线
@qiuydj · 621 postPG电子-加拿大-真人棋牌
@Sifangsisi · 61 post捡尸,醉酒,KTV
@songchigannixihuanmawoyexihuan85 · 91 post天上人间
@tianshangrenj1 · 481 post2026世界杯足球-欧洲杯
@tvtv520_TVTV520 · 91 post小玛莉休闲博彩赌场游戏
@waiwei11999 · 91 post科学网
@ximencuix · 371 post飞投 TG最强博彩平台-足彩 体育
@yfqh16855888 · 151 post皇冠足球 皇冠体育 欧博代理 亚星代理
@youguanqunfa12 · 4031 post东南亚大事件 金三角大事件 缅甸大事件
@yuenanU · 240,2431 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@dongmanzhuliu named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“经典动漫|热门动漫|动漫影视” (@dongmanzhuliu), 74 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dongmanzhuliu.
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.