卧槽 有这么好的频道你咋不早点告诉我? 林羽 enen 雪花 橘子作者含泪推荐的大牛频道 https://t.me/xuehuadaili 喷不了,这是真大牛
👍6🥰1
Signed 优秀.

Channel
@qingtPD
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
22,927subscribers
-53 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003674991196 |
|---|---|
| Type | Channel |
| Username | @qingtPD |
| Description | 广告联系 @HackHack998 主频道 @qingtPD 交流群 https://t.me/+DhP133ixaRNjNTRl |
| Created | 15 January 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/qingtPD |
Hacking & security — 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 67% 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/169106 Aug 2026, 16:19 UTC | @qingtPD/16666 · this entry7 Aug 2026, 05:22 UTC | 1.00 | 13 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yhtjdk | 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. 2 of the 2 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 24 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. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 8 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 |
|---|---|---|
| 1 Sept 2026, 23:48 | 22,927 | -11 |
| 1 Sept 2026, 02:57 | 22,938 | +6 |
| 31 Aug 2026, 05:35 | 22,932 | -2 |
| 30 Aug 2026, 03:46 | 22,934 | +7 |
| 29 Aug 2026, 07:12 | 22,927 | +16 |
| 28 Aug 2026, 10:24 | 22,911 | -19 |
| 27 Aug 2026, 07:34 | 22,930 | -2 |
| 26 Aug 2026, 08:47 | 22,932 | +12 |
| 25 Aug 2026, 05:43 | 22,920 | -7 |
| 24 Aug 2026, 06:13 | 22,927 | -5 |
| 22 Aug 2026, 14:55 | 22,932 | -17 |
| 21 Aug 2026, 05:13 | 22,949 | +11 |
| 20 Aug 2026, 06:36 | 22,938 | +3 |
| 19 Aug 2026, 08:28 | 22,935 | -10 |
| 18 Aug 2026, 09:14 | 22,945 | -22 |
| 17 Aug 2026, 10:05 | 22,967 | +9 |
| 15 Aug 2026, 19:26 | 22,958 | +33 |
| 14 Aug 2026, 06:08 | 22,925 | -29 |
| 12 Aug 2026, 19:13 | 22,954 | -13 |
| 11 Aug 2026, 20:12 | 22,967 | first reading |
749 posts held, back to 15 January 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 60 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 657 of 678 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 749 (15 January 2026 – 2 September 2026) |
| Views total | 82,925 |
| Reactions total | 3,303 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 12:16 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 2 September 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.
Measured directly from 83 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.
3,367 reactions across 664 posts, in 15 distinct kinds. The most used accounts for 90.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3,042 | 90.3% | |
| ❤ | 120 | 3.56% | |
| 🤓 | 67 | 1.99% | |
| 🥰 | 47 | 1.40% | |
| 😱 | 35 | 1.04% | |
| 💩 | 26 | 0.772% | |
| 🔥 | 10 | 0.297% | |
| 🖕 | 9 | 0.267% | |
| 👏 | 4 | 0.119% | |
| 🤮 | 2 | 0.059% | |
| 👎 | 1 | 0.03% | |
| 😁 | 1 | 0.03% | |
| 😘 | 1 | 0.03% | |
| 🤣 | 1 | 0.03% | |
| 🤩 | 1 | 0.03% |
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 666 of the 749 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 3,367 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 749 most recent posts we hold, published 15 January 2026 to 2 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.
卧槽 有这么好的频道你咋不早点告诉我? 林羽 enen 雪花 橘子作者含泪推荐的大牛频道 https://t.me/xuehuadaili 喷不了,这是真大牛
👍6🥰1
Signed 优秀.
❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️ udp+多种解密·工艺库洛米三角洲 欢迎来拆包真实我打假我 下单地址 https://luoye.yjsfk.cn/shop/kuluomi886 对接码: kuluomi 纯算法解密,全机型适配解密,不闪框不漏人不遁地 点我下载工艺无解密版本 点我下载收费解密版本 点我下载本地模型 工艺版本卡密: @kuluomi886 多种纯算法算法并行,一条路和谐另有兜底,一直能玩,任何解密都能开 ✅4r体验卡 ✅15/天 ✅88/周 ✅288/月 ✅卡密解绑点我✅代理批卡点我 体验卡是每天限量100张 ✅ AI自动压枪(识别图层+传感器调整,比自瞄更好演戏) ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 网页雷达+局域网雷达双端协同 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 🌟🙃🌟➡️ @kuluomi886
👍6🥰1
王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】 👍代理注册链接 对接码: 6flmo95s 欢迎对接,利润拉满
👍4🥰1
Signed 全网广告互推主打三角洲
🔠🔠🔠🔠小意数据货源站 🔠🔠🔠🔠(什么数据号都有) 🎮🎮🎮🎮🎮 😃每天送500免费号!!卡网领取😃 😙😍😗😋😝🙃😜🤨😜 👉卖垃圾号死妈死全家出门被车撞 真实价格有任何虚假死全家 吊打全网数据号同行,他们不敢给的我里统统给你们,小意从不卖垃圾号从不宰客户⬅️ 😇🙃😉请加入(免费送号通知群): https://t.me/xiaoyishujuhao 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 🥰唯一下单地址(进不去关vpn) https://dg.001122.top/shop/xiao 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 1️⃣上号前请先下面网站查询在线状态! 验号.com 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 2️⃣安卓上号器(自带拦截可防冻结人脸) https://www.123865.com/s/JS5eVv-E4JIh ✅点我看真实真人反馈如有虚假出门被撞死 ✅点我看真实真人反馈如有虚假出门被撞死
👍4🥰1
Signed 吴 在
三角洲国服算法解密—护航仔 ━━━━━━━━━━━━━━━━ ⭐️购买地址 : https://luoye.yjsfk.cn/shop/R77LYAUH ━━━━━━━━━━━━━━━━ ✅下载 ✅网盘下载 ✅解绑地址 ━━━━━━━━━━━━━━━━ 🟢使用教程 🟢护航仔详细介绍 ━━━━━━━━━━━━━━━━ ✔️疑难杂症解决 ✔️反馈图加时 ━━━━━━━━━━━━━━ ❤️护航仔打单俱乐部 😃代理批卡客服:@hhz1666 😃双向bot:@hhzsxjqrbot 🥇技术客服1:@frs101027 🥈技术客服2:@skkbkp 🥉技术客服3:@zhehan6696 🥉技术客服4:@taffy996 使用中遇到任何问题请联系技术客服解决 交流群:https://t.me/hhzjlq
👍6🥰1
Signed 广告机器人
庆祝频道人数22k 给大家发一个红包
👍5
🎉🧧红包发送成功🧧🎉 ✔️达利客服-娜娜 发送了一个红包 💵总金额: 5888 U💰 📊 剩余: 188/398 🥇 76.88 USDT - nbns 🥈 56.10 USDT - 不凡 🥉 55.95 USDT - 辣椒免费公益
👍5
🔠🔠🔠🔠小意数据货源站 🔠🔠🔠🔠(什么数据号都有) 🎮🎮🎮🎮🎮 😃每天送500免费号!!卡网领取😃 😙😍😗😋😝🙃😜🤨😜 👉卖垃圾号死妈死全家出门被车撞 真实价格有任何虚假死全家 吊打全网数据号同行,他们不敢给的我里统统给你们,小意从不卖垃圾号从不宰客户⬅️ 😇🙃😉请加入(免费送号通知群): https://t.me/xiaoyishujuhao 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 🥰唯一下单地址(进不去关vpn) https://dg.001122.top/shop/xiao 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 1️⃣上号前请先下面网站查询在线状态! 验号.com 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸 2️⃣安卓上号器(自带拦截可防冻结人脸) https://www.123865.com/s/JS5eVv-E4JIh ✅点我看真实真人反馈如有虚假出门被撞死 ✅点我看真实真人反馈如有虚假出门被撞死
👍5
Signed 吴 在
晴天主频道 pinned a photo
❗️❗️❗️❗️❗️❗️❗️❗️❗️❗️ udp+多种解密·工艺库洛米三角洲 欢迎来拆包真实我打假我 下单地址 https://luoye.yjsfk.cn/shop/kuluomi886 对接码: kuluomi 纯算法解密,全机型适配解密,不闪框不漏人不遁地 点我下载工艺无解密版本 点我下载收费解密版本 点我下载本地模型 工艺版本卡密: @kuluomi886 多种纯算法算法并行,一条路和谐另有兜底,一直能玩,任何解密都能开 ✅4r体验卡 ✅15/天 ✅88/周 ✅288/月 ✅卡密解绑点我✅代理批卡点我 体验卡是每天限量100张 ✅ AI自动压枪(识别图层+传感器调整,比自瞄更好演戏) ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 网页雷达+局域网雷达双端协同 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 🌟🙃🌟➡️ @kuluomi886
👍3
三角洲Jk内部 已适配新赛季 无视偏漏,无视加密,无视破解 专供俱乐部 长期合作 素材来自 萌萌猫 全程无剪辑,精彩击杀集锦 使用机型 y700四代 欢迎俱乐部长期对接合作 不偏不漏,有能力长期更新,解决问题(🈲跑路🈲改名⭕️米) 开卡售后合作咨询客服 @ask1525 点击加入JK官方通知频道 点击加入JK官方通知频道 点击加入JK官方通知频道
👍6
Signed 推广 AI
🚨🚨🚨 ➡️三角洲KG内核 UDP解密 ❤️支持三角洲-国服 ❤️可以无视三角洲加密坐标 ❤️无需配置任何参数 ❤️不动任何游戏数据! ❤️支持全系统 支持纯C模式 懒得介绍了 功能齐全 无需多说 下单地址 https://yun.ffkpp.top/shop/33EAJS2A …
👍2
Signed 广告代发
Showing the 12 most recent of 749 posts we hold for @qingtPD. 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 — 582,565 of 1,629,403 entries 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.
@qingtPD named 9 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“晴天主频道” (@qingtPD), 22,927 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/qingtPD.
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.