Telegram RegisterThe public register of Telegram
Telegram profile photo for 狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)

Channel

狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)

@pj7645

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

62,890subscribers

+24,534 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002366586765
TypeChannel
Username@pj7645
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 October 2026
Measurements held46
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/pj7645

Topic

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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 why it has no browse page of its own yet.

Growth

38,17462,89050,5327 August 2026 — 38,356 subscribers7 August 2026 — 38,356 subscribers8 August 2026 — 38,305 subscribers9 August 2026 — 38,271 subscribers10 August 2026 — 38,220 subscribers11 August 2026 — 38,174 subscribers12 August 2026 — 39,014 subscribers14 August 2026 — 40,425 subscribers15 August 2026 — 41,561 subscribers16 August 2026 — 42,373 subscribers17 August 2026 — 42,938 subscribers18 August 2026 — 43,134 subscribers19 August 2026 — 43,375 subscribers20 August 2026 — 43,535 subscribers21 August 2026 — 43,882 subscribers23 August 2026 — 44,229 subscribers24 August 2026 — 44,491 subscribers25 August 2026 — 44,563 subscribers26 August 2026 — 44,676 subscribers27 August 2026 — 44,794 subscribers28 August 2026 — 44,894 subscribers29 August 2026 — 45,246 subscribers30 August 2026 — 45,451 subscribers31 August 2026 — 45,667 subscribers1 September 2026 — 45,985 subscribers2 September 2026 — 46,240 subscribers4 September 2026 — 46,470 subscribers6 September 2026 — 46,991 subscribers9 September 2026 — 48,248 subscribers12 September 2026 — 48,740 subscribers13 September 2026 — 49,020 subscribers15 September 2026 — 49,559 subscribers17 September 2026 — 50,861 subscribers29 September 2026 — 54,715 subscribers5 October 2026 — 56,775 subscribers9 October 2026 — 58,010 subscribers13 October 2026 — 59,631 subscribers14 October 2026 — 59,845 subscribers16 October 2026 — 60,070 subscribers16 October 2026 — 60,491 subscribers17 October 2026 — 61,106 subscribers18 October 2026 — 61,431 subscribers19 October 2026 — 61,699 subscribers20 October 2026 — 62,049 subscribers21 October 2026 — 62,516 subscribers23 October 2026 — 62,890 subscribers7 August 202623 October 2026
46 measurements spanning 77 days, net +24,534. 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 34,467–66,597 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
23 Oct 2026, 02:1162,890+374
21 Oct 2026, 22:5962,516+467
20 Oct 2026, 16:5062,049+350
19 Oct 2026, 15:5961,699+268
18 Oct 2026, 19:1161,431+325
17 Oct 2026, 20:2761,106+615
16 Oct 2026, 22:5560,491+421
16 Oct 2026, 00:1960,070+225
14 Oct 2026, 21:5859,845+214
13 Oct 2026, 16:1659,631+1,621
9 Oct 2026, 20:5958,010+1,235
5 Oct 2026, 11:1756,775+2,060
29 Sept 2026, 12:3954,715+3,854
17 Sept 2026, 20:5550,861+1,302
15 Sept 2026, 18:2249,559+539
13 Sept 2026, 23:5849,020+280
12 Sept 2026, 07:1848,740+492
9 Sept 2026, 23:4048,248+1,257
6 Sept 2026, 13:4046,991+521
4 Sept 2026, 07:3746,470first reading

Engagement

1,120 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 251 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.42%
avg views ÷ 62,890 subscribers
Avg views / post
2,150
637 posts measured
Reaction rate
3.11%
reactions ÷ views · ER floor
Posts in window
637
of 1,120 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 October 2026
Posts held1,120 (4 August 2026 – 23 October 2026)
Views total1,368,861
Reactions total42,619
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Oct 2026, 02:00 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

Video runtime
41m 03s
Average length
30s

Measured directly from 82 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.

Reaction mix

48,147 reactions across 999 posts, in 42 distinct kinds. The most used accounts for 90.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍43,44690.2%
❤1,4753.06%
🥰6511.35%
🔥5511.14%
👏5451.13%
😍3170.658%
🤔2810.584%
🤡1120.233%
🤣970.201%
🍌730.152%
🤩640.133%
🕊530.11%
🤪530.11%
👌510.106%
😱510.106%
🤬480.1%
🤝360.075%
🤮350.073%
🙏310.064%
😁250.052%
22 further kinds1520.316%

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 999 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 48,147 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 21 August 2026 to 23 October 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 Stars

Stars received
1
across the posts below
Posts paid on
1
of 1,000 we hold a reading for · 0.1%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @pj7645. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 21 August 2026 to 23 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

23 Oct 2026, 01:30 UTC137 views35 reactionsread 23 October 2026

破解投稿联系 @Lingxiaoxi6 @Qianyeq 防止倒卖2改每日卡密点我获取 ✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀 狗头交流群: https://t.me/goutou46

👍35

Signed TGBot Pro

23 Oct 2026, 01:10 UTC215 views41 reactionsread 23 October 2026
Photo

频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1002366586765_8089084457_groups_50d43973

👍41

Signed SOSO搜搜

22 Oct 2026, 23:26 UTC226 views34 reactionsread 23 October 2026
Photo

