Channel
@yhtjdk
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
36,039subscribers
+82 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 | 12 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 August 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 why it has no browse page of its own yet.
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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @yhtjdk/16910 · this entry6 Aug 2026, 16:19 UTC | @qingtPD/166667 Aug 2026, 05:22 UTC | 1.00 | 13 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @qingtPD | 6 (5/6 hand-verifiable sample passed) | 1.00 | under a minute | even |
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.
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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:46 | 36,039 | +16 |
| 11 Aug 2026, 06:38 | 36,023 | +23 |
| 10 Aug 2026, 04:14 | 36,000 | +17 |
| 9 Aug 2026, 05:02 | 35,983 | +11 |
| 8 Aug 2026, 07:53 | 35,972 | +15 |
| 7 Aug 2026, 13:45 | 35,957 | first reading |
164 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 28 pagesof 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 158 of 159 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 164 (6 August 2026 – 12 August 2026) |
| Views total | 35,544 |
| Reactions total | 1,319 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:52 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 12 August 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 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.
1,319 reactions across 158 posts, in 7 distinct kinds. The most used accounts for 90.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,189 | 90.1% | |
| ❤ | 119 | 9.02% | |
| 🔥 | 4 | 0.303% | |
| 🥰 | 3 | 0.227% | |
| 🤯 | 2 | 0.152% | |
| 👏 | 1 | 0.076% | |
| 😱 | 1 | 0.076% |
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 158 of the 164 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,319reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 164 most recent posts we hold, published 6 August 2026 to 12 August 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.
⭐今天我整合了挂圈各大热门频道！ 以下频道是挂圈热门频道大合集 enen内核频道 林羽内核频道 小雪内核频道 吴迪公益破解频道 时间内核频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进百人 参加联系 @didb431 (频道主联系） 参加互推要求:频道10k+日浏览800 ------------------------------------- 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️
👍8❤1
✅失控进化【K2直装/内核双版本】8月13号用户反馈 目前部分用户新版本不稳定的 可以去玩以前的版本 稳定性依旧还在🔵 🌟🥰购买链接： https://mall.682fk.cn/shop/R2XX832T 评论领取K2卡密/7.99🐛活动： https://t.me/ZHOLMJ/5586 ✅发视频领取卡密活动： https://t.me/ZHOLMJ/5583 📣点我获星辞公益端口😀
👍3❤2
Signed 星辞
爽玩，所有私信已回有漏掉的重新发
👍9❤2
公益这么久了你们买一点数据号支持一下我吧高质量低价 店铺链接：https://aoa.222bx.cn/shop/V5YPKDEA 频道 @WGSJH888 秒回售后 @WGSJH520 上号器验号器之类的 https://pan.baidu.com/s/1cTVWXSxXyuipx2XaIbB9WA?pwd=2RM7
👍9❤1
Signed 神秘人
😀😃😀三角洲 MVP 内核 模拟解密 限时公益 公益卡密 @MVP777888 限时公益 公益卡密 @MVP777888 限时公益 公益卡密 @MVP777888 ➡️MVP 内核自带解密 ➡️无需配端口、全防 ➡️启动自销毁痕迹 ➡️无视游戏扫盘 无落盘痕迹 ➡️无视文件下发 ➡️支持全部系统 支持纯C模式 功能 全局人物透视 陀螺仪自瞄 高级物资透视 …
👍16❤1🤯1
Signed 广告
Photo, posted without a caption
👍5❤2
Photo, posted without a caption
👍5❤2
公益这么久了你们买一点数据号支持一下我吧高质量低价 店铺链接：https://aoa.222bx.cn/shop/V5YPKDEA 频道 @WGSJH888 秒回售后 @WGSJH520 上号器验号器之类的 https://pan.baidu.com/s/1cTVWXSxXyuipx2XaIbB9WA?pwd=2RM7
👍10❤4
Signed 神秘人
⭐今天我整合了挂圈各大热门频道！ 以下频道是挂圈热门频道大合集 enen内核频道 林羽内核频道 小雪内核频道 吴迪公益破解频道 时间内核频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道 互推日进百人 参加联系 @didb431 (频道主联系） 参加互推要求:频道10k+日浏览800 ------------------------------------- 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️ 点我一键加入全部频道🗡️
👍9❤2
Photo, posted without a caption
👍6
Photo, posted without a caption
👍6
Photo, posted without a caption
👍6
Showing the 12 most recent of 164 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.
Citation-graph rank — 434,202 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 3 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“派大黑腾讯*网易免费加速器(2026持续更新中)” (@yhtjdk), 36,039 subscribers as measured 12 August 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.