Telegram RegisterThe public register of Telegram
Telegram profile photo for 派大黑腾讯*网易免费加速器(2026持续更新中)

Channel

派大黑腾讯*网易免费加速器(2026持续更新中)

@yhtjdk

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry

38,094subscribers

+2,137 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-1002176008797
TypeChannel
Username@yhtjdk
Description免费学习交流游戏加速 主频道:https://t.me/yhtjdk 广告位: @xiaomenzhuanxianbot 反馈和问题发送机器人 @xiaomenzhuanxianbot
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/yhtjdk

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 41% 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.

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 word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@yhtjdk/16910 · this entry6 Aug 2026, 16:19 UTC@qingtPD/166667 Aug 2026, 05:22 UTC1.0013 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@qingtPD6 (5/6 hand-verifiable sample passed)1.00under a minuteeven

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 0 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 22 comparable posts for this entry, running 6 August 2026 to 7 August 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).

Across the whole group of 3, the earliest publisher we hold is @yhtjdk — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

35,95738,09437,025.57 August 2026 — 35,957 subscribers8 August 2026 — 35,972 subscribers9 August 2026 — 35,983 subscribers10 August 2026 — 36,000 subscribers11 August 2026 — 36,023 subscribers12 August 2026 — 36,039 subscribers13 August 2026 — 36,027 subscribers14 August 2026 — 36,007 subscribers16 August 2026 — 36,053 subscribers17 August 2026 — 36,088 subscribers18 August 2026 — 36,109 subscribers19 August 2026 — 36,119 subscribers20 August 2026 — 36,167 subscribers21 August 2026 — 36,223 subscribers23 August 2026 — 36,279 subscribers24 August 2026 — 36,408 subscribers25 August 2026 — 36,528 subscribers26 August 2026 — 36,598 subscribers27 August 2026 — 36,680 subscribers28 August 2026 — 36,762 subscribers29 August 2026 — 36,887 subscribers30 August 2026 — 36,968 subscribers31 August 2026 — 37,043 subscribers2 September 2026 — 37,041 subscribers3 September 2026 — 37,100 subscribers5 September 2026 — 37,195 subscribers8 September 2026 — 37,315 subscribers11 September 2026 — 37,435 subscribers13 September 2026 — 37,525 subscribers14 September 2026 — 37,631 subscribers16 September 2026 — 37,704 subscribers19 September 2026 — 37,825 subscribers25 September 2026 — 38,094 subscribers7 August 202625 September 2026
33 measurements spanning 49 days, net +2,137. 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 35,636–38,415 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 15:2038,094+269
19 Sept 2026, 01:0137,825+121
16 Sept 2026, 17:3737,704+73
14 Sept 2026, 17:2137,631+106
13 Sept 2026, 02:1737,525+90
11 Sept 2026, 03:3837,435+120
8 Sept 2026, 08:3837,315+120
5 Sept 2026, 05:1737,195+95
3 Sept 2026, 10:2437,100+59
2 Sept 2026, 02:2637,041-2
31 Aug 2026, 23:2737,043+75
30 Aug 2026, 19:2536,968+81
29 Aug 2026, 19:1336,887+125
28 Aug 2026, 17:1836,762+82
27 Aug 2026, 17:0336,680+82
26 Aug 2026, 20:2736,598+70
25 Aug 2026, 18:3336,528+120
24 Aug 2026, 17:1636,408+129
23 Aug 2026, 03:1836,279+56
21 Aug 2026, 13:0336,223first reading

Engagement

1,211 posts held, back to 6 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 146 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.724%
avg views ÷ 38,094 subscribers
Avg views / post
276
657 posts measured
Reaction rate
5.18%
reactions ÷ views · ER floor
Posts in window
683
of 1,211 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. It is computed over the 656 of 657 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held1,211 (6 August 2026 – 27 September 2026)
Views total181,177
Reactions total9,377
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 02:41 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
≈7,800
Videos
≈256
Links
≈2,950

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
20m 07s
Average length
30s

Measured directly from 40 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

13,005 reactions across 959 posts, in 7 distinct kinds. The most used accounts for 96.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12,59896.9%
❤3662.81%
🔥150.115%
🥰140.108%
😱60.046%
🤯40.031%
👏20.015%

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 959 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 13,005 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 14 August 2026 to 27 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.

