德国 荷兰 阿根廷 墨西哥 英国 尼日利亚 印度 阿曼 玻利维亚 混合 印度尼西亚 厄瓜多尔 古巴 巴西 香港 伊拉克 欧混 委内瑞拉 巴基斯坦 美国 孟加拉 塞内加尔 加纳 博茨瓦纳 布基纳法索 哥伦比亚 喀麦隆 加拿大 摩洛哥 刚果 土耳其 毛里搭尼亚 秘鲁 危地马拉 约旦 埃及 几内亚 马来 意大利 也门 WS协议老号,需要的滴滴

Channel
大马猴通知屋
@DMH666688
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
484subscribers
-10 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002509845689 |
|---|---|
| Type | Channel |
| Username | @DMH666688 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/DMH666688 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 21:06 | 484 | -5 |
| 26 Aug 2026, 07:11 | 489 | -5 |
| 18 Aug 2026, 15:02 | 494 | no change |
| 17 Aug 2026, 22:31 | 494 | first reading |
Engagement
20 posts held, back to 17 January 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.51%
- avg views ÷ 484 subscribers
- Avg views / post
- 17.0
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- 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 15 August 2026 |
|---|---|
| Posts held | 20 (17 January 2026 – 15 August 2026) |
| Views total | 17 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 22:31 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
166 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 41.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 68 | 41.0% | |
| 💩 | 51 | 30.7% | |
| 🖕 | 21 | 12.7% | |
| 🤣 | 10 | 6.02% | |
| 🌚 | 9 | 5.42% | |
| 🗿 | 3 | 1.81% | |
| 🤮 | 2 | 1.20% | |
| 🤡 | 1 | 0.602% | |
| 🤪 | 1 | 0.602% |
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 19 of the 20 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 166 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 January 2026 to 15 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
全球TG拉群 TG超链按钮私信 进粉猛的一批 全球可发 全球可打 支持盘口来联系 源头直发 直打 支持测试
💩1
墨西哥2个月老号,10W库存无限供 个人商业均有
🌚2👎2
WS美国,加拿大,混合,阿根廷,英国,印度直登老号,需要的联系
👎1🖕1
墨西哥 印度 美国 加拿大 英国 阿根廷 哥伦比亚 南美 欧州 非洲 全球混合个人 商业老号,几十W库存存 长年供货
👎2💩1
长期供应WS协议老号 阿联酋,美国,加拿大,墨西哥,秘鲁,阿根廷,土耳其,哥伦比亚,智利,印度,印尼,南美洲,非洲老号,全球可挑国家, 新号混合可定制跑日产10万
👎1💩1🤡1
出一批ws协议老号🥰🥰 巴基斯坦 沙特 秘鲁 印尼 印度 全球混合 哥伦比亚 阿联酋 委内瑞拉 美国 加拿大 墨西哥 非洲混合 巴西 尼日利亚 阿根廷 英国 欧洲混合 南美洲混合 土耳其 智利 德国☺️☺️☺️
🤮2
出全球各国老号 赞比亚,加纳,坦桑尼亚,英国,墨西哥,美国,加拿大,阿根廷,秘鲁,土耳其,尼日,德国,印尼,斯里兰卡,沙特,印度,南美洲混合 欧洲混合 非洲混合
💩5👎4🗿3🖕1🤣1🤪1
印度墨西哥美国WS老号,大量有货
👎5🌚4💩3🤣1
需要炒群 建群 接粉ws老号,认准大马猴 专业诚信第一
👎5🖕4💩3
祝大家新年快乐 马年大吉 马年行大运,发大财!
👎5💩4🖕4🤣1
需要炒群 建群 接粉ws老号,认准大马猴 专业诚信第一
👎5🖕4💩3🤣1
Showing the 12 most recent of 20 posts we hold for @DMH666688. 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.
Mentions
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“大马猴通知屋” (@DMH666688), 484 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/DMH666688.
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.