Telegram RegisterThe public register of Telegram
Telegram profile photo for 小狐狸通知频道

Channel

小狐狸通知频道

@GAMEyunduan

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

24,773subscribers

+6,052 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002075928449
TypeChannel
Username@GAMEyunduan
Description交流群:https://t.me/xiaohulitequan
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/GAMEyunduan

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 69 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@appletzpd/253430 Jul 2026, 05:42 UTC@GAMEyunduan/1166 · this entry30 Jul 2026, 05:46 UTC1.004 minutes
@appletzpd/25451 Aug 2026, 16:12 UTC@GAMEyunduan/1167 · this entry1 Aug 2026, 16:13 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@appletzpd10 (8/8 hand-verifiable sample passed)1.0072 seconds@appletzpd (10–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 9 July 2026 to 12 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 69 channels, the one whose matching posts we hold earliest is @banruo91. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 69 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

🌹林羽の小窝(随缘更新)🌸
@LinYuKernels · Channel
176,495 subscribers
小烧鸡公益频道
@appletzpd · Channel
168,165 subscribers
落叶公益
@luoyeop · Channel
132,118 subscribers
TP通知频道<有问题置顶找解决>
@TPKernel · Channel
119,691 subscribers
🌹林羽の小窝🌸
@LinYuKernel · Channel
118,570 subscribers
时间辅助频道
@time_pd · Channel
115,922 subscribers
葫芦娃公益大家庭
@HLWNHNB · Channel
114,735 subscribers
落叶公益内核
@luoyenb521 · Channel
105,804 subscribers
落叶内核
@luoyenhnb666 · Channel
90,822 subscribers
TwT驱动更新频道(新人看置顶)
@TwT_driver · Channel
88,799 subscribers
ZERO公益频道
@ZEROPD · Channel
87,879 subscribers
A内核 公益官方频道
@ANHNB666 · Channel
81,805 subscribers
黑雪主频道
@HeiXuePD · Channel
66,519 subscribers
小雪
@XiaoxuePD · Channel
66,240 subscribers
XFchart[主频道]
@XFchart · Channel
53,670 subscribers
落叶公益内核
@luoyeco · Channel
50,245 subscribers
Like公益内核/暗区-三角洲-瓦
@Likenb667 · Channel
45,255 subscribers
汉堡追锁
@hb52066 · Channel
42,179 subscribers
Cycle1337's Cheats (新人看置顶)
@Cycle1337 · Channel
41,307 subscribers
派大黑腾讯*网易免费加速器(2026持续更新中)
@yhtjdk · Channel
39,522 subscribers
Dra™
@Drabanb · Channel
39,329 subscribers
OrbitalX更新频道(原Star)
@OXKernelPD · Channel
33,545 subscribers
XU-主频道
@Drabanl · Channel
33,272 subscribers
三角洲【VIP内部】官方通知频道
@FOXNB86 · Channel
32,618 subscribers
zcr521环境
@Xiaogu_zcr521 · Channel
31,201 subscribers
星辞/001/AORUS/K2官方通知频道
@ZHOLMJ · Channel
30,576 subscribers
晴天公益内核
@YouxinNB · Channel
30,392 subscribers
小雪频道
@SnowKernelPD · Channel
29,618 subscribers
TwT无蛤蟆广更新频道
@TwT_update · Channel
29,451 subscribers
蛋蛋破解频道(和平精英失控进化王者荣耀三角洲)
@SJZWL · Channel
28,547 subscribers
🌹江颜の小窝(无广)🌸
@JiangYanKernels · Channel
28,022 subscribers
闪电直装永久公益看置顶
@xtq66688 · Channel
27,479 subscribers
花海主频道
@huahainb · Channel
26,142 subscribers
晴天主频道
@qingtPD · Channel
22,671 subscribers
🔨锤子
@CHUIZINB · Channel
22,313 subscribers
神烦狗通知频道
@azsfg66 · Channel
21,594 subscribers
三角洲稳定项目频道
@xxmnbnbnb · Channel
20,934 subscribers
XF内核频道
@XFNHNB666 · Channel
20,099 subscribers
不嘿嘿频道
@enennba · Channel
19,984 subscribers
猪猪侠AI自瞄
@aizmzzx · Channel
19,689 subscribers
AY全防频道
@cfsYYDSAN · Channel
19,018 subscribers
JG酒馆美化频道
@jiuguan86 · Channel
16,473 subscribers
Ai官方拿包,解绑发布频道
@XB11033 · Channel
16,353 subscribers
三角洲JK内部
@jk789com · Channel
15,796 subscribers
三角洲和平公益项目推荐
@xiaobaidpd · Channel
15,604 subscribers
Loki的小蜗
@LokiNB666 · Channel
14,725 subscribers
90000
@Te90000 · Channel
14,557 subscribers
修罗炮的主人
@TwT_kihan · Channel
13,961 subscribers
启航科技货源丨三脚粥-逆战未来-暗区-无畏契约-超凡-失控进化通知频道
@RTXSSSA · Channel
13,604 subscribers
凌风全防频道
@lingfeng669 · Channel
13,433 subscribers

18 more channels are in this same group but not listed individually here.

Growth

18,72124,83421,777.524,7737 August 202615 November 2026
65 measurements spanning 100 days, net +6,052. 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 17,804–25,751 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
15 Nov 2026, 15:5124,773-61
12 Nov 2026, 06:3224,834+14
10 Nov 2026, 03:0824,820+4
8 Nov 2026, 17:5424,816+66
7 Nov 2026, 08:0724,750+7
6 Nov 2026, 09:0824,743+18
5 Nov 2026, 06:1024,725+22
4 Nov 2026, 08:3924,703-2
3 Nov 2026, 10:1724,705+19
2 Nov 2026, 10:3624,686+36
1 Nov 2026, 12:0924,650+38
31 Oct 2026, 11:1924,612+33
30 Oct 2026, 12:4924,579+37
29 Oct 2026, 13:0024,542+35
28 Oct 2026, 12:5624,507+73
27 Oct 2026, 13:4924,434+31
26 Oct 2026, 10:1424,403+19
25 Oct 2026, 08:4424,384+58
24 Oct 2026, 08:0524,326+67
23 Oct 2026, 08:2624,259first reading

Engagement

41 posts held, back to 9 July 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 137 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.0%
avg views ÷ 24,773 subscribers
Avg views / post
3,730
4 posts measured
Reaction rate
1.44%
reactions ÷ views · ER floor
Posts in window
4
of 41 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 14 November 2026
Posts held41 (9 July 2026 – 14 November 2026)
Views total14,911
Reactions total215
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 15:51 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
21
Videos
4
Links
128

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.

Reaction mix

1,188 reactions across 40 posts, in 16 distinct kinds. The most used accounts for 54.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍64454.2%
❤40934.4%
🍌221.85%
😭191.60%
🤔191.60%
👎161.35%
🖕151.26%
🤗110.926%
💯90.758%
🐳80.673%
😍50.421%
😘40.337%
❤‍🔥30.253%
🎉20.168%
🔥10.084%
🙈10.084%

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

Measured over the 41 most recent posts we hold, published 9 July 2026 to 14 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 4 posts 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).

