Telegram RegisterThe public register of Telegram
Telegram profile photo for 无极分享社–破解软件

Channel

无极分享社–破解软件

@ddddffxxr

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Domains linked from posts · Cite this entry

211,062subscribers

-14,074 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001608484349
TypeChannel
Username@ddddffxxr
Description商务广告联系 @ddddffxxr99 永久分享白嫖,实用与加速器,各种杂类软件,白嫖分享各种软件。黑料八封 地址发布页①https://wuji.usite.pro/ma.html 无极中文索引:https://t.me/sssss66666666666666 无极交流吧 https://t.me/+EzxrLqWniv81ZmFl 无极资源存放处 https://t.me/xoxovvv 巨魔至尊版频道 https://t.me/ddddffxxr03
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/ddddffxxr

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

210,075226,729218,4027 August 2026 — 225,136 subscribers7 August 2026 — 225,194 subscribers8 August 2026 — 225,248 subscribers9 August 2026 — 225,271 subscribers10 August 2026 — 225,294 subscribers12 August 2026 — 225,274 subscribers14 August 2026 — 225,317 subscribers15 August 2026 — 225,466 subscribers17 August 2026 — 225,506 subscribers18 August 2026 — 225,608 subscribers19 August 2026 — 225,819 subscribers20 August 2026 — 226,142 subscribers21 August 2026 — 226,434 subscribers23 August 2026 — 226,542 subscribers24 August 2026 — 226,583 subscribers25 August 2026 — 226,626 subscribers26 August 2026 — 226,658 subscribers27 August 2026 — 226,727 subscribers28 August 2026 — 226,729 subscribers29 August 2026 — 226,521 subscribers30 August 2026 — 226,161 subscribers1 September 2026 — 224,858 subscribers2 September 2026 — 224,290 subscribers3 September 2026 — 223,237 subscribers5 September 2026 — 221,113 subscribers8 September 2026 — 214,789 subscribers11 September 2026 — 213,169 subscribers13 September 2026 — 212,227 subscribers14 September 2026 — 211,854 subscribers16 September 2026 — 211,601 subscribers18 September 2026 — 211,244 subscribers1 October 2026 — 210,290 subscribers6 October 2026 — 210,138 subscribers10 October 2026 — 210,075 subscribers13 October 2026 — 210,117 subscribers15 October 2026 — 210,138 subscribers15 October 2026 — 210,170 subscribers16 October 2026 — 210,182 subscribers17 October 2026 — 210,210 subscribers19 October 2026 — 210,249 subscribers20 October 2026 — 210,282 subscribers21 October 2026 — 210,227 subscribers22 October 2026 — 210,210 subscribers23 October 2026 — 210,228 subscribers24 October 2026 — 210,229 subscribers25 October 2026 — 210,284 subscribers26 October 2026 — 210,318 subscribers27 October 2026 — 210,335 subscribers28 October 2026 — 210,406 subscribers29 October 2026 — 210,448 subscribers30 October 2026 — 210,509 subscribers31 October 2026 — 210,544 subscribers1 November 2026 — 210,621 subscribers2 November 2026 — 210,708 subscribers3 November 2026 — 210,767 subscribers4 November 2026 — 210,874 subscribers5 November 2026 — 211,009 subscribers6 November 2026 — 211,062 subscribers211,0627 August 20266 November 2026
58 measurements spanning 91 days, net -14,074. 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 207,577–229,227 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
6 Nov 2026, 06:49211,062+53
5 Nov 2026, 05:16211,009+135
4 Nov 2026, 04:31210,874+107
3 Nov 2026, 07:37210,767+59
2 Nov 2026, 07:47210,708+87
1 Nov 2026, 10:41210,621+77
31 Oct 2026, 12:56210,544+35
30 Oct 2026, 16:00210,509+61
29 Oct 2026, 13:29210,448+42
28 Oct 2026, 15:26210,406+71
27 Oct 2026, 15:48210,335+17
26 Oct 2026, 18:30210,318+34
25 Oct 2026, 15:18210,284+55
24 Oct 2026, 12:36210,229+1
23 Oct 2026, 09:27210,228+18
22 Oct 2026, 10:57210,210-17
21 Oct 2026, 07:06210,227-55
20 Oct 2026, 01:30210,282+33
19 Oct 2026, 02:37210,249+39
17 Oct 2026, 23:28210,210first reading

Engagement

1,613 posts held, back to 5 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 202 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.606%
avg views ÷ 211,062 subscribers
Avg views / post
1,280
567 posts measured
Reaction rate
0.622%
reactions ÷ views · ER floor
Posts in window
567
of 1,613 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. It is computed over the 546 of 567 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held1,613 (5 August 2026 – 6 November 2026)
Views total724,684
Reactions total4,508
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 19: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.

What this channel posts

Photos
15
Links
360

Lifetime counters from Telegram’s own channel header, read 6 November 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.

Reaction mix

