🥰推荐一个不错的软件频道 ❤️https://t.me/qgzyw8
❤10🥰10💯6🔥5🎉3

Channel
@dcmpj
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
39,403subscribers
+1,715 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001826860805 |
|---|---|
| Type | Channel |
| Username | @dcmpj |
| Description | 🔞安卓破解/精品绿色/精品老司机/原创破解 ❤️原创分享/精品免费/免费独家/资源放送 广告/投稿/反馈: @qgcyw8_bot |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/dcmpj |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 15:15 | 39,403 | +174 |
| 21 Aug 2026, 06:56 | 39,229 | +101 |
| 20 Aug 2026, 10:29 | 39,128 | +84 |
| 19 Aug 2026, 08:36 | 39,044 | +77 |
| 18 Aug 2026, 09:23 | 38,967 | +84 |
| 17 Aug 2026, 12:07 | 38,883 | +171 |
| 16 Aug 2026, 02:27 | 38,712 | +116 |
| 14 Aug 2026, 15:35 | 38,596 | +156 |
| 13 Aug 2026, 08:27 | 38,440 | +84 |
| 12 Aug 2026, 10:06 | 38,356 | +100 |
| 11 Aug 2026, 09:23 | 38,256 | +67 |
| 10 Aug 2026, 12:58 | 38,189 | +109 |
| 9 Aug 2026, 14:15 | 38,080 | +109 |
| 8 Aug 2026, 15:45 | 37,971 | +107 |
| 7 Aug 2026, 15:31 | 37,864 | +89 |
| 6 Aug 2026, 17:01 | 37,775 | +87 |
| 6 Aug 2026, 02:00 | 37,688 | no change |
| 6 Aug 2026, 01:53 | 37,688 | first reading |
92 posts held, back to 4 August 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 50 pagesof 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. It is computed over the 83 of 92 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 92 (4 August 2026 – 22 August 2026) |
| Views total | 113,863 |
| Reactions total | 1,196 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 20:29 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 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
1,101 reactions across 76 posts, in 11 distinct kinds. The most used accounts for 13.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 146 | 13.3% | |
| ❤🔥 | 134 | 12.2% | |
| 👍 | 131 | 11.9% | |
| 💯 | 131 | 11.9% | |
| 🎉 | 122 | 11.1% | |
| 🔥 | 119 | 10.8% | |
| 🥰 | 112 | 10.2% | |
| 🤩 | 103 | 9.36% | |
| 😍 | 101 | 9.17% | |
| 🍌 | 1 | 0.091% | |
| 💩 | 1 | 0.091% |
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 83 of the 92 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 1,196reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 92 most recent posts we hold, published 4 August 2026 to 22 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.
🥰推荐一个不错的软件频道 ❤️https://t.me/qgzyw8
❤10🥰10💯6🔥5🎉3
🔰各种破解资源应用尽有
❤4❤🔥4💯3👍1🤩1
🍄软件名称:震动按摩器_1.0.4 🔰功能介绍: 一款手机随身放松App!震动按摩器,一键调用手机马达,十多种震动节奏自由切换,多档力度随心调节,缓解肩颈疲劳、放松肌肉压力,小巧便携,随时随地舒缓身心! #工具 #震动按摩器
💯6❤5🎉4🔥3😍2
🍄软件名称:众人迷_1.01 🔰功能介绍: 一款手时尚穿搭欣赏App!众迷,汇集海量潮流穿搭视频,多种风格分类浏览,支持收藏保存,发现穿搭学灵感,闲暇浏览放松的趣味工具! #工具 #众人迷
🥰9💯7👍6🔥6🎉2
🍄软件名称:红薯自取_1.0 🔰功能介绍: 一款手平台清理工具App!小红书自动取关,支持批量清理关注列表,筛选无效账号一键取关,解放双手省去手动作,高效整理账号关注,自媒体账号打理实用工具! #工具 #红薯自取
❤5👍4🥰4❤🔥2🤩2
#开车 #tiktok🔞
🥰5👍4😍4❤🔥3🔥3
#频道推荐 #互推 ● 白嫖分享社 ● 重生之我在 TG做内置代理 ● 独特吧-破解软件游戏资源分享 ● 某不知名藏馆 网红 Cosplay 二次元 写真 ● 大聪明 破解软件分享频道 ● 零度资源分享-破解软件/游戏分享 ● 安卓软件游戏破解资源分享 参加互推: @pindaohutui123bot
👍2
🍄软件名称:牛牛视频_1.5.6 🔰功能介绍: 一款手机影视App!牛牛影视!汇集电影、剧集、综艺、动漫海量资源,实时更新热播内容,支持超清播放、离线缓存、大屏投屏,多条播放线路切换,追剧观影神器! #影视 #牛牛视频
❤1👍1🥰1
🍄软件名称:笔趣阁_5.0.0 🔰功能介绍: 一款手机阅读App!笔趣阁漫画小说二合一!汇集海量网文与高清漫画,小说、漫画一站式阅读,题材丰富持续更新,支持听书、离线缓存、自定义阅读设置,追书追漫两不误! #小说 #笔趣阁
❤1
🍄软件名称:AI极速翻译_1.0.4 🔰功能介绍: 一款手机AI翻译App!AI极速翻译,支持文本、语音、拍照多模式翻译,覆盖多国语言,翻译响应迅速,识别准确度高,日常出行、学习办公实用翻译工具! #工具 #AI极速翻译
#开车 #tiktok🔞
🍄软件名称:酷漫星_4.4.01 🔰功能介绍: 一款手机漫画App!酷漫星!海量高清漫画资源,国漫日漫韩漫多题材全覆盖,每日同步更新,支持离线缓存、书架管理、多种阅读模式,漫迷追漫阅读必备! #动漫 #酷漫星
❤2👍1
Showing the 12 most recent of 92 posts we hold for @dcmpj. 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 — 191,087 of 1,584,142entries 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.
Named by 22 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.
Named by
Channels on the register whose posts name this channel's handle.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“大聪明 破解软件分享频道” (@dcmpj), 39,403 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/dcmpj.
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.