在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1002366586765_7666741257_b0c8347f
👍12

Channel
@pj7645
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
46,991subscribers
+8,635 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002366586765 |
|---|---|
| Type | Channel |
| Username | @pj7645 |
| Description | 工艺内核破解频道 我不是资源的创造者,我只是勤劳的小蜜蜂 本频道中的所有内容均来源于网络,仅供个人学习和研究使用,请在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 | 6 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/pj7645 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 13:40 | 46,991 | +521 |
| 4 Sept 2026, 07:37 | 46,470 | +230 |
| 2 Sept 2026, 20:43 | 46,240 | +255 |
| 1 Sept 2026, 17:26 | 45,985 | +318 |
| 31 Aug 2026, 14:26 | 45,667 | +216 |
| 30 Aug 2026, 14:26 | 45,451 | +205 |
| 29 Aug 2026, 16:25 | 45,246 | +352 |
| 28 Aug 2026, 16:03 | 44,894 | +100 |
| 27 Aug 2026, 17:29 | 44,794 | +118 |
| 26 Aug 2026, 19:14 | 44,676 | +113 |
| 25 Aug 2026, 18:28 | 44,563 | +72 |
| 24 Aug 2026, 19:39 | 44,491 | +262 |
| 23 Aug 2026, 03:24 | 44,229 | +347 |
| 21 Aug 2026, 14:06 | 43,882 | +347 |
| 20 Aug 2026, 15:36 | 43,535 | +160 |
| 19 Aug 2026, 18:44 | 43,375 | +241 |
| 18 Aug 2026, 20:28 | 43,134 | +196 |
| 17 Aug 2026, 19:34 | 42,938 | +565 |
| 16 Aug 2026, 20:55 | 42,373 | +812 |
| 15 Aug 2026, 11:36 | 41,561 | first reading |
275 posts held, back to 4 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 85 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 6 September 2026 |
|---|---|
| Posts held | 275 (4 August 2026 – 6 September 2026) |
| Views total | 187,460 |
| Reactions total | 2,810 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Sept 2026, 14:15 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 6 September 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 24 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.
2,890 reactions across 275 posts, in 7 distinct kinds. The most used accounts for 88.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,566 | 88.8% | |
| ❤ | 240 | 8.30% | |
| 🔥 | 62 | 2.15% | |
| 🥰 | 16 | 0.554% | |
| 🎉 | 3 | 0.104% | |
| 👏 | 2 | 0.069% | |
| 🤩 | 1 | 0.035% |
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 275 of the 275 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 2,890 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 275 most recent posts we hold, published 4 August 2026 to 6 September 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 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1002366586765_7666741257_b0c8347f
👍12
#频道互推 #相似推荐 ------------------------------ 📢 公益辅助直装资源分享 📢 王者荣耀-和平精英-直装 📢 🥩ABC货源外挂提卡网三角洲端游直装和平王者 📢 落雾改文件官方频道和平精英&PUBG 📢 YY改文件官方主频道 📢 落幕和平文件资源分享🇨🇳 📢 ✨游戏辅助公益分享✨ 📢 全资源最全公益辅助破解软件分享 📢 雾鱼官方频道🇨🇳 📢 白雪和平&PUBG公益改文件/直装破解项目分享 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
👍8
无畏契约HE断点范围破解 先开辅助 在上游戏 🔗点我下载🔗 #无畏契约 #内核
👍10
和平精英起源最新版破解9.6 亲测有效 必须看包里视频教程 安装起源破解器app使用 🔗点我下载🔗 #和平精英 #内核
👍12❤1
三角洲HTY强锁自瞄pak 包里面有使用教程视频 支持最新版本 🔗点我下载🔗 #三角洲 #改文件
👍15
王牌战争国际服lvd功能文件9.5 人物绿名 隔墙自瞄 吸附自瞄 强制建造 解封设备 无视坦克 无视飞机 无视怪物 无视炮台 锁定天气 全图除草 无限氧气 🔗点我下载🔗 #王牌战争 #改文件
👍14
香肠派对XFileTool注入直装 特效 美化 自瞄 打击特效 解锁高级版 🔗点我下载🔗 #香肠派对
👍9
王者荣耀天问HOOK防掉框 配合无解密的使用 卡密乱输 🔗点我下载🔗 #王者荣耀
👍13❤1
三角洲虎牙内透9.6 自瞄 内透 颜色调节 漏人的时候打开设置,把那个隔墙关一下,再打开就行 🔗点我下载🔗 #三角洲 #内透
👍15
PC三角洲端游画质大杂烩9.6 除烟 除草 高亮 ps:群友闲鱼买的投稿 🔗点我下载🔗 #三角洲 #端游
👍13❤1
和平精英汉堡Kernel_LNA_追锁版1.0.9破解 解密 追踪 自瞄 物资 卡密乱输 🔗点我下载🔗 #和平精英 #内和
👍13❤1
三角洲可乐纯c版本破解 绘制 物资 无卡密验证 支持虚拟机 纯c版 🔗点我下载🔗 #三角洲 #内核
👍20
Showing the 12 most recent of 275 posts we hold for @pj7645. 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.
@pj7645 edited 2 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.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
玩那种的多,那个投票多就多更新那个
The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
三角洲模块内透玩不玩兄弟们
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
大杂烩支不支持
Shares as published. No per-option vote count is published by Telegram, so none is shown.
玩直装的多不多
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 275 most recent posts we hold, published 4 August 2026 to 6 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 5 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)” (@pj7645), 46,991 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/pj7645.
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.