😀😀😀😀😀😃😀😀 💫💫点击进入。开启时来运转财富之旅 公群201加拿大pc28🈵赔 0/27😁😁😁😁倍 😀😀😁😆每日置顶红包特殊奖励数字8。顺子。豹子等流水累计活动 公群757加拿大pc2.0💍4/2/4.6💍时时流水领取。还有亏损转运包 置顶红包特殊奖励数字8。顺子。豹子等奖励 💍💍时来运转。一切皆有可能 💍💍熬过低谷。0/27终会相遇 💍💍梭哈才是艺术。赢钱才是王道 💍时来运转国际娱乐城💍开启你的财富好运之旅
❤1👍1
Signed 群管@FLL0

Channel
@DFHSTYLT
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 · Telegram's recommendations · Cite this entry
53,178subscribers
-1,025 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001699178426 |
|---|---|
| Type | Channel |
| Username | @DFHSTYLT |
| Description | 本频道提供各种免费资源,飞机代理,TG下载链接,语言包 。 @FLL8 法拉利担保 @FLLMU 法拉利USDT交易 @FLLDFH 法拉利东方汇 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/DFHSTYLT |
Gambling & betting — 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 100% 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. 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 |
|---|---|---|---|
| @diaosile99/186387 Aug 2026, 12:54 UTC | @DFHSTYLT/18106 · this entry7 Aug 2026, 12:54 UTC | 1.00 | under a minute |
| @diaosile99/186407 Aug 2026, 13:21 UTC | @DFHSTYLT/18108 · this entry7 Aug 2026, 13:21 UTC | 1.00 | under a minute |
| @diaosile99/186427 Aug 2026, 13:42 UTC | @DFHSTYLT/18110 · this entry7 Aug 2026, 13:42 UTC | 1.00 | under a minute |
| @diaosile99/186447 Aug 2026, 15:01 UTC | @DFHSTYLT/18111 · this entry7 Aug 2026, 15:01 UTC | 1.00 | under a minute |
| @diaosile99/186747 Aug 2026, 16:44 UTC | @DFHSTYLT/18115 · this entry7 Aug 2026, 16:44 UTC | 1.00 | under a minute |
| @DFHSTYLT/18088 · this entry6 Aug 2026, 16:51 UTC | @diaosile99/186857 Aug 2026, 18:34 UTC | 1.00 | 26 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @diaosile99 | 15 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | this entry (15–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 32 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 2, the earliest publisher we hold is @DFHSTYLT — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 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 1 other registered channel, 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 |
|---|---|---|
| 27 Sept 2026, 03:19 | 53,178 | -323 |
| 17 Sept 2026, 12:36 | 53,501 | -23 |
| 15 Sept 2026, 10:17 | 53,524 | +18 |
| 13 Sept 2026, 17:58 | 53,506 | -42 |
| 11 Sept 2026, 20:38 | 53,548 | -71 |
| 9 Sept 2026, 09:39 | 53,619 | -64 |
| 6 Sept 2026, 00:18 | 53,683 | -71 |
| 3 Sept 2026, 19:36 | 53,754 | -27 |
| 2 Sept 2026, 11:26 | 53,781 | -19 |
| 1 Sept 2026, 11:33 | 53,800 | -19 |
| 31 Aug 2026, 13:19 | 53,819 | -27 |
| 30 Aug 2026, 10:13 | 53,846 | -15 |
| 29 Aug 2026, 13:25 | 53,861 | -19 |
| 28 Aug 2026, 11:57 | 53,880 | -22 |
| 27 Aug 2026, 08:45 | 53,902 | -20 |
| 26 Aug 2026, 06:35 | 53,922 | -37 |
| 25 Aug 2026, 04:27 | 53,959 | -31 |
| 24 Aug 2026, 01:34 | 53,990 | -58 |
| 22 Aug 2026, 11:36 | 54,048 | -31 |
| 21 Aug 2026, 01:24 | 54,079 | first reading |
1,337 posts held, back to 20 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 105 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 649 of 779 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 1,337 (20 November 2025 – 27 September 2026) |
| Views total | 211,747 |
| Reactions total | 1,553 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 05: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 27 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 3 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.
1,951 reactions across 839 posts, in 6 distinct kinds. The most used accounts for 87.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,714 | 87.9% | |
| ❤ | 210 | 10.8% | |
| 🥰 | 15 | 0.769% | |
| 😍 | 10 | 0.513% | |
| 👎 | 1 | 0.051% | |
| 😁 | 1 | 0.051% |
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 844 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 1,951 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 19 August 2026 to 27 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.
😀😀😀😀😀😃😀😀 💫💫点击进入。开启时来运转财富之旅 公群201加拿大pc28🈵赔 0/27😁😁😁😁倍 😀😀😁😆每日置顶红包特殊奖励数字8。顺子。豹子等流水累计活动 公群757加拿大pc2.0💍4/2/4.6💍时时流水领取。还有亏损转运包 置顶红包特殊奖励数字8。顺子。豹子等奖励 💍💍时来运转。一切皆有可能 💍💍熬过低谷。0/27终会相遇 💍💍梭哈才是艺术。赢钱才是王道 💍时来运转国际娱乐城💍开启你的财富好运之旅
❤1👍1
Signed 群管@FLL0
诚信白资收U,全国送现,江苏宿迁周边10W起,支持U还支付宝,微信,银行卡转账,现金存款,为广大法拉利用户提供U换R便捷渠道,本群承诺所出资金一律白资,遇司法退一赔三! 公群链接:https://t.me/+DyKuYWxgV1plMWQ0
👍2
Signed 群管@FLL0
😀😀⚡️😀😀⚡️😀😀⚡️⚡️ 熊猫公群红包 :https://t.me/feivip888/17823240 熊猫899🈵赔扫雷 : t.me/feivip888 熊猫 866🈵赔扫雷 : https://t.me/+ZYGsvaeKGwo2Yjc8 💎公群006 . 熊猫🈵赔扫雷 https://t.me/+ehrz6mpvuSo0MGU0
👍4
Signed 群管@FLL0
😀全部采用官方骰子表情开奖 公平 公正 公开 😀没有任何套路 邀您尽享游戏乐趣 欢迎各位老板前来爆庄提款 😃公群992蛋仔🈵 赔扫雷 😃公群092·蛋仔·扫雷1:1 🈵赔 😃公群084·蛋仔高福利快三 公群红包:https://t.me/c/2698092330/4422290 快三公群链接 :https://t.me/+li9f68eOfhgzYmJk 以下是快三晋级 ✨ 1️⃣ - 累计2万U流水 奖励188U 2️⃣ - 累计10万U流水 奖励588U 3️⃣ - 累计50万U流水 奖励2888U 4️⃣ - 累计100万U流水 奖励5888U 🍀本活动叠加领取奖励,直到领取最高级 ‼️注:流水可累计,达标24点发放! 🔖VIP周奖励 : 等级 周流水 奖励 1️⃣ ≥5000U 58U 💰 2️⃣ ≥10000U 138U 💰 3️⃣ ≥5000…
Signed 群管@FLL0
余额:30万U @xiaoma 小马娱乐 😃 小马快3 122公群: https://t.me/+tYb0pmHgBQo1ZWMx 😀 小马牛牛120公群: https://t.me/+Pv9N33eR5dM0NzVl 😀 小马扫雷129公群: https://t.me/+SCn5HCeUhqwxNWZl 业务:🏅全网最火爆的骰子游戏公群,快3,牛牛,扫雷,全部采用telegram👤官方骰子表情开奖,公平公正,😃福利来担保上押☺️
👍2
Signed 群管@FLL0
🟢钱多多刁哈哈 高反水快3活动/限红2万U 🔖🔖 🎉🎉高反流水奖励:💧💧💧 1️⃣-2️⃣0️⃣0️⃣0️⃣0️⃣ 大小单双1.95倍 全部流水2️⃣.3️⃣% 无阶梯群内反水自动反到账户 🔖实力硬碰硬🔖 赢就三骰子 🎲🎲🎲 敢闯就上前 ‼️无任何福利 公平对战‼️ 📣 钱多多客服: @Qianduoduo1789 📣 本群业务员: @Qianyw 🛡钱多多唯一负责人 @QianDuoDuoVip ❌本群客服/业务员/不涉及私下交易,被骗概不负责! 🔖钱多多旗下游戏公群链接: ✔公群789 钱多多 快3 高反水赔付💧 ✔公群868 钱多多1:1🈵赔扫雷 ✔公群689 钱多多加拿大pc2.0🈵赔🇨🇦 ✔️公群026 钱多多加拿大pc2.8🈵赔🇨🇦 【⚠️因活动存在套利空间,同期出现对压等一切套利行为,不管是不是一人多个号,还是不同人对压,都有权取消活…
👍3
Signed 群管@FLL0
😃福利来手摇牛牛,同点不杀 ⬇️⬇️⬇️ 公群157.牛蛙哇手摇牛牛🐮 日亏损反5% 日流水活动 累积流水活动
👍4
Signed 群管@FLL0
🥇鼎峰娱乐 🥇PC2.84🈵倍 😃鼎峰娱乐PC2.8 801已押6000U ✅中秋活动进行中 大奖128U天天送 ✅『卷到无边』循环拿奖赢也送,输也送 💖单日318u流水🎁: 2⃣8⃣8⃣🔤➡1⃣2️⃣8⃣🧧 💖单日999u流水🎁: 6️⃣6️⃣6️⃣🔤➡1⃣2️⃣8⃣🧧 💖单日5000u流水🎁: 1⃣2⃣8⃣8⃣🔤➡1⃣2️⃣8⃣🧧 😃鼎峰娱乐PC2.8 708已押6999U ✅组合全网最高赔率6.79/6.33 ✅VIP晋级奖励: 👑 VIP1 - 累计8888流水8U 👑VIP2 - 累计 18888流水18U 👑VIP3 - 累计48888流水58U 👑 VIP4 - 累计88888流水 88U 👑 VIP5 - 累计288888流水288U 👑VIP6 - 累计488888流水588U 👑VIP7 - 累计888888流水 888U 👑VIP8 - 累计6888888流水2188U 👑VIP9- 累计1…
👍3
Signed 群管@FLL0
🔥🔥达亿国际🔥🔥单骰🈵1:1倍扫雷🎲,满倍PC2.8加拿大 达亿国际强势入驻TG福利来平台,采用TG官方骰子,任何人无法控制此随机性💯公平公正的娱乐品牌! 全网押金超300WU 达亿单骰🈵倍2.0扫雷333公群: https://t.me/+l5iETsezfvs2MmVk 达亿PC2.8🈵倍加拿大7777公群: https://t.me/+kMJRP-vVIco5NWY8 达亿PC2.0满倍加拿大2828公群: https://t.me/+thiZie8n3Wk1NjNk ———————————— 达亿集团🈵倍扫雷,🈵倍2.8加拿大 专属VIP福利 ⚡️ 特殊红包奖励,抢得越多拿得越爽! 😀【特殊红包奖励】 ✨抢到纯豹奖励⚡️⚡️⚡️⚡️ ✨抢到正顺奖 ⚡️⚡️⚡️ ✨抢到最高奖励⚡️⚡️⚡️ ✨抢到最低奖励⚡️⚡️⚡️ ============================================…
👍4
Signed 群管@FLL0
公群876🈵赔扫雷: https://t.me/+OUhtSBAHVtE5Mzdh 公群《6789》手摇快三牛牛推子 :https://t.me/+-2xhqPqGYodkODk0 项目介绍: 《1️⃣U可以上分》 支持 微信/支付宝/所有钱hb 😃 公群876🈵陪扫雷 😃 手摇公群6789 手摇快三.牛牛.推子 随意切换 无抢摇规则 无抽水 😴 👑快三 推子 u上 一倍水可随时下分 价格:⭐️大白鹅的人情世故: 根据玩家情况每日发各种福利红包🧧 联系人: @xby59 频道(群):https://t.me/+-2xhqPqGYodkODk0
👍2
Signed 群管@FLL0
🟢🟢🟢🟢🟢🟢🟢🟢🟢 🟢🟢🟢🟢🟢 🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢 稳盈综合游戏:@wyyl 👈一键开启 🀄🟢🟢🟢🟢🟢 ① 充值大赠送 ⑥ 电子幸运注单 ② 爆奖投稿奖励 ⑦ 日投注奖励 ③大额出款奖励 ⑧ 周投注奖励 ④真人连赢 奖励 ⑨ VIP 尊享豪礼 ⑤ 真人幸运注单 ⑩ 每日亏返 5% 🟢🟢🟢🟢🟢🟢🟢🟢 ✨🎲扫雷 6688群💫大额无忧 ✨🎲扫雷88888 群💫极速秒到 ✨🧧稳盈快三扫雷💫重磅启幕 ✨🎰稳盈B5综合娱乐 💫 一站畅玩 🧐福利来合计上押超百万U 🧐累计派发玩家盈利超 2800 万 U 😃每日一次流水红包福利 ♑ 流水红包 150U ♑ 流水红包 1500U ♑ 流水红包 15000U 🧐立即登录 B5.COM ,稳盈让娱乐更高效! 🟢🟢🟢: @eeeeee 🟢🟢🟢 : @wyyl
👍4❤1
Signed 群管@FLL0
😀远洋1️⃣3️⃣7️⃣大食堂 ———————————— 群盈利5000+群红包1️⃣8️⃣8️⃣ 群盈利5万+群红包1️⃣8️⃣8️⃣×2 群盈利10万+群红包1️⃣8️⃣8️⃣×3 群盈利15万+群红包1️⃣8️⃣8️⃣×4 群盈利20万+群红包1️⃣8️⃣8️⃣×5 ———————————— 💲以上红包额度以此类推。 💲5000下或负盈利则无红包。 💲公群137当月流水超1000即可进群。 💲或法拉利当月流水超5000即可进群。 💲各大综合台可进群直播广告,每日需向群友交保护费100u起 ———————————— 😀远洋集团 • 满赔扫雷 🀄️ 137 满赔扫雷 🀄️ 全网满赔扫雷天花板 🀄️ 最高限红1刀99999 🀄️ 1分钟翻盘直接封神! ———————————— 😀公群每日红包5️⃣8️⃣8️⃣8️⃣ 红包链接:https://t.me/c/2883856816/6042519 🀄️ 一刀99999高到没对手…
👍2
Signed 群管@FLL0
Showing the 12 most recent of 1,337 posts we hold for @DFHSTYLT. 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.
Named by 3 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.
@DFHSTYLT named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 24 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Telegram免费代理 @FLL8” (@DFHSTYLT), 53,178 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/DFHSTYLT.
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.