Recent posts

27 Sept 2026, 01:54 UTC64 views27 reactionsread 27 September 2026
Forwarded from @QYSJZKJPhoto

✅三角洲【毒蛇直装】重磅来袭 !全网唯一公益稳定直装 🌟重塑巅峰体验!全网顶级稳定直装重磅来袭 复刻昔日无敌稳定性 再也不必苦于对局劣势! 😙功能介绍:人物自瞄/人物绘制/物资绘制/人物方框/人物血量/名称绘制/增加爆率 ⏩目前全网7天/十年/三方问题一直困扰兄弟们 毒蛇携手顶尖团队 诚意打造全网功能最全 稳定性拉满的直装 🫡下载链接:https://wwbfz.lanzout.com/b019w6tdmj 密码:dsnb 📣永久公益卡密:QYSJZKJ 反馈发送给 @JHsae8 👍毒蛇中国区正版官方频道 ❗️❗️https://t.me/QYSJZKJ ❗️❗️https://t.me/QYSJZKJ ❗️❗️https://t.me/QYSJZKJ ❗️❗️➡️点击加入【全部频道】 注:一定要全部加入频道 才可生效卡密

👍27

Signed 星辞

27 Sept 2026, 01:21 UTC127 views20 reactionsread 27 September 2026
Forwarded from @QYSJZFZPhoto

✅三角洲【阿波罗追踪直装】重磅来袭 !全网唯一追踪稳定直装 9/27反馈稳定连打奔放中! 😙全网首发且唯一概率追踪直装 👍概率 范围可全部自由调节! 😀丝滑蓝光高清全套绘制 包括绘制武器装备等等!! ⏩标记物资价值 颜色重点标记高价值物资!寻宝更方便!嘎嘎得吃保持富态! 🏆卡网搜索【阿波罗】即可购买体验 欢迎各大代理一起推广 !

👍20

Signed 星辞

26 Sept 2026, 18:58 UTC308 views24 reactionsread 27 September 2026
Forwarded from @kuluomi886File

❤️库洛米v29测试版本 此版本为测试版本 如遇到问题交流群反馈就行 目前还是公益 解密a1/a2/a3/a4 都可测试哪个能用就用哪个 如果遇到驱动刷不进去就先去用v28版本先输入驱动再来执行v29版本就行了 公益解密卡密: @kuluomi886 (进频道才能用) 此版本解密每个人能用的可能不同 a1能用的人可能a2不能用 a3a4同理 目前很多人都说a1/a4这俩有效果的人多

👍23❤1

26 Sept 2026, 18:09 UTC330 views22 reactionsread 27 September 2026

😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益频道 enen内核频道 林羽内核频道 小雪内核频道 狗头公益破解频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进500+参与联系负责人 @didb431 全网收广告位出的直接私信我 ------------------------------------- 点我一键加入全部频道 点我一键加入全部频道 点我一键加入全部频道

👍21❤1

26 Sept 2026, 17:02 UTC351 views26 reactionsread 27 September 2026

🎮库洛米三角洲公益引擎算法解密🎮 🎮库洛米暗区公益纯算法解密版本🎮 公益三角洲/暗区解密一周9.18-9.25期间随便使用随便玩 稳定连打出来一个月了好评如潮 ⭐最新更新三角洲全息投影(角色投影) 还有本地漏打/掩体变色等效果 ✅使用教程视频点我

👍25❤1

26 Sept 2026, 17:00 UTC335 views26 reactionsread 27 September 2026

按照这个速度,貌似要开赞助三区了

👍24❤2

26 Sept 2026, 14:22 UTC36 viewsread 26 September 2026
Forwarded from @QYSJZKJPhoto

✅三角洲行动【疾风直装】9月26号已进行云更新 已经内测过了 目前无敌稳定 跑刀带妹护航首选 用过的人都说稳! 🥰疾风直装购买链接: https://mall.682fk.cn/shop/R2XX832T ✅免费白嫖6.66红包活动 https://t.me/QYSJZKJ/522 ✅评论免费领取疾风天卡: https://t.me/QYSJZKJ/7

