Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7308145154
👍28😍1
Signed 极搜🔍资源搜索@JISOU

Channel
@wjhshsne
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
45,933subscribers
-1,714 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001454404574 |
|---|---|
| Type | Channel |
| Username | @wjhshsne |
| Description | 收集公益辅助、破解辅助、实用软件 广告无担保,请自行分辨。转发软件来自于网络,侵权请私聊联系我删除。 频道资源仅供学习研究使用/交流群 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/wjhshsne |
Software piracy — 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 94% 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 11 other registered channels. This entry also sits inside a group of 56 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 |
|---|---|---|---|
| @LMGWJWD6/399247 Aug 2026, 01:34 UTC | @wjhshsne/81448 · this entry7 Aug 2026, 01:34 UTC | 1.00 | under a minute |
| @wjhshsne/81950 · this entry12 Aug 2026, 15:28 UTC | @LMGWJWD6/4065712 Aug 2026, 15:29 UTC | 1.00 | under a minute |
| @LMGWJWD6/4188822 Aug 2026, 16:32 UTC | @wjhshsne/82619 · this entry22 Aug 2026, 16:32 UTC | 1.00 | under a minute |
| @LMGWJWD6/435289 Sept 2026, 23:20 UTC | @wjhshsne/82819 · this entry9 Sept 2026, 23:20 UTC | 1.00 | under a minute |
| @LMGWJWD6/4753319 Oct 2026, 09:47 UTC | @wjhshsne/85831 · this entry19 Oct 2026, 09:47 UTC | 1.00 | under a minute |
| @LMGWJWD6/4753919 Oct 2026, 09:47 UTC | @wjhshsne/85837 · this entry19 Oct 2026, 09:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @LMGWJWD6 | 334 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @LMGWJWD6 (252–82) |
| @HUIYIYYDS6 | 321 (8/8 hand-verifiable sample passed) | 1.00 | 4 minutes | @HUIYIYYDS6 (307–14) |
| @LMY1015 | 74 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @XiaoxueVkernel6 | 45 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (29–16) |
| @dddailik | 33 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @dddailik (18–15) |
| @Drabanl6 | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (8–4) |
| @BBTSNHNB1 | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @GTQNB003 | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–3) |
| @HeixuePD6 | 10 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | even |
| @REBAC8 | 20 (8/8 hand-verifiable sample passed) | 0.98 | 34 minutes | @REBAC8 (18–2) |
| @yannb6 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 33 hours | @yannb6 (5–0) |
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. 547 of the 562 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 659 comparable posts for this entry, running 5 August 2026 to 17 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 56 channels, the one whose matching posts we hold earliest is @LMGWJWD. 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, 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 56 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.
5 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 22:20 | 45,933 | -62 |
| 12 Nov 2026, 14:18 | 45,995 | -10 |
| 10 Nov 2026, 12:09 | 46,005 | -42 |
| 8 Nov 2026, 20:08 | 46,047 | -21 |
| 7 Nov 2026, 14:47 | 46,068 | +8 |
| 6 Nov 2026, 13:26 | 46,060 | -23 |
| 5 Nov 2026, 11:30 | 46,083 | -27 |
| 4 Nov 2026, 10:05 | 46,110 | -43 |
| 3 Nov 2026, 08:36 | 46,153 | -13 |
| 2 Nov 2026, 09:16 | 46,166 | +11 |
| 1 Nov 2026, 11:36 | 46,155 | -1 |
| 31 Oct 2026, 13:30 | 46,156 | +15 |
| 30 Oct 2026, 16:38 | 46,141 | -9 |
| 29 Oct 2026, 15:45 | 46,150 | -20 |
| 28 Oct 2026, 17:07 | 46,170 | +16 |
| 27 Oct 2026, 19:05 | 46,154 | +15 |
| 26 Oct 2026, 17:26 | 46,139 | -9 |
| 25 Oct 2026, 15:06 | 46,148 | +22 |
| 24 Oct 2026, 14:46 | 46,126 | -20 |
| 23 Oct 2026, 15:26 | 46,146 | first reading |
1,291 posts held, back to 5 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 255 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 292 of 293 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 1,291 (5 August 2026 – 17 November 2026) |
| Views total | 107,482 |
| Reactions total | 4,098 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 14:06 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. 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 56 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.
9,770 reactions across 989 posts, in 16 distinct kinds. The most used accounts for 97.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9,498 | 97.2% | |
| ❤ | 137 | 1.40% | |
| 🤬 | 42 | 0.43% | |
| 🔥 | 36 | 0.368% | |
| 🕊 | 17 | 0.174% | |
| 😡 | 12 | 0.123% | |
| 🤓 | 7 | 0.072% | |
| 🤡 | 7 | 0.072% | |
| 😍 | 6 | 0.061% | |
| 🤣 | 2 | 0.02% | |
| 🍌 | 1 | 0.01% | |
| 👌 | 1 | 0.01% | |
| 👎 | 1 | 0.01% | |
| 💩 | 1 | 0.01% | |
| 🤔 | 1 | 0.01% | |
| 🤮 | 1 | 0.01% |
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 996 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 9,770 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 24 August 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 0 of 293 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).
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7308145154
👍28😍1
Signed 极搜🔍资源搜索@JISOU
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍28😍1
Signed 全网收质量频道 @adggku
1.三角洲行动国服 (DFM: China) 2.三角洲行动国际 (DFM: Global) 3.三角洲行动台湾 (DFM: Taiwan) 4.暗区突围国服 (UAM: China) 5.暗区突围国际 (UAM: Global) 6.使命召唤国服 (CODM: China) 7.使命召唤国际 (CODM: Global) 8.使命召唤台湾 (CODM: Taiwan) 9.穿越火线国服 (CFM: China) 10.穿越火线国际 (CFM: Global) 11.迷你世界全服 (MiniPVE: All) 12.王者荣耀国际 (SGAME: Google) 13.萤火突击渠道 (YHTJ: China) 14.萤火突击国际 (Lost Light: Global) 15.英雄联盟手游 (LOLM : China) 16.英雄联盟手游 (LOLM : Gogbal) 17.无畏契约手游 (Valorant : China) …
👍7❤2
光头强公益频道: 高能英雄: 功能介绍: 1.齐全的绘制 2.四种自瞄算法 3.硬件断点与PTE断点追踪 4.稳定的内存功能 注意事项: 1.除了被提交不可能10年 2.注意游戏这游戏绿玩非常极端觉得你有一点点嫌疑就去官方提交 3.闪退是不兼容 和平美化: 美化界属于很不错的美化了建议娱乐使用别到时候封号怪着怪那,我只是要做大公益满足每个人需求你不需要可以不开很简单道理 更新内容: 1.修复全局部分情况没效果问题 2.修复锁帧没效果问题 3.修复大厅异常判断导致的误写入导致的闪退问题 此版本必须用最新版配置文件 否则无效果! 迷你枪战精英: 本次更新: 1.适配最新版本 2.更换开火开镜判断 注意事项: 1.自瞄或追踪没效果请游戏内或大厅执行 三角洲解密: -修复vivo/天机 -修复部分人解密失效问题 -优化自瞄逻辑 -优化绘制流畅度 -几乎适配全机型 解密方式:算法解密 Udp解密 模拟解密等 丝滑流畅支持vk opengl…
👍6
三角洲行动芊羽美化公益内核 芊羽三角洲美化1.0.0 全刀皮/枪械/干员美化 QianYuHome 使用教程:执行后进入三角洲即可 塔菲音效可在设置界面关闭 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #三角洲行动 #芊羽美化 #美化 #公益内核 #内核
👍7
和平精英LK全皮肤美化公益内核 和平精英LK公益全皮肤美化2.9.0 介绍说明:不修改任何文件实现全皮肤局内秒刷美化;安装失败的用MT管理器打开安装;不是pak文件不是sh文件;不需要修改任何文件。 更新日志:修复了部分bug;更新了大飞机美化;更新了广角;修复超体度假岛,没效果重进软件设置确认更新到最新版。 传世武器美化使用教程:悬浮窗设置选择好了之后随便拿个近战武器进局内就行,不要在局内切换那样没效果。 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #和平精英 #LK #全皮肤美化 #公益 #内核 #LK全皮肤美化
👍7
和平精英小夜T7引擎漏打公益内核 小夜破解.和平.T7引擎漏打(适配新赛季).zip 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #和平精英 #小夜 #T7引擎 #漏打 #内核 #小夜T7引擎漏打
👍7
和平精英美国范围Pro公益内核 和平精英美国范围内核Pro破解 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #和平精英 #美国范围Pro #内核 #辅助
👍7
和平精英/PUBG/三角洲行动方源公益内核 11月15 方源强锁+据点+无后 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #和平精英 #PUBG #三角洲行动 #方源 #内核 #强锁 #和平精英/PUBG/三角洲行动
👍7
无畏契约铭轩Nl瓦手防观察公益内核 NL无畏契约瓦手拦截,此版本专防瓦手。采用独家拦截【伪装/清理/防封】,可防【十年/行为/观察/高危】,可以搭配任何辅助使用,乱杀不观察,支持所有安卓root设备。采用最新内核级自研思路:零观察期,排位/匹配乱杀零记录,不进观察期;设备通杀,安卓ROOT全机型支持,黑碳设备也稳;自研过检测思路,不检测、不闪退、不读取内存;代练专用,上分/炸鱼/打单零风险,效率翻倍。 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #无畏契约 #铭轩Nl #瓦手防观察 #内核 #防封 #铭轩Nl瓦手防观察
👍7❤1
无畏契约手游灰灰裸奔公益内核 5.7 内透➕范围➕自瞄 范围自改大小为:大/中/小 已修复禁网 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #无畏契约手游 #灰灰裸奔 #内透 #自瞄 #范围 #内核
👍8
和平精英元未央地铁逃生公益内核 未央配置文件【通用版本】v3 支持:和平精英 PUBG(国际服 / 日韩服 / 台湾服 / 越南服) 安全-100%(小黑屋另算) 功能:一击必中,对所有怪物都有效,3-5发子弹即可击杀,100%命中率,仅适用于地铁逃生模式 安装:将文件夹移动到 android/data/你的游戏/ 并将文件粘贴进去替换。安装完成 ✓ 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月17日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #和平精英 #元未央 #地铁逃生 #配置文件 #公益 #内核
👍7
Showing the 12 most recent of 1,291 posts we hold for @wjhshsne. 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.
@wjhshsne 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 53 posts on @wjhshsne 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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“❤️公益辅助分享❤️” (@wjhshsne), 45,933 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/wjhshsne.
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.