Telegram RegisterThe public register of Telegram
Telegram profile photo for 海盗狗内核主频道

Channel

海盗狗内核主频道

@FXQPJ

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

9,970subscribers

+167 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002189932200
TypeChannel
Username@FXQPJ
Description合作批卡联系 @hdg88688 海盗狗总端
Created3 July 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held43
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/FXQPJ

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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

9,68810,1739,930.512 August 2026 — 9,803 subscribers12 August 2026 — 9,802 subscribers15 August 2026 — 9,780 subscribers19 August 2026 — 9,748 subscribers22 August 2026 — 9,717 subscribers25 August 2026 — 9,688 subscribers28 August 2026 — 9,710 subscribers31 August 2026 — 9,728 subscribers4 September 2026 — 9,765 subscribers10 September 2026 — 9,828 subscribers13 September 2026 — 9,923 subscribers18 September 2026 — 9,917 subscribers28 September 2026 — 9,965 subscribers5 October 2026 — 10,075 subscribers10 October 2026 — 10,107 subscribers13 October 2026 — 10,147 subscribers15 October 2026 — 10,152 subscribers16 October 2026 — 10,162 subscribers17 October 2026 — 10,166 subscribers18 October 2026 — 10,173 subscribers19 October 2026 — 10,161 subscribers20 October 2026 — 10,155 subscribers20 October 2026 — 10,149 subscribers22 October 2026 — 10,142 subscribers23 October 2026 — 10,127 subscribers24 October 2026 — 10,126 subscribers25 October 2026 — 10,118 subscribers26 October 2026 — 10,110 subscribers27 October 2026 — 10,104 subscribers28 October 2026 — 10,098 subscribers29 October 2026 — 10,093 subscribers30 October 2026 — 10,088 subscribers31 October 2026 — 10,083 subscribers1 November 2026 — 10,073 subscribers2 November 2026 — 10,064 subscribers3 November 2026 — 10,054 subscribers4 November 2026 — 10,046 subscribers5 November 2026 — 10,035 subscribers6 November 2026 — 10,029 subscribers7 November 2026 — 10,022 subscribers8 November 2026 — 10,003 subscribers9 November 2026 — 9,992 subscribers14 November 2026 — 9,970 subscribers9,97012 August 202614 November 2026
43 measurements spanning 94 days, net +167. 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 9,615–10,246 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
14 Nov 2026, 13:049,970-22
9 Nov 2026, 22:089,992-11
8 Nov 2026, 13:0110,003-19
7 Nov 2026, 06:1110,022-7
6 Nov 2026, 07:0010,029-6
5 Nov 2026, 03:1510,035-11
4 Nov 2026, 02:5610,046-8
3 Nov 2026, 02:5110,054-10
2 Nov 2026, 05:5610,064-9
1 Nov 2026, 03:5010,073-10
31 Oct 2026, 06:5810,083-5
30 Oct 2026, 04:3110,088-5
29 Oct 2026, 06:3610,093-5
28 Oct 2026, 02:5810,098-6
27 Oct 2026, 05:4810,104-6
26 Oct 2026, 06:2910,110-8
25 Oct 2026, 07:2710,118-8
24 Oct 2026, 09:3510,126-1
23 Oct 2026, 10:0910,127-15
22 Oct 2026, 06:5110,142first reading

Engagement

61 posts held, back to 3 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.57%
avg views ÷ 9,970 subscribers
Avg views / post
256
1 post measured
Reaction rate
1.56%
reactions ÷ views · ER floor
Posts in window
1
of 61 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 3 November 2026
Posts held61 (3 July 2024 – 3 November 2026)
Views total256
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 00:07 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
121
Videos
1
Links
5

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

Video runtime
4s
Average length
4s

Measured directly from 1 video 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

187 reactions across 43 posts, in 5 distinct kinds. The most used accounts for 79.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍14879.1%
❤2714.4%
🤪63.21%
🤓52.67%
😁10.535%

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 45 of the 61 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 187 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 61 most recent posts we hold, published 3 July 2024 to 3 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: 0 of 1 post held from the last 30 days (0%) 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).

3 Nov 2026, 10:14 UTC256 views4 reactionsread 17 November 2026
Forwarded from @LDYYDSNAPhoto

✔️ADE典藏版 三服 直达无痕解密内核/三角洲—暗区: 🈷️卡密不限设备↓↓↓ 3AQ6-67LK-GPUU-YKIM (已封禁) 支持游戏: 三角洲国服-三角洲国际服-三角洲台服 暗区国服-暗区国际服 🌐更新到了最新的版本号 🌐 适配暗区国服最新赛季 👀提卡链接 https://www.zidianidc.com/shop/ADE 🔔官方频道 https://t.me/LDYYDSNA 💥反馈加时联系 @vfdxxdse ➡️将zip压缩包里的三个lossless.xz文件放入到/data/adb/ade/目录下即可开启掩体判断 🔥对接码 ADEBUFF 🔥对接地址 www.zidianidc.com 🛡上架福利周卡 限制一个账号一单 📣代理对接限时 超优惠 3折对接 🎄转发消息到任意5个群组联系客服领取 免费卡密 @vfdxxdse

👍3❤1

17 Oct 2026, 15:47 UTC883 views8 reactionsread 17 November 2026

说你爹是盗版的 你爹我这个项目刚出的第一天本人就拿下后台 我盗版你麻痹

👍8

17 Oct 2026, 15:45 UTC866 views7 reactionsread 17 November 2026

晚上我云更一下 明天正常恢复运营此项目 低于25一律盗版处理

👍7

17 Oct 2026, 14:07 UTC862 views10 reactionsread 17 November 2026

评论 海岛狗解密送卡 20个评论领天卡 @hdg88688

👍9❤1

17 Oct 2026, 14:02 UTC853 views9 reactionsread 17 November 2026

没有跑路 不好意思走的时候信息都没发

👍9

1 Oct 2026, 02:54 UTC≈1,610 views3 reactionsread 17 November 2026
Photo

Photo, posted without a caption

👍3

1 Oct 2026, 02:54 UTC≈1,930 views3 reactionsread 17 November 2026
Photo

Photo, posted without a caption

👍3

Showing the 12 most recent of 61 posts we hold for @FXQPJ. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

12 May 2026, 18:25 UTCAnonymous Poll1,370 voters approx.

想要破解什么类型 全网任何项目都能破 破不了当场退网

  1. 1.三角洲50%
  2. 2.和平6%
  3. 3.王者4%
  4. 4.暗区31%
  5. 5.cf3%
  6. 6.其他6%

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 61 most recent posts we hold, published 3 July 2024 to 3 November 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

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.

Mentions

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.

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.

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

“海盗狗内核主频道” (@FXQPJ), 9,970 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/FXQPJ.

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.