投稿破解请联系 @luyikui ,投稿请发送辅助包与辅助频道并备注游戏名称。
Signed Lunor.

Channel
@rg99999
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
22,549subscribers
+9,956 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002300864329 |
|---|---|
| Type | Channel |
| Usernames | @pomozhizhuang @rg99999 |
| Description | 公益内核破解频道 交流群组 https://t.me/rg666666666 投稿破解 @luyikui 禁止搬运,二改,倒卖,此频道破解的所有辅助 免责声明 本频道中的所有内容均来源于网络,仅供个人学习和研究使用,请在24小时之内删除,请勿用于任何商业用途或非法用途。如果您喜欢该资源,请支持正版,购买正版资源。如有任何内容侵犯了您的权益,请及时联系我们,我们将立即予以删除. |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 126 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/rg99999 |
Software piracy — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 10:20 | 22,549 | +63 |
| 10 Nov 2026, 19:28 | 22,486 | +15 |
| 10 Nov 2026, 09:15 | 22,471 | +39 |
| 9 Nov 2026, 08:17 | 22,432 | +12 |
| 8 Nov 2026, 22:56 | 22,420 | +37 |
| 7 Nov 2026, 20:39 | 22,383 | +55 |
| 7 Nov 2026, 13:21 | 22,328 | +7 |
| 6 Nov 2026, 16:08 | 22,321 | +1 |
| 6 Nov 2026, 10:51 | 22,320 | +30 |
| 5 Nov 2026, 19:28 | 22,290 | +13 |
| 5 Nov 2026, 11:17 | 22,277 | +34 |
| 4 Nov 2026, 15:57 | 22,243 | +23 |
| 4 Nov 2026, 08:07 | 22,220 | +11 |
| 3 Nov 2026, 13:00 | 22,209 | -23 |
| 3 Nov 2026, 04:37 | 22,232 | -18 |
| 2 Nov 2026, 12:07 | 22,250 | +1 |
| 2 Nov 2026, 05:58 | 22,249 | -21 |
| 1 Nov 2026, 13:16 | 22,270 | +12 |
| 1 Nov 2026, 07:40 | 22,258 | +42 |
| 31 Oct 2026, 10:05 | 22,216 | first reading |
357 posts held, back to 1 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 79 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 12 November 2026 |
|---|---|
| Posts held | 357 (1 August 2026 – 12 November 2026) |
| Views total | 70,093 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 16:25 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 12 November 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.
Measured directly from 2 videos 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.
1,315 reactions across 276 posts, in 5 distinct kinds. The most used accounts for 93.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,231 | 93.6% | |
| ❤ | 71 | 5.40% | |
| 🔥 | 10 | 0.76% | |
| 🥰 | 2 | 0.152% | |
| 🍌 | 1 | 0.076% |
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 277 of the 357 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,315 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 357 most recent posts we hold, published 1 August 2026 to 12 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.
Telegram’s own ‘edited’ marker: 1 of 47 posts held from the last 30 days (2.13%) 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).
投稿破解请联系 @luyikui ,投稿请发送辅助包与辅助频道并备注游戏名称。
Signed Lunor.
Photo, posted without a caption
Signed Lunor.
【鹿安破解】.三角洲.知音尊享版_1.0.0.apk 去除卡密验证 随便输入 #三角洲 #内核
Signed Lunor.
Photo, posted without a caption
Signed Lunor.
【鹿安破解】.三角洲.APEX内核.zip 去除卡密验证 直接进入 解密不卡顿 #三角洲 #内核
Signed Lunor.
Photo, posted without a caption
Signed Lunor.
【鹿安破解】.三角洲.XF市场版-1.35.zip 去除卡密验证 直接进入悬浮窗 #三角洲 #内核
Signed Lunor.
谁去把三角洲anc拿个包给我 @luyikui
Signed Lunor.
投稿破解请联系 @luyikui ,投稿请发送辅助包与辅助频道并备注游戏名称。
Signed Lunor.
Photo, posted without a caption
Signed Lunor.
【鹿安破解】.三角洲.XF市场版-追踪 自瞄版本1.33.zip 最新追索版本破解 #三角洲 #内核
Signed Lunor.
出售一份三角洲单解密 288稳定不和谐 @luyikui
Signed Lunor.
Showing the 12 most recent of 357 posts we hold for @rg99999. 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.
We recorded 14 posts on @rg99999 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“鹿安内核辅助破解(和平王者CFM暗区使命无畏三角洲PUBG内核)” (@rg99999), 22,549 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/rg99999.
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.