三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 ✅栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd 有问题的手动下载不要覆盖安装
👍29❤1

Channel
@xiaobaidpd
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
15,729subscribers
-4,361 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004294335755 |
|---|---|
| Type | Channel |
| Usernames | @lmodfm @xiaobaidpd |
| Created | Between 1 May 2026 and 4 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/xiaobaidpd |
Gaming — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 4 other registered channels. This entry also sits inside a group of 68 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 |
|---|---|---|---|
| @xiaobaidpd/240 · this entry9 Oct 2026, 18:20 UTC | @enennba/1609 Oct 2026, 18:27 UTC | 1.00 | 7 minutes |
| @enennba/16110 Oct 2026, 19:48 UTC | @xiaobaidpd/241 · this entry10 Oct 2026, 19:48 UTC | 1.00 | under a minute |
| @enennba/16211 Oct 2026, 09:14 UTC | @xiaobaidpd/242 · this entry11 Oct 2026, 09:14 UTC | 1.00 | under a minute |
| @enennba/16514 Oct 2026, 09:07 UTC | @xiaobaidpd/245 · this entry14 Oct 2026, 09:07 UTC | 1.00 | under a minute |
| @appletzpd/27126 Oct 2026, 08:16 UTC | @xiaobaidpd/235 · this entry6 Oct 2026, 08:17 UTC | 1.00 | 72 seconds |
| @appletzpd/27147 Oct 2026, 17:11 UTC | @xiaobaidpd/236 · this entry7 Oct 2026, 17:12 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @enennba | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–1) |
| @appletzpd | 6 (6/6 hand-verifiable sample passed) | 1.00 | 2 minutes | @appletzpd (6–0) |
| @aizmzzx | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @aizmzzx (6–0) |
| @qingtPD | 6 (6/6 hand-verifiable sample passed) | 1.00 | 36 minutes | 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. 11 of the 11 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 28 comparable posts for this entry, running 4 August 2026 to 14 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 68 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 15 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 68 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.
17 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 12:01 | 15,729 | -60 |
| 10 Nov 2026, 11:59 | 15,789 | -53 |
| 8 Nov 2026, 23:38 | 15,842 | -50 |
| 7 Nov 2026, 13:18 | 15,892 | -35 |
| 6 Nov 2026, 14:48 | 15,927 | -41 |
| 5 Nov 2026, 16:48 | 15,968 | -11 |
| 4 Nov 2026, 19:08 | 15,979 | -43 |
| 3 Nov 2026, 18:07 | 16,022 | -53 |
| 2 Nov 2026, 16:16 | 16,075 | -18 |
| 1 Nov 2026, 18:20 | 16,093 | -64 |
| 31 Oct 2026, 16:06 | 16,157 | -29 |
| 30 Oct 2026, 13:26 | 16,186 | -38 |
| 29 Oct 2026, 13:57 | 16,224 | -23 |
| 28 Oct 2026, 12:59 | 16,247 | -13 |
| 27 Oct 2026, 16:31 | 16,260 | -22 |
| 26 Oct 2026, 12:36 | 16,282 | -53 |
| 25 Oct 2026, 09:04 | 16,335 | -39 |
| 24 Oct 2026, 09:36 | 16,374 | -21 |
| 23 Oct 2026, 11:44 | 16,395 | -28 |
| 22 Oct 2026, 11:15 | 16,423 | first reading |
46 posts held, back to 4 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 31 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 14 November 2026 |
|---|---|
| Posts held | 46 (4 August 2026 – 14 November 2026) |
| Views total | 4,826 |
| Reactions total | 59 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 19:07 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 15 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.
3,987 reactions across 46 posts, in 24 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🖕 | 2,125 | 53.3% | |
| 👍 | 857 | 21.5% | |
| ❤ | 450 | 11.3% | |
| 😡 | 279 | 7.00% | |
| 😭 | 108 | 2.71% | |
| 🍌 | 94 | 2.36% | |
| 🕊 | 10 | 0.251% | |
| 🤗 | 10 | 0.251% | |
| 🤷 | 9 | 0.226% | |
| 👌 | 6 | 0.15% | |
| 🙏 | 5 | 0.125% | |
| 🫡 | 5 | 0.125% | |
| 👏 | 4 | 0.1% | |
| 💯 | 4 | 0.1% | |
| 🤓 | 4 | 0.1% | |
| ☃ | 3 | 0.075% | |
| 🌭 | 3 | 0.075% | |
| ❤🔥 | 2 | 0.05% | |
| 👾 | 2 | 0.05% | |
| 💊 | 2 | 0.05% | |
| 4 further kinds | 5 | 0.125% |
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 46 of the 46 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,987 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 46 most recent posts we hold, published 4 August 2026 to 14 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: 0 of 4 posts held from the last 30 days (0%) 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).
三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 ✅栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd 有问题的手动下载不要覆盖安装
👍29❤1
三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 🎮栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd
👍15
🎮三角洲公益🎮暗区突围公益🎮无畏契约公益免root网页雷达3d全彩 纯网络路由读取坐标100%不封号无视行为1,3,7各种封号 3款游戏❤️🎮🎮全部通通公益免费,卡密都可以免费获取,不需要付一分钱,没有任何套路 手机端只需要安装一个加速器即可,不需要电脑,不需要开热点,不需要root权限,纯网络读取 支持🍎iOS全系列,安卓,鸿蒙全系统,只要你的设备可以正常联网即可(网络获取坐标),不需root权限,不需要电脑,不需要解bl,手机联网即可绘制 3d人物骨骼,2d平面地图,人物职业,武器手持,名字信息,血量状态,全部可以显示,效果堪比内核,并且比内核更加稳定 本地内核绘制全部信息都要在本地游戏内存里面读取,非常容易封号封一天或者三天,甚至十年,而我们所有坐标都是在网络中获取 ✅免root网页雷达公益更新通知频道: 👉@guitouwy 【领取公益卡密需要先加入频道】 ❤️🎮 点我获取免费卡密注册免root网页雷达
👍9❤1
『❤️公益三角洲/🎮公益暗区突围双游戏算法解密_Kernel_v1.3』 2026年10月20日 三角洲/暗区突围UDP解密,内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲/暗区突围公益UDP解密 🎮暗区突围更新内容 ✅加入T7绘制 ✅加入夜视仪绘制 ✅加入本地模型掩体,自己APP手动选择下载地图模型 ✅加入掩体变色,掩体自瞄,漏那打那 ✅加入自瞄开火开镜判断 ✅加入真人盒子,人机盒子判断 ✅加入忽略人机盒子 ❤️三角洲更新内容 ✅修复本地模型下载失败,已更换境外服务器 ✅修复千人千面加密部分用户失效 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月20日 ✨栖月 Kernel公益运营团队 🎮推荐一个朋友的三角洲暗区双游戏免root网页雷达项目:👉 https://t.me/gu…
👍4
三角洲🎮暗区突围🎮双游戏公益算法解密内核 共享网页雷达,共享队友使用 支持physx模型建筑物漏打 自瞄支持内核陀螺仪 超低占用,流畅高清绘图,三角洲暗区已解密游戏坐标加密 卡密随意输入,本程序公益使用,抵制倒卖 ! 程序完全公益,不收取任何费用 程序完全公益,不收取任何费用 ✅模型掩体判断 ✅陀螺仪自瞄 ✅单透模式 ✅Hook陀螺仪自瞄 采用最新新方案PhysX渲染模型 自瞄指哪打哪 丝滑跟人 🎮👉推荐一个朋友的三角洲手游软路由免root雷达项目【目前0封号】: @guitouwy 栖月公益内核通知频道: @yuenhpdd
👍9❤3🌚1
『❤️三角洲/🎮暗区突围双游戏公益算法解密_Kernel_v1.0』 2026年10月14日 三角洲/暗区突围UDP解密,内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲/暗区突围公益UDP解密 🎮三角洲更新内容: - 修复解密一解密二失效 - 适配最新千人千面加密 - 优化解密适配性 🐱三角洲/暗区突围目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 🎮推荐一个朋友的三角洲免root网页雷达项目:👉 https://t.me/guitouwy/50
👍13❤1
🎮『暗区突围公益算法解密_Kernel_v1.0』 2026年10月14日 暗区突围UDP解密,内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月暗区突围公益UDP解密 🦾更新内容: - 优化解密效率 - 优化程序启动速度 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh
👍2
❤️『栖月三角洲公益算法解密_Kernel_v1.9』 2026年10月12日 已更新三角洲最新UDP解密,纯内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲公益UDP解密 🦾更新内容: - 修复部分用户无法打开程序bug - 优化程序启动速度 - 已适配10.12日最新千人千面加密 -优化网页雷达共享传输效率,异地共享数据延迟降至30毫秒 😡网页雷达共享链接: http://114.66.40.26:12345 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh 👉三角洲免root网页3d雷达,…
👍15❤1
❤️『栖月三角洲公益算法解密_Kernel_v1.8』 2026年10月11日 已更新三角洲最新UDP解密,纯内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲公益UDP解密 🦾更新内容: - 修复部分用户解密失效 - 修复部分用户密钥获取失败,解决解密1,解密2失效 - 已适配10.11日最新千人千面加密 -优化网页雷达共享传输效率,异地共享数据延迟降至30毫秒 ✅网页雷达共享链接: http://114.66.40.26:12345 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh 👉三角洲免…
👍23❤1
❤️『三角洲公益算法解密_Kernel_v1.7』 2026年10月11日 已更新三角洲最新UDP解密,纯内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲公益UDP解密 🦾更新内容: - 修复最新千人千面加密 - 修复密钥获取失败,解决解密1,解密2失效 - 部分仍解密失败的重启一下辅助跟游戏在尝试 ✅网页雷达共享链接: http://114.66.40.26:12345 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh 🎮三角洲免root网页3d雷达,非传统内核共享,仅需一个加速器即可,读取…
👍8❤1
❤️『栖月三角洲公益算法解密_Kernel_v1.6』 已更新三角洲最新UDP解密,纯内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲公益UDP解密 🦾更新内容: - 修复最新千人千面加密 - 加入敌人盒子开启状态显示 - 加入敌人盒子已开启忽略功能 - 加入高价值物资列表显示功能,位置调整,大小调节 ✅网页雷达共享链接: http://114.66.40.26:12345 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月10日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh
👍8
❤️『栖月_Kernel_v1.5』 已更新三角洲最新UDP解密,纯内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲公益UDP解密 🦾更新内容: - 新增网页雷达共享 - 网页人物共享,物资共享 -使用方法:内核悬浮窗开启雷达共享,生成房间号,朋友访问雷达链接输入房间号访问即可 ✅网页雷达共享链接: http://114.66.40.26:12345 🎮目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force🥰 ✨更新时间:2026年10月8日 ✨栖月 Kernel运营团队 不禁言交流群: https://t.me/qiyuenh
👍21❤1
Showing the 12 most recent of 46 posts we hold for @xiaobaidpd. 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.
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 16 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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“三角洲和平公益项目推荐” (@xiaobaidpd), 15,729 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/xiaobaidpd.
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.