你们好 很抱歉 我的频道被人骗走了 今天正式回归,我将在今天晚上12点更新最强公益 注:只有加入频道才能获得 我的新频道: https://t.me/+RHS1HkYv-qU4YjY1
👍61
Signed 全网收质量频道 @adggku
![Telegram profile photo for 浪漫内核分享频道[公益破解][软件分享][免费代理]](https://cdn.tgregister.com/av/66/668a7deb568c1aa8b5923362b3bf9add7896a47837780e24b3e4d7dfe65bcca6.jpg)
Channel
@LMGWJWD6
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 · Handles named that no longer answer · Cite this entry
44,343subscribers
+10,576 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002283106558 |
|---|---|
| Type | Channel |
| Username | @LMGWJWD6 |
| Description | 每日分享各种破解软件.游戏辅助.免费代理等等 Dear channel member: This channel strictly complies with the Telegram community guidelines and related laws and regulations, and all content has been strictly reviewed to ensure compliance and legality. ⚠ If you have any quest |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/LMGWJWD6 |
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 99% 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 54 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/39924 · this entry7 Aug 2026, 01:34 UTC | @wjhshsne/814487 Aug 2026, 01:34 UTC | 1.00 | under a minute |
| @wjhshsne/8195012 Aug 2026, 15:28 UTC | @LMGWJWD6/40657 · this entry12 Aug 2026, 15:29 UTC | 1.00 | under a minute |
| @LMGWJWD6/41888 · this entry22 Aug 2026, 16:32 UTC | @wjhshsne/8261922 Aug 2026, 16:32 UTC | 1.00 | under a minute |
| @LMGWJWD6/43528 · this entry9 Sept 2026, 23:20 UTC | @wjhshsne/828199 Sept 2026, 23:20 UTC | 1.00 | under a minute |
| @LMGWJWD6/47533 · this entry19 Oct 2026, 09:47 UTC | @wjhshsne/8583119 Oct 2026, 09:47 UTC | 1.00 | under a minute |
| @LMGWJWD6/47539 · this entry19 Oct 2026, 09:47 UTC | @wjhshsne/8583719 Oct 2026, 09:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @wjhshsne | 326 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (250–76) |
| @HUIYIYYDS6 | 323 (8/8 hand-verifiable sample passed) | 1.00 | 3 minutes | @HUIYIYYDS6 (305–18) |
| @LMY1015 | 85 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (70–15) |
| @XiaoxueVkernel6 | 74 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @yannb6 | 17 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | @yannb6 (17–0) |
| @Drabanl6 | 30 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (16–14) |
| @GTQNB003 | 30 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (21–9) |
| @BBTSNHNB1 | 31 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @BBTSNHNB1 (16–15) |
| @qwgwj666 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 45 hours | @qwgwj666 (7–0) |
| @SNGF666888 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 34 hours | @SNGF666888 (7–0) |
| @NL666NB | 7 (7/7 hand-verifiable sample passed) | 1.00 | 45 hours | @NL666NB (7–0) |
| @lianbingnb | 7 (7/7 hand-verifiable sample passed) | 1.00 | 11 minutes | this entry (7–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. 418 of the 426 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 825 comparable posts for this entry, running 5 August 2026 to 12 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 54 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 · clone_source, last confirmed 13 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 54 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.
3 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 06:00 | 44,343 | -37 |
| 8 Nov 2026, 14:51 | 44,380 | -22 |
| 7 Nov 2026, 07:07 | 44,402 | +21 |
| 6 Nov 2026, 06:39 | 44,381 | -3 |
| 5 Nov 2026, 06:55 | 44,384 | +75 |
| 4 Nov 2026, 05:06 | 44,309 | +2 |
| 3 Nov 2026, 03:49 | 44,307 | +94 |
| 2 Nov 2026, 02:46 | 44,213 | +333 |
| 1 Nov 2026, 02:54 | 43,880 | +157 |
| 31 Oct 2026, 04:18 | 43,723 | +115 |
| 30 Oct 2026, 07:46 | 43,608 | -2 |
| 29 Oct 2026, 10:46 | 43,610 | -8 |
| 28 Oct 2026, 09:39 | 43,618 | +92 |
| 27 Oct 2026, 07:59 | 43,526 | +62 |
| 26 Oct 2026, 07:51 | 43,464 | +1 |
| 25 Oct 2026, 06:47 | 43,463 | +49 |
| 24 Oct 2026, 09:37 | 43,414 | +30 |
| 23 Oct 2026, 09:29 | 43,384 | +13 |
| 22 Oct 2026, 06:01 | 43,371 | +58 |
| 21 Oct 2026, 00:18 | 43,313 | first reading |
1,283 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 236 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 13 November 2026 |
|---|---|
| Posts held | 1,283 (5 August 2026 – 13 November 2026) |
| Views total | 94,234 |
| Reactions total | 6,740 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 14:15 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 13 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 48 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.
15,469 reactions across 990 posts, in 7 distinct kinds. The most used accounts for 98.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15,176 | 98.1% | |
| ❤ | 265 | 1.71% | |
| 🥰 | 11 | 0.071% | |
| 👏 | 7 | 0.045% | |
| 🎉 | 4 | 0.026% | |
| 🔥 | 3 | 0.019% | |
| 😁 | 3 | 0.019% |
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 995 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 15,469 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 20 August 2026 to 13 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 20 August 2026 to 13 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: 3 of 255 posts held from the last 30 days (1.18%) 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).
你们好 很抱歉 我的频道被人骗走了 今天正式回归,我将在今天晚上12点更新最强公益 注:只有加入频道才能获得 我的新频道: https://t.me/+RHS1HkYv-qU4YjY1
👍61
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) C…
👍68
使命召唤手游大杂烩公益内核 适配国服/国际/台湾解密 卡密 ANQUY3D8C1C9852220C6BE97827FC045 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #使命召唤手游 #CODM #大杂烩 #内核 #解密
👍47❤1
PUBG黑崎小夜公益内核 PUBG 4.7 硬件断点内核 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #PUBG #黑崎小夜 #硬件断点 #内核 #公益
👍47❤1
三角洲行动温暖解密公益内核 【三角洲行动辅助 · 更新公告】 版本:v2.0 日期:2026-11-13 更新内容: - 已适配最新三角洲S12赛季 - 适配程序所有功能 - 适配新赛季算法解密功能 - 解决新赛季迷雾加密 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #三角洲行动 #温暖 #解密 #辅助 #公益 #内核 #温暖解密
👍46❤1
PUBG Mobile夜神月公益内核 夜神月更新PUBGM4.7最新版本,仅支持日韩,后续再更新其他。公益卡密key:夜神月公益卡密 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #PUBGM #夜神月 #公益内核 #日韩 #PUBGMobile #内核
👍48❤1
三角洲行动Like公益内核 Like_4.1版本[三角洲]更新通知 更新内容: - 解决10.12号新加密 - 服务器迁移 做到零延迟 - 修复解密1 UDP解密 - 修复解密2 模拟算法解密 - 修复解密3 断点UDP - 适配vivo iqoo -无视迷雾系统 纯模拟解密 -解密三独家断点只需要0.3s的断点 比外面的垃圾断点稳定 可稳定奔放 解密三必须刷入par驱动 对接par/时间/TWT驱动 自瞄漏打必须解压文件 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #三角洲行动 #Like #公益内核 #驱动 #解密 #内核
👍49❤1
无畏契约单透公益内核 🔗 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:11月13日更新 https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 #无畏契约 #单透 #源码 #透视 #内核
👍49❤1
【超级会员V3】通过百度网盘分享的文件:各种辅助分享 链接:https://pan.baidu.com/s/1NvMzBhL3kb_wzWj7WO1heA?pwd=6666 复制这段内容打开「百度网盘APP 即可获取」
👍52❤1
葫芦娃10.8版本 更新和平新版本数据 适配PUBG新赛季 有bug反馈评论区 葫芦娃公益频道: @HLWNHNB2 网盘更新下载: https://pan.baidu.com/s/11pxYvr9c5_ERtJuoCE_41Q?pwd=6666 葫芦娃频道点我加入 葫芦娃交流群 @PUBGMAMTLS 支持的可以去网盘下载了谢谢各位义父了❤️ 保存文件 然后再下载 以免出错❤️ #和平精英 #无畏契约 #pubg #内核 #三角洲
👍68❤1
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍22
Signed 全网收质量频道 @adggku
大肥鱼2.5三角洲公益算法解密 11.13最新更新解密 下载地址 📥📥📥📥📥📥📥📥📥📥 https://pan.quark.cn/s/6061a5d18530 更新日志 更新适配新算法解密 适配最新par驱动 优化辅助卡顿 ✈️大肥鱼新手/老手不会使用的点我查看视频和文字教程 公益卡密: 联系机器人获取 @bbblajibot ❗️❗️➡️ 点我加入官方频道 ❗️❗️➡️ 点我加入官方群组
👍35
Showing the 12 most recent of 1,283 posts we hold for @LMGWJWD6. 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.
@LMGWJWD6 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 @LMGWJWD6 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.
Named by 18 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.
@LMGWJWD6 named 6 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“浪漫内核分享频道[公益破解][软件分享][免费代理]” (@LMGWJWD6), 44,343 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/LMGWJWD6.
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.