✅不会小学生还没有ROOT米八吧? 今晚一共送出8️⃣台ROOT米八🌟 😒而且全是配置12+256一点都不卡 (点击下面蓝色字体进入频道) 点我进入频道获取ROOT米八 一定要加入频道才能获取抽奖资格

👍32❤1🤣1

Signed 阿呆 (全网收管理) @adggku

22 Oct 2026, 23:15 UTC572 views33 reactionsread 23 October 2026
Photo

✅王者荣耀grok解密算法界界破解9.23 ✅偏框开启解密 不偏可以不用开 🔗点我下载🔗点我获取卡密🔗 #王者荣耀 #内核

👍33

22 Oct 2026, 17:59 UTC≈1,190 views52 reactionsread 23 October 2026
File

🔥HERO免费开盒助手🔥 🌈开盒专用🌈 🌈HERO户籍猎手🌈 安装包下载链接 https://wwbnv.lanzouw.com/imiFi4c8kb3e 密码:8888 🔨支持免费查询:手机号、身份证、QQ号、微信号、抖音号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、小红书、网易云ID、脸书、推特、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔... 🥰官方卡密售卖机器人⬇️⬇️ 👉 @ATC_AutoShop_Bot 👈 注: 最老猎手之一 也是唯一猎手其余仿冒 唯一权威官方频道 t.me/PLCOINP/8

👍52

Signed 全网收质量频道@ai520i

22 Oct 2026, 16:12 UTC≈1,500 views72 reactionsread 23 October 2026

投稿联系 @Lingxiaoxi6 直接发包发卡密 包下载下来发,别发链接 23日卡密:点我获取 点击就可以获取 聊天吹牛: https://t.me/goutou46

👍71❤1

22 Oct 2026, 15:29 UTC≈1,690 views90 reactionsread 23 October 2026

三角洲公益雷达机器人3/4号雷达卡密已补100张,私信机器人免费获取! @bbblajibot

👍85🔥2🥰2🤔1

22 Oct 2026, 13:55 UTC≈2,140 views92 reactionsread 23 October 2026
Video

✅三角洲ZD注入内部12.0快破解 ✅人物透视 人物内透 算法自瞄 ✅人物追踪 人物高跳 人物缩小 ✅人物加速 物资透视 三称广角 🔗点我下载🔗 #三角洲 #注入

👍83🥰4🔥3❤1🤔1

22 Oct 2026, 13:29 UTC275 views90 reactionsread 22 October 2026

破解投稿联系 @Lingxiaoxi6 @Qianyeq 防止倒卖2改每日卡密点我获取 ✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀 狗头交流群: https://t.me/goutou46

👍85❤3🤩2

Signed TGBot Pro

22 Oct 2026, 12:46 UTC≈2,400 views82 reactionsread 23 October 2026

这个4.9有三个解密⚽️,4.8俩个解密

👍76🥰3❤2🔥1

22 Oct 2026, 12:30 UTC≈2,500 views78 reactionsread 23 October 2026

还想玩什么游戏的什么项目 火速在此条信息下评论 点下面链接给狗头哥的频道助力一下➕曝光! https://t.me/soso?start=boost_pj7645_8089084457

👍70❤3🥰3🤔2

22 Oct 2026, 12:29 UTC212 views70 reactionsread 22 October 2026

破解投稿联系 @Lingxiaoxi6 @Qianyeq 防止倒卖2改每日卡密点我获取 ✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀 狗头交流群: https://t.me/goutou46

👍66❤2🤔1🥰1

Signed TGBot Pro

Showing the 12 most recent of 1,120 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.

Posts edited after publishing

@pj7645 edited 15 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
8 August 2026
Most recent edit
22 October 2026

Polls

The 6 most recent of 7 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.

17 Oct 2026, 13:26 UTCAnonymous Poll1,180 voters approx.

喜欢玩什么热门游戏多一点

  1. 三角洲行动32%
  2. 王者荣耀20%
  3. 暗区突围10%
  4. 和平精英17%
  5. pubg5%
  6. 瓦17%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

10 Oct 2026, 16:45 UTCAnonymous Poll502 voters

接下来想要玩哪个

  1. 三角洲T1算法解密45%
  2. 三角洲lsenna解密12%
  3. 三角洲LGB解密33%
  4. 三角洲arrogance解密10%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 09:43 UTCAnonymous Poll231 voters

三角洲纯C的要不要无解密支持虚拟机

  1. 要44%
  2. 不用60%

The shares total 104%, 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.

10 Sept 2026, 07:31 UTCAnonymous Poll178 voters

库洛米AI吸附自瞄有没有要,带声波雷达 【支持多款游戏】支持免root和root

  1. 要87%
  2. 不要15%

The shares total 102%, 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.

3 Sept 2026, 15:56 UTCAnonymous Poll133 voters

玩那种的多,那个投票多就多更新那个

  1. 内核85%
  2. 直装11%
  3. 改文件11%

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.

27 Aug 2026, 10:38 UTCAnonymous Poll121 voters

三角洲模块内透玩不玩兄弟们

  1. 玩70%
  2. 不玩33%

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.

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 1,000 most recent posts we hold (the sample is capped at 1,000), published 21 August 2026 to 23 October 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 42 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

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

“狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)” (@pj7645), 62,890 subscribers as measured 23 October 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.