Signed 星辞

26 Sept 2026, 14:20 UTC61 views28 reactionsread 26 September 2026

😁🩵为了后续科技软件之类的开发成本太大了😭大家没号玩买个号支持下吧 快饿死了,买个极品号猛攻吧 http://aoa.aacu.cn/shop/mxkj 🤝👍出问题换号售后客服 @mxsjh66

👍28

Signed 频道主全网收管理@WGSJH520

Showing the 12 most recent of 1,211 posts we hold for @yhtjdk. 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

@yhtjdk edited 3 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
28 August 2026
Most recent edit
8 September 2026

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.

19 Aug 2026, 10:43 UTCAnonymous Poll877 voters

目前有的内部包有下面几个需要玩哪个投票我就逆向哪个解密

  1. 保护伞最新包30%
  2. eto最新包11%
  3. 12306最新包9%
  4. evo内部最新包50%

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

星辞/月亮/AORUS/K2官方通知频道
@ZHOLMJ · 31,016
104 posts
EO三角洲官方频道
@EO66789 · 55,078
50 posts
库洛米官方频道
@kuluomi886 · 52,828
48 posts
三角洲PPT内核/范围/单解密/内透
@NB666686 · 17,135
26 posts
三角洲KG官方群
@KGKG111333 · 18,015
25 posts
雨天主频道
@yt66669 · 57,307
24 posts
三角洲MVP官方群
@MVP777888 · 24,706
20 posts
三角洲 LVO 单解密
@lvoNB888 · 5,286
19 posts
星辞/倒霉熊/K2官方通知频道
@QYWWQY · 11,005
18 posts
梦想🇨🇳主频道通知群
@MXSJH520 · 17,649
15 posts
哆啦A梦账号交易所
@WGSJH888 · 1,626
14 posts
安全D暗区突围解密内核🇨🇳【主频道】
@AQD520 · 996
11 posts
天眼内核频道
@tianyan63 · 27,999
11 posts
蛋蛋破解频道(和平精英失控进化王者荣耀三角洲)
@SJZWL · 22,224
10 posts
天问王者防闪框
@qvxvxz · 6,609
10 posts
星辞/grok/AORUS官方频道
@QYSJZFZ · 12,344
8 posts
疾风直装官方频道
@QYSJZKJ · 18,199
8 posts
梦醉主频道🇨🇳【公益暗区突围解密】
@MZAQ520 · 5,119
7 posts
花海【技术编程交流】
@HKNB1 · 247
6 posts
WWE三角洲官方频道
@WWE386 · 34,051
6 posts
小呆呆范围/单解密/内透频道
@XDDNB68 · 13,525
5 posts
三角洲摸金校尉
@mjxw668 · 23,276
5 posts
寻血猎犬官方频道
@XXLQNB6 · 23,409
4 posts
K2/牛牛/AORUS官方通知频道
@ZHWMJ · 6,911
4 posts
潮寄派派官方频道(链游项目)
@cwpp666 · 11,619
3 posts
狗头工艺破解频道(王者荣耀和平精英暗区突围pubg三角洲行动萤火突击CFM无畏契约)
@pj7645 · 50,861
3 posts
三角洲MI官方频道
@kknb699 · 11,506
2 posts
TG挂圈稳定最强互推
@qyvip666666 · 457
2 posts
时间辅助频道
@time_pd · 57,831
2 posts
黑雪主频道
@HeiXuePD · 55,818
1 post
星辞端口通知频道
@JFSJZ · 6,745
1 post
啊米诺思(KX追踪)
@Sakurayyda · 52,466
1 post
TwT无广更新频道
@TwT_update · 22,622
1 post
美国漏打
@USA_Sep · 44,536
1 post
王者Angel官方频道(天使)
@angel_kernel · 78,946
1 post
黑客公益分享(和平精英王者荣耀萤火突击CFM暗区使命
@heike258258 · 2,083
1 post
旺旺户籍助手【签到送钱💰】
@wangwangsgk · 8,564
1 post

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.

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

“派大黑腾讯*网易免费加速器(2026持续更新中)” (@yhtjdk), 38,094 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/yhtjdk.

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.