🌟三角洲DL公益算法解密注入写法 ❤️DL最新版本:11月15日 V1.0.0版本 DL功能介绍: 😳适配全部机型: 只要手机root了就能使用 🥵自研AI自瞄算法: 稳定使用无需搭配任何端口 🤯独家算法解密思路: ✅不闪框 ✅不卡框 ✅不遁地 ▎📣公益卡密(点击自动复制): @DLerend ▎📸点我查看视频教程 (必须看完) ▎✈️加入官方频道: @DLerend ▎✈️加入交流群组 ✈️问题反馈点我
👍47❤1

Channel
@HeiXuePD
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
65,155subscribers
+12,522 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002374654856 |
|---|---|
| Type | Channel |
| Username | @HeiXuePD |
| Description | 黑雪唯一频道 频道主 广告联系:@kkkkwwaw123 小雪频道 @XiaoxuePD 纯聊天频道无广告 有内核文件 也会转载文件 官方更新网盘 https://drive.uc.cn/s/8ee2bdeb55e74?public=1 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/HeiXuePD |
Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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 |
|---|---|---|---|
| @HeiXuePD/28195 · this entry23 Sept 2026, 22:41 UTC | @LinYuKernel/6688124 Sept 2026, 09:31 UTC | 1.00 | 11 hours |
| @LinYuKernel/782684 Nov 2026, 13:13 UTC | @HeiXuePD/34167 · this entry4 Nov 2026, 13:13 UTC | 1.00 | under a minute |
| @HeiXuePD/21835 · this entry15 Aug 2026, 18:51 UTC | @time_pd/872817 Aug 2026, 02:27 UTC | 1.00 | 32 hours |
| @HeiXuePD/27227 · this entry18 Sept 2026, 13:23 UTC | @Cycle1337/1172818 Sept 2026, 13:23 UTC | 1.00 | under a minute |
| @HeiXuePD/27394 · this entry19 Sept 2026, 15:05 UTC | @Cycle1337/1178219 Sept 2026, 15:05 UTC | 1.00 | under a minute |
| @Cycle1337/126607 Oct 2026, 18:35 UTC | @HeiXuePD/31426 · this entry8 Oct 2026, 04:24 UTC | 1.00 | 9.8 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @LinYuKernel | 174 (8/8 hand-verifiable sample passed) | 1.00 | 4.4 hours | this entry (102–72) |
| @time_pd | 82 (7/8 hand-verifiable sample passed) | 1.00 | 4.0 hours | this entry (57–25) |
| @TwT_driver | 124 (7/8 hand-verifiable sample passed) | 1.00 | 2.6 hours | this entry (82–42) |
| @Cycle1337 | 65 (7/8 hand-verifiable sample passed) | 1.00 | 2.2 hours | @Cycle1337 (41–24) |
| @DUOLEA66 | 17 (8/8 hand-verifiable sample passed) | 0.98 | 6.1 hours | this entry (15–2) |
| @XiaoxuePD | 25 (8/8 hand-verifiable sample passed) | 0.97 | under a minute | this entry (22–3) |
| @Drabanb | 57 (8/8 hand-verifiable sample passed) | 1.00 | 3.7 hours | this entry (42–15) |
| @yuyannb666 | 30 (8/8 hand-verifiable sample passed) | 1.00 | 3.4 hours | this entry (24–6) |
| @pj7645 | 19 (8/8 hand-verifiable sample passed) | 1.00 | 3.1 hours | @pj7645 (12–7) |
| @OXKernelPD | 14 (8/8 hand-verifiable sample passed) | 1.00 | 72 minutes | this entry (10–4) |
| @qingtPD | 81 (8/8 hand-verifiable sample passed) | 1.00 | 4.3 hours | this entry (45–36) |
| @ZEROPD | 18 (8/8 hand-verifiable sample passed) | 1.00 | 5.2 hours | @ZEROPD (10–8) |
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. 113 of the 113 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 2,314 comparable posts for this entry, running 7 August 2026 to 16 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 17 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 |
|---|---|---|
| 14 Nov 2026, 00:59 | 65,155 | +1,384 |
| 11 Nov 2026, 03:48 | 63,771 | +506 |
| 9 Nov 2026, 10:37 | 63,265 | +352 |
| 7 Nov 2026, 23:51 | 62,913 | +299 |
| 6 Nov 2026, 20:29 | 62,614 | +472 |
| 5 Nov 2026, 16:46 | 62,142 | +404 |
| 4 Nov 2026, 18:50 | 61,738 | +104 |
| 3 Nov 2026, 18:41 | 61,634 | +166 |
| 2 Nov 2026, 21:25 | 61,468 | +146 |
| 1 Nov 2026, 22:54 | 61,322 | +329 |
| 31 Oct 2026, 23:40 | 60,993 | +193 |
| 31 Oct 2026, 01:57 | 60,800 | +110 |
| 30 Oct 2026, 01:10 | 60,690 | +163 |
| 29 Oct 2026, 00:10 | 60,527 | +98 |
| 27 Oct 2026, 23:06 | 60,429 | +213 |
| 26 Oct 2026, 21:27 | 60,216 | +134 |
| 25 Oct 2026, 18:09 | 60,082 | +304 |
| 24 Oct 2026, 18:49 | 59,778 | +212 |
| 23 Oct 2026, 18:21 | 59,566 | +155 |
| 22 Oct 2026, 16:19 | 59,411 | first reading |
2,988 posts held, back to 7 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 253 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.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 2,988 (7 August 2026 – 17 November 2026) |
| Views total | 254,974 |
| Reactions total | 52,633 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 07:20 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 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.
Measured directly from 88 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.
53,679 reactions across 957 posts, in 20 distinct kinds. The most used accounts for 98.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 52,617 | 98.0% | |
| ❤ | 551 | 1.03% | |
| 🤬 | 210 | 0.391% | |
| 🔥 | 60 | 0.112% | |
| 😭 | 50 | 0.093% | |
| 😡 | 46 | 0.086% | |
| 💩 | 44 | 0.082% | |
| 🖕 | 37 | 0.069% | |
| 👏 | 17 | 0.032% | |
| 🙉 | 10 | 0.019% | |
| 😁 | 8 | 0.015% | |
| 🥰 | 8 | 0.015% | |
| 🕊 | 6 | 0.011% | |
| 👎 | 3 | 0.006% | |
| 😘 | 3 | 0.006% | |
| 🤮 | 3 | 0.006% | |
| 🤣 | 2 | 0.004% | |
| 🤩 | 2 | 0.004% | |
| 🤡 | 1 | 0.002% | |
| 🤯 | 1 | 0.002% |
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 961 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 53,679 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 17 October 2026 to 17 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: 10 of 977 posts held from the last 30 days (1.02%) 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).
🌟三角洲DL公益算法解密注入写法 ❤️DL最新版本:11月15日 V1.0.0版本 DL功能介绍: 😳适配全部机型: 只要手机root了就能使用 🥵自研AI自瞄算法: 稳定使用无需搭配任何端口 🤯独家算法解密思路: ✅不闪框 ✅不卡框 ✅不遁地 ▎📣公益卡密(点击自动复制): @DLerend ▎📸点我查看视频教程 (必须看完) ▎✈️加入官方频道: @DLerend ▎✈️加入交流群组 ✈️问题反馈点我
👍47❤1
⭐三角洲国服—护航仔⭐ ✅购买地址 频道下载 解绑地址 ✅网盘下载地址 ✅算法解密/独家思路/独家驱动 ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:5.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:国服 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢大地图雷达/小地图雷达 🟢全图模型漏打/掩体变色 ✅自瞄配置:陀螺仪自瞄+触摸自瞄 🌟🙃🌟➡️ @SJZcq 😃😃😃😃 @CQ_669
👍52❤1
Signed 春 秋(直奔主题)
开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? 😃😀😃小意全游戏数据号⚠️⚠️⚠️ 😃😃最低价数据号货源 账号包含🎮🎮🎮🎮🎮🎮 卡网成交6000➕1314保证金🥰 【⚠️黑奴客服人工验号上架😀】 【⚠️保证不二卖不圈钱不跑路】 🤩100%都是高质量皮肤套装 🤩包冻结/鉴别/人脸/封号/黑屋/二级密码问题 只要是账号问题都售后☑️ 😃😃😃😃 @xiaoyisjh 下单🥰http://shop.918fk.cn/shop/xiao http://shop.918fk.cn/shop/xiao http://shop.918fk.cn/shop/xiao ❗️❗️ @xiaoyishujuhao (查看反馈和每天送号) 🖥上号器➕公益清理:https://xysj.lanzoub.com/qqqyy…
👍51❤1
Signed 小 白
😀今天我整合了挂圈各大热门频道! 以下频道是挂圈热门频道大合集 库洛米公益内核频道 狗头公益破解内核频道 enen内核频道 林羽内核频道 zero驱动频道 时间驱动频道 twt驱动频道 paradise驱动频道 小雪内核频道 光头强工艺内核频道 雪花工艺内核频道 TP工艺内核频道 葫芦娃工艺频道
👍50❤1
三角洲Jk内部 已适配新赛季 无视偏漏,无视加密,无视破解 专供俱乐部 长期合作 素材来自 萌萌猫 全程无剪辑,精彩击杀集锦 使用机型 y700四代 欢迎俱乐部长期对接合作 不偏不漏,有能力长期更新,解决问题(🈲跑路🈲改名⭕️米) 开卡售后合作咨询客服 @ask1525 点击加入JK官方通知频道 点击加入JK官方通知频道 点击加入JK官方通知频道
👍41❤1
Signed 推广 AI
❗️❗️❗️❗️❗️❗️❗️ 【网易云漏打追锁】 🎮【网易云】云更新至1.1.7版本 ⚡️适配最新S12赛季 ✨网易云运营团队 ✨更新时间:2026年11月14日 🚨限时公益卡密: @UJM6688 🚨限时公益卡密: @UJM6688 ❤️ 支持设备:安卓 ROOT ❤️ 支持内核:4.x - 6.x 全系 ❤️支持天机/骁龙 处理器 ❤️支持区服:国服 ❤️支持模式:内核/纯c 功能说明🎚 ✅方框 ✅骨骼 ✅干员 ✅血量 ✅距离 ✅手持 ✅头甲 ✅物资 🟢全图模型漏打 🟢战斗模式 🟢添加独立大小雷达 🟢Physx/本地模型 支持全地图模型 ✅自瞄配置:陀螺仪自瞄+内核触摸 ✅网页雷达: 2D/3D雷达 👉网盘下载 👉解绑地址 ━━━━━━━━━━━━━━━━ 🟢网易云详细介绍 ━━━━━━━━━━━━━━━━ 👉疑难杂症解决 👉网易云相关问题答疑解惑 ━━━━━━━━━━━━━━ ❗️❗️ 点我进入官方…
👍50💩1
Signed UU推广号【私下收款都是骗子】
三角洲EO公益解密1.1版本 11月17日最新更新 采用模拟/udp解密(目前市面上都是这个解密收费公益也是) 解密已适配99%的机型 驱动对接:eo驱动 时间驱动 par驱动 下载地址 https://pan.quark.cn/s/01d5154f6c6e 公益解密卡密: @EO66789 更新日志 更新适配三角洲最新加密 更新算法解密 优化辅助 自瞄配置点我查看 ❗️❗️➡️ @EO66789 ❗️❗️➡️ @EO66669
👍52❤1
小新三角洲公益端口 😙😍😗😋😝🙃😜🤨😜 📣更新公告: 更新修复聚框/封号问题 🔥公益卡密: @xiaoxindknb ✅无视 加密/聚框 问题 ✅无视网络波动等问题 😀企鹅交流群: 676715796 🩵小新端口客服: @lliul666 🩵官方频道: https://t.me/xiaoxindknb https://t.me/xiaoxindknb https://t.me/xiaoxindknb
👍51
Signed 有事直说!
星瑶三角洲已攻克动态下发机制、全迷雾渲染限制,全程不动任何内存, ✅绘制模块:骨骼、方框、距离、血量、头甲、角色标识可视化 ✅自瞄模块:陀螺仪适配、内核触摸自瞄 ✅物资绘制:多类型物资精细化分类渲染 不走内存篡改路子,新版本适配省心,迷雾遮挡直接破除 卡网:http://aceyun.cn/shop/xingyao007 官方频道点我进入 📱纸飞机账号 优质账号 价格实惠📱 📱多国家任选📱 📱多种类型,老号权重高📱 📡现货充足,支持挑选🧩 🐈价格合适,质量优质📱 📱破解版tg包,可注册+86📱 💩永久VIP破解版VPN加速器🖕 🔝🔝🔝优质帐号选星瑶😵👉
👍47❤1
Signed 星瑶
大肥鱼3.0三角洲公益算法/udp解密 11.16最新更新解密 下载地址 📥📥📥📥📥📥📥📥📥📥 https://pan.quark.cn/s/6061a5d18530 更新日志 适配三角洲最新解密 优化辅助性能 优化新解密 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 公益卡密: 联系机器人获取 @bbblajibot ❗️❗️➡️ 点我加入官方频道 ❗️❗️➡️ 点我加入官方群组 收费解密都不一定有我这个好,长期稳定更新公益解密辅助
👍48
三角洲公益De解密+网页雷达 更新11.16版本,解决加密问题 算法解密+网页共享雷达二合一 可共享给队友 功能:算法解密/自瞄/掩体变色/防录屏/网页雷达/支持烽火/大战场 🌟【点我下载De公益解密】 📱 【全网货源批卡点我】 👉【内部稳大号科技点我】👈 😣大量收广告管理位:@GGX654bot
👍51
Signed 有 点
小新三角洲公益端口 😙😍😗😋😝🙃😜🤨😜 📣更新公告: 更新修复聚框/封号问题 🔥公益卡密: @xiaoxindknb ✅无视 加密/聚框 问题 ✅无视网络波动等问题 😀企鹅交流群: 676715796 🩵小新端口客服: @lliul666 🩵官方频道: https://t.me/xiaoxindknb https://t.me/xiaoxindknb https://t.me/xiaoxindknb
👍44
Signed 有事直说!
Showing the 12 most recent of 2,988 posts we hold for @HeiXuePD. 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.
@HeiXuePD edited 1 post 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 47 posts on @HeiXuePD 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.
Republishes 87 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 5 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.
@HeiXuePD named 23 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“黑雪主频道” (@HeiXuePD), 65,155 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/HeiXuePD.
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.