😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍3❤1

Channel
@ChinaWOLFxnw
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13,327subscribers
-48 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002132904535 |
|---|---|
| Type | Channel |
| Username | @ChinaWOLFxnw |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/ChinaWOLFxnw |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 17:34 | 13,327 | -12 |
| 16 Aug 2026, 14:38 | 13,339 | -1 |
| 14 Aug 2026, 19:54 | 13,340 | -5 |
| 13 Aug 2026, 13:05 | 13,345 | +2 |
| 12 Aug 2026, 10:17 | 13,343 | -10 |
| 11 Aug 2026, 06:48 | 13,353 | -2 |
| 10 Aug 2026, 05:58 | 13,355 | -18 |
| 9 Aug 2026, 05:03 | 13,373 | -9 |
| 8 Aug 2026, 08:30 | 13,382 | +7 |
| 7 Aug 2026, 11:45 | 13,375 | no change |
| 7 Aug 2026, 09:18 | 13,375 | first reading |
38 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 22 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.
| Window | Rolling 30 days · latest post in window 16 August 2026 |
|---|---|
| Posts held | 38 (5 August 2026 – 16 August 2026) |
| Views total | 26,366 |
| Reactions total | 175 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 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.
Lifetime counters from Telegram’s own channel header, read 17 August 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.
Measured directly from 3 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.
175 reactions across 38 posts, in 3 distinct kinds. The most used accounts for 64.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 112 | 64.0% | |
| ❤ | 61 | 34.9% | |
| 🥰 | 2 | 1.14% |
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 38 of the 38 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 175reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 5 August 2026 to 16 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.
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍3❤1
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍3
铭记8·15日本投降:勿忘历史,吾辈自强 1945年8月15日,日本天皇发布《终战诏书》,宣布无条件投降。消息传遍华夏大地,饱受战火蹂躏的亿万国人终于迎来盼望已久的胜利。 山河破碎,烽火连天,十四年艰苦抗战。无数将士奔赴前线浴血杀敌,无数普通百姓在苦难之中坚守抗争。三千五百万同胞的鲜血与苦难,铸就了来之不易的和平。这不是轻易得来的和解,是先辈以血肉之躯,击退侵略,守住家国。 8月15日,是投降宣告日;而9月3日,是我国法定的中国人民抗日战争胜利纪念日,那是正式签署投降书之后,刻入民族记忆的胜利之日。 岁月流转,硝烟早已散尽,但历史不容遗忘。我们铭记这段历史,不是为了延续仇恨,而是记住曾经的苦难,记住先烈的牺牲。知来路,方知归途;以史为鉴,方能珍惜当下的山河安宁。 吾辈当自强,怀敬畏之心,记历史之痛,护盛世中华。
👍25❤2🥰2
Video, posted without a caption
👍5
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍3❤1
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍6
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍5❤1
狼头每日安全状态😮安全😭风险 🔥全球(✅安全)🎮日韩(✅安全) 🎮越南(✅安全)🎮台湾(✅安全) 👑(解密状态:✅正常) (✅以云更新更新解密) (😙如果你是之前用过别的辅助(不限美化包改文件等等)或者第一次使用榔头请使用一下狼头清理否则后果自负) ➡️注意演戏百分百安全,像一个正常人,不要像一个疯狗 ❗️不要要自己觉得没问题,要让敌人觉得没问题
👍1
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
❤2👍1
狼头每日安全状态😮安全😭风险 🔥全球(✅安全)🎮日韩(✅安全) 🎮越南(✅安全)🎮台湾(✅安全) 👑(解密状态:✅正常) (✅以云更新更新解密) (😙如果你是之前用过别的辅助(不限美化包改文件等等)或者第一次使用榔头请使用一下狼头清理否则后果自负) ➡️注意演戏百分百安全,像一个正常人,不要像一个疯狗 ❗️不要要自己觉得没问题,要让敌人觉得没问题
👍5❤2
😄WOLF kernel/狼头内核😄 😍独家自研源码/仿生独家概率追😍 ❤️注入内核掩体判断/独家思路解密❤️ 点我跳转WOLF狼头官方卡网
👍4
已经加卡
👍3
Showing the 12 most recent of 38 posts we hold for @ChinaWOLFxnw. 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 — 196,029 of 1,548,671entries 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.
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.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“狼头内核官方频道” (@ChinaWOLFxnw), 13,327 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/ChinaWOLFxnw.
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.