❤️三角洲【Java】今日用户反馈 依旧无敌稳定连打中 全网唯一一个解密直装 稳定性毋庸置疑 用过人都说一个字【稳】! 🥰Java直装购买链接 https://682.vin/shop/R2XX832T 评论白嫖Java直装6小时卡👇 https://t.me/QYSJZKJ/7 发视频领取6小时卡或红包 https://t.me/QYSJZKJ/2831?single
👍48❤2
Signed 1

Channel
@yhtjdk
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
39,452subscribers
+3,495 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002176008797 |
|---|---|
| Type | Channel |
| Username | @yhtjdk |
| Description | 免费学习交流游戏加速 主频道:https://t.me/yhtjdk 广告位: @xiaomenzhuanxianbot 反馈和问题发送机器人 @xiaomenzhuanxianbot |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/yhtjdk |
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 the other topics.
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.
Posts published here appear in near-verbatim form on 12 other registered channels. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @yhtjdk/25525 · this entry9 Oct 2026, 20:07 UTC | @time_pd/150429 Oct 2026, 20:08 UTC | 1.00 | under a minute |
| @SJZWL/92828 Oct 2026, 13:23 UTC | @yhtjdk/28346 · this entry28 Oct 2026, 14:43 UTC | 1.00 | 80 minutes |
| @HeiXuePD/3379630 Oct 2026, 09:02 UTC | @yhtjdk/28498 · this entry30 Oct 2026, 09:02 UTC | 1.00 | under a minute |
| @yhtjdk/18524 · this entry19 Aug 2026, 02:59 UTC | @lianbingnb/1931619 Aug 2026, 08:19 UTC | 1.00 | 5.3 hours |
| @yhtjdk/19005 · this entry21 Aug 2026, 13:20 UTC | @lianbingnb/2021731 Aug 2026, 08:01 UTC | 1.00 | 10 days |
| @yhtjdk/19005 · this entry21 Aug 2026, 13:20 UTC | @yazinh/927526 Aug 2026, 03:00 UTC | 1.00 | 5 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @TwT_driver | 90 (8/8 hand-verifiable sample passed) | 1.00 | 36 minutes | this entry (51–39) |
| @time_pd | 43 (7/8 hand-verifiable sample passed) | 1.00 | 2.5 hours | this entry (25–18) |
| @SJZWL | 55 (8/8 hand-verifiable sample passed) | 0.97 | 76 minutes | @SJZWL (54–1) |
| @ZHOLMJ | 92 (8/8 hand-verifiable sample passed) | 1.00 | 2.5 hours | @ZHOLMJ (90–2) |
| @HeiXuePD | 60 (7/8 hand-verifiable sample passed) | 1.00 | 56 minutes | this entry (39–21) |
| @Cycle1337 | 44 (7/8 hand-verifiable sample passed) | 1.00 | 1.5 hours | this entry (26–18) |
| @LinYuKernel | 47 (7/8 hand-verifiable sample passed) | 1.00 | 4.7 hours | this entry (30–17) |
| @qingtPD | 53 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (34–19) |
| @lianbingnb | 10 (8/8 hand-verifiable sample passed) | 1.00 | 20 hours | even |
| @yazinh | 8 (8/8 hand-verifiable sample passed) | 0.97 | 17 hours | even |
| @Xo_eps | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @Drabanb | 16 (8/8 hand-verifiable sample passed) | 1.00 | 1.7 hours | this entry (9–7) |
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. 54 of the 54 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 944 comparable posts for this entry, running 6 August 2026 to 10 November 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.
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 keys clone_copy · clone_mutual · clone_source, last confirmed 11 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.
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.
18 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 10:09 | 39,452 | +3 |
| 8 Nov 2026, 19:08 | 39,449 | +24 |
| 7 Nov 2026, 14:54 | 39,425 | +11 |
| 6 Nov 2026, 16:37 | 39,414 | +26 |
| 5 Nov 2026, 14:35 | 39,388 | +13 |
| 4 Nov 2026, 15:30 | 39,375 | +1 |
| 3 Nov 2026, 15:36 | 39,374 | -17 |
| 2 Nov 2026, 13:39 | 39,391 | -6 |
| 1 Nov 2026, 10:26 | 39,397 | -68 |
| 31 Oct 2026, 11:56 | 39,465 | +20 |
| 30 Oct 2026, 12:19 | 39,445 | -2 |
| 28 Oct 2026, 18:50 | 39,447 | +28 |
| 27 Oct 2026, 15:16 | 39,419 | +13 |
| 26 Oct 2026, 16:16 | 39,406 | +21 |
| 25 Oct 2026, 18:56 | 39,385 | +32 |
| 24 Oct 2026, 20:08 | 39,353 | +63 |
| 23 Oct 2026, 21:16 | 39,290 | +28 |
| 22 Oct 2026, 21:01 | 39,262 | +18 |
| 21 Oct 2026, 20:38 | 39,244 | +21 |
| 20 Oct 2026, 17:11 | 39,223 | first reading |
2,116 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 256 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. It is computed over the 538 of 540 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 2,116 (6 August 2026 – 11 November 2026) |
| Views total | 64,618 |
| Reactions total | 21,742 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 10:45 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 11 November 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.
Measured directly from 47 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.
34,871 reactions across 979 posts, in 6 distinct kinds. The most used accounts for 98.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 34,405 | 98.7% | |
| ❤ | 409 | 1.17% | |
| 🔥 | 39 | 0.112% | |
| 🥰 | 8 | 0.023% | |
| 😱 | 6 | 0.017% | |
| 🤯 | 4 | 0.011% |
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 981 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 34,871 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 23 September 2026 to 11 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.
Telegram’s own ‘edited’ marker: 1 of 542 posts held from the last 30 days (0.185%) 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).
❤️三角洲【Java】今日用户反馈 依旧无敌稳定连打中 全网唯一一个解密直装 稳定性毋庸置疑 用过人都说一个字【稳】! 🥰Java直装购买链接 https://682.vin/shop/R2XX832T 评论白嫖Java直装6小时卡👇 https://t.me/QYSJZKJ/7 发视频领取6小时卡或红包 https://t.me/QYSJZKJ/2831?single
👍48❤2
Signed 1
大肥鱼三角洲2.3内核算法解密 已解决三角洲最新加密 下载地址 https://drive.uc.cn/s/316265f7583f4?public=1 卡密联系机器人获取 @bbblajibot
👍52❤1
🎮库洛米 v41.0.0 11.11最新更新内容 🤩三角洲公益雷达点我查看 更新内容如下 修复解密一过于卡顿,延迟高问题 修复开启解密掉针锁帧问题 新增算法解密二 新增算法解密三,并修复玩一半掉效果问题 新增算法解密四 修复自喵只打人机 优化 cpu 占用,修复悬浮窗掉帧问题 修复若干问题和bug 下载地址: https://drive.uc.cn/s/316265f7583f4?public=1 公益卡密: 联系机器人获取 @bbblajibot 🎮工艺暗区版本点我查看 ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群组
👍39
🥰三角洲【宙斯】容器直装11/11反馈漏打➕范围稳定奔放连打中!!“航天基地”持续奔放中! ❤️全网唯一全套丝滑蓝光绘制 ‼️漏打自瞄 掩体变色 范围攻击! 😙绘制盒子 手持 人数 等等等等!!这里不bb太多了! 🌟玩别的直装杀多了第三方 玩宙斯杀多了屁事没有 其他直装还在更新 昨天宙斯首发更新解决全部问题 还不明白该怎么选择吗 宙斯直装购买链接 https://mall.682fk.cn/shop/R2XX832T 评论白嫖宙斯直装6小时卡👇 https://t.me/QYSJZFZ/950 发视频领取6小时卡或红包 https://t.me/QYSJZFZ/921 😙招快手直播员播宙斯直装【包卡密】能直播联系我 @JHsae8
👍41❤1
Signed 1
大肥鱼飞天更新1.1版本 飞天如果只上下爬梯那就加大一下爬梯速度就行了 可以搭配其他辅助使用 不吃举报即可 更新:修复触摸卡屏 下载地址 https://drive.uc.cn/s/316265f7583f4?public=1 公益卡密: 联系机器人获取大肥鱼卡密 @bbblajibot 官方频道 @BIGFATFISH6 温馨提示小号娱乐即可
👍10
😀三角洲【宙斯】容器直装11/10反馈漏打➕范围稳定奔放连打中!! 🥹全网唯一全套丝滑蓝光绘制 ‼️漏打自瞄 掩体变色 范围攻击! 😙绘制盒子 手持 人数 等等等等!!这里不bb太多了! 🫵功能齐全 稳定顶尖 售后无忧!便捷易上手!安装即用 ! 🥰宙斯直装购买链接 https://mall.682fk.cn/shop/R2XX832T 评论白嫖宙斯直装6小时卡👇 https://t.me/QYSJZFZ/950 发视频领取6小时卡或红包 https://t.me/QYSJZFZ/1700 😙招快手直播员播宙斯直装【包卡密】能直播联系我 @JHsae8
👍22
Signed 1
三角洲kx爬楼飞天 第三人称 追踪 👍👍👍 @Sakurayyda
👍24
半夜想要看片👀找不到的各种资源群里都可以搜索的到 🔍 相关游戏外挂安装包也可以搜的到 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781
👍38❤1
大肥鱼飞天更新1.1版本 飞天如果只上下爬梯那就加大一下爬梯速度就行了 更新:修复触摸卡屏 下载地址 https://drive.uc.cn/s/316265f7583f4?public=1 公益卡密: @BIGFATFISH6 温馨提示小号娱乐即可
👍45
?自己号封了开挂🤡没号玩? 点我入手全游戏开挂满级皮肤账号低价账号 只需几块钱买到一个满级开挂号🎁 📩💵😁购买网址😁📩💵 http://aoafk.melognb.cn/shop/V5YPKDEA 全游戏开科技满级便宜号购买💠🎮🎮🎮🎮🎮🎮🎮🎮🎮🎮🎮🎵🎵 ⚠️官网频道 @WGSJH888 🐔账号问题在线解决问题客服 @XKL878 双向给客服发不了信息联系机器人补号 @duolaamnb55bot 👇上号器+上号视频之类的👇 https://wwass.lanzoub.com/iE9qi3qm0v3g 账号在线查询皮肤网页版本验号器点我查看 免费送号活动点我查看 点我免费制作属于自己的上号器验号器锁号器
👍49
Signed 频道主全网收管理@xkl878
三角洲双子星1.8公益解密更新算法解密 采用算法/udp双解密方案 解决3.0迷雾 正在公益中!正在公益中!欢迎体验! ❤️支持天机/骁龙等处理器 适配驱动:Kairos和Paradise驱动 1.7版本更新内容如下: 1.修复解密部分人偏框 2.优化解密速率 🔗公益安装包频道下载 🔥驱动1 🔥驱动2 🔥双子星公益解密卡密获取/疑难杂症问题 🌟🙃🌟➡️ @SZXNBPD ❗️❗️➡️ @SZXPD777
👍63
三角洲先来玩库洛米的库洛米解密未和谐依旧无视三角洲最新更新 @kuluomi886 晚点优化一下就不卡了
👍53
Showing the 12 most recent of 2,116 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.
@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.
We recorded 93 posts on @yhtjdk as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 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.
@yhtjdk named 10 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“派大黑腾讯*网易免费加速器(2026持续更新中)” (@yhtjdk), 39,452 subscribers as measured 10 November 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.