14 Nov 2026, 08:34 UTC871 views57 reactionsread 17 November 2026
Forwarded from @appletzpdFile

更新和平闪框解密 烧鸡公益频道:https://t.me/appletzpd

👍55❤2

10 Nov 2026, 23:49 UTC≈1,950 views53 reactionsread 17 November 2026
Forwarded from @appletzpdFile

适配和平新赛季软件版本

👍39😭6❤4😘4

24 Oct 2026, 01:06 UTC≈4,870 views76 reactionsread 17 November 2026
Forwarded from @appletzpdFile

修复低版本安卓系统小烧鸡无法运行bug 修复闪框解密失效 修复数组解密失效 主频道: @appletzpd 无广频道: @GAMEyunduan

👍54❤11🤔8💯3

21 Oct 2026, 01:53 UTC≈7,220 views29 reactionsread 17 November 2026
Forwarded from @appletzpdFile

小烧鸡和平更新日志 1.更新喷子连点 2.更新超体职业 3.人机人数显示逻辑优化 4.修开闪框解密以后,敌人在载具上不绘制的问题 5.添加和平sh版本 主频道: @appletzpd 无广频道: @GAMEyunduan

❤16👍13

14 Oct 2026, 21:00 UTC≈7,790 views29 reactionsread 17 November 2026
Forwarded from @appletzpdFile

修复和平最新闪框加密 主频道: @appletzpd 无广频道: @GAMEyunduan

👍21🍌5❤3

12 Oct 2026, 08:24 UTC≈9,010 views34 reactionsread 17 November 2026
Forwarded from @appletzpdFile

小烧鸡PUBG 1.修复闪框解密 👰‍♀️👰‍♀️👰‍♀️👰‍♀️👰‍♀️👰‍♀️👰‍♀️ 小烧鸡和平精英 1.添加载具鹿显示 2.修复拉力车跟货拉拉都显示赛车bug 3.修复掉后台严重问题 4.开镜自瞄加入单独部位调节跟腰射分开 主频道: @appletzpd 无广频道: @GAMEyunduan

👍21❤7🐳5💯1

8 Oct 2026, 17:39 UTC≈8,640 views31 reactionsread 17 November 2026
Forwarded from @appletzpdFile

更新和平密钥物资解密 主频道: @appletzpd 无广频道: @GAMEyunduan

👍19🍌8❤1❤‍🔥1🐳1🤗1

6 Oct 2026, 07:20 UTC≈8,200 views49 reactionsread 17 November 2026
Forwarded from @appletzpdFile

更新和平闪框解密 主频道: @appletzpd 无广频道: @GAMEyunduan

👍38❤7🍌3👎1

5 Oct 2026, 05:16 UTC≈7,620 views40 reactionsread 17 November 2026
Forwarded from @appletzpdFile

新增大地图雷达功能 主频道: @appletzpd 无广频道: @GAMEyunduan

👍36❤4

30 Sept 2026, 02:31 UTC≈9,240 views47 reactionsread 17 November 2026
Forwarded from @appletzpdFile

修复闪框解密 修复密钥解密 主频道: @appletzpd 无广频道: @GAMEyunduan

👍26❤11👎5😍2🍌1🖕1🤔1

27 Sept 2026, 15:15 UTC≈9,590 views34 reactionsread 17 November 2026
Forwarded from @appletzpdFile

小烧鸡和平🎮 修复侧边血条不能改颜色 增加血条显示距离调节 小烧鸡PUBG🎮 修复真人人机识别bug 主频道: @appletzpd 无广频道: @GAMEyunduan

👍21❤13

25 Sept 2026, 00:21 UTC≈10,100 views27 reactionsread 17 November 2026
Forwarded from @appletzpdFile

小烧鸡和平内核更新 修复更新闪框解密 修复部分设备打开悬浮窗失败 修复空投 三级包绘制问题 主频道: @appletzpd 无广频道: @GAMEyunduan

👍16❤6🤔4💯1

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

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 2 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.

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

“小狐狸通知频道” (@GAMEyunduan), 24,773 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/GAMEyunduan.

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.