6,683 reactions across 935 posts, in 21 distinct kinds. The most used accounts for 93.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6,26293.7%
❤2273.40%
🤡310.464%
💩270.404%
💔260.389%
😱200.299%
🤓170.254%
🔥120.18%
🤔100.15%
🤬100.15%
🖕80.12%
👏70.105%
🫡60.09%
💯40.06%
🤮40.06%
😁30.045%
🥰30.045%
😍20.03%
🙏20.03%
👨‍💻10.015%
1 further kind10.015%

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 938 of the 1,000 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 6,683 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 12 September 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 51 of 567 posts held from the last 30 days (8.99%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 13:29 UTC≈1,070 views16 reactionsread 6 November 2026
File

👩‍👩‍👧 点击 ➡️AI 短剧破解合集下载区 👩‍👩‍👧 🥰 点击 ➡️ 无极软件库 10.0🥰

👍15❤1

6 Nov 2026, 13:29 UTC≈1,030 views17 reactionsread 6 November 2026
File

解锁无限观看,懒得修改会员图标 👩‍👩‍👧➡️11月6日VPN破解合集更新👩‍👩‍👧 👩‍👩‍👧➡️ 临时网盘总资源同步更新合集 👩‍👩‍👧 👩‍👩‍👧➡️QQ 老司机 (VPN 功能) 浏览器专业版 👩‍👩‍👧 🥰 点击 ➡️ 无极软件库 10.0🥰 商务广告合作 @无极

👍15❤1🤔1

6 Nov 2026, 13:29 UTC657 views16 reactionsread 6 November 2026
File

🥰 点击 ➡️ 无极软件库 10.0🧕🥰

👍15❤1

6 Nov 2026, 13:29 UTC900 views16 reactionsread 6 November 2026
File

⚽️🥰 点击 ➡️ 无极软件库 10.0🧕🥰⚽️

👍15❤1

6 Nov 2026, 13:29 UTC939 views16 reactionsread 6 November 2026
File

⚽️🥰 点击 ➡️ 无极软件库 10.0🧕🥰⚽️

👍15❤1

6 Nov 2026, 13:29 UTC976 views16 reactionsread 6 November 2026
File

⚽️🥰 点击 ➡️ 无极软件库 10.0🧕🥰⚽️

👍15❤1

6 Nov 2026, 13:29 UTC980 views16 reactionsread 6 November 2026
File

🥰 点击 ➡️ 无极软件库 10.0🥰

👍15❤1

6 Nov 2026, 13:29 UTC≈1,020 views16 reactionsread 6 November 2026
File

⚽️🥰 点击 ➡️ 无极软件库 10.0🧕🥰⚽️

👍15❤1

6 Nov 2026, 13:29 UTC727 views16 reactionsread 6 November 2026
File

#无极破解 #老司机 #桃色 解锁无限观看,随便注册登录就是会员 使用说明: 先关闭 vpn 代理,再使用。 重要警告 ⚠️ 千万别跑去反映问题,被作者发现破解版,到时候和谐了就坑爹。切记! 官方版与破解版签名不一致,老人傻傻跑去反映无法更新,傻逼玩意! 👩‍👩‍👧➡️ 哪个傻逼玩意跑去反映情况 👩‍👩‍👧 🥰 点击 ➡️ 无极软件库 10.0🥰

👍15❤1

6 Nov 2026, 13:29 UTC847 views16 reactionsread 6 November 2026
File

解锁无限观看,懒得修改会员图标 🥰 点击 ➡️ 无极软件库 10.0🥰

👍15❤1

6 Nov 2026, 13:29 UTC947 views16 reactionsread 6 November 2026
File

👩‍👩‍👧 点击 ➡️AI 短剧破解合集下载区 👩‍👩‍👧 🥰 点击 ➡️ 无极软件库 10.0🥰

👍15❤1

6 Nov 2026, 13:29 UTC584 views14 reactionsread 6 November 2026
File

🥰 点击 ➡️ 无极软件库 10.0🧕🥰

👍13❤1

Showing the 12 most recent of 1,613 posts we hold for @ddddffxxr. 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.

Posts edited after publishing

@ddddffxxr edited 10 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
23 August 2026
Most recent edit
6 November 2026

Posts recorded as deleted after publishing

We recorded 13 posts on @ddddffxxr as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
22 August 2026
Most recent seen missing
30 October 2026
Median time before seen missing
24 hours
Seen missing in the last 30 days
6

Mentions

Named by 3 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.

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.

Domains linked from posts

8 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

yq7.lanzout.comregistrable domain: lanzout.com3 posts · 5 August 2026 – 5 August 2026 · example post
www.xsnwfbk.cnregistrable domain: xsnwfbk.cn2 posts · 5 August 2026 – 5 August 2026 · example post
hldqggg.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post
tpsld.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post
xvytsabc.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post
bbbasll.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post
yqpjyyay.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post
bjsisisj.fawsokt.cnregistrable domain: fawsokt.cn1 post · 5 August 2026 – 5 August 2026 · example post

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

“无极分享社–破解软件” (@ddddffxxr), 211,062 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/ddddffxxr.

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.