Telegram RegisterThe public register of Telegram
Telegram profile photo for 海华出海-供需资源发布/供应30U/需求15U

Channel

海华出海-供需资源发布/供应30U/需求15U

@chuhaigongx

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

23,420subscribers

+19,775 since we began measuring on 17 September 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002821926844
TypeChannel
Usernames@chuhaigongx @haihuashuju
Description供需信息发布频道一 @haihuagong 图文供应50U/需求信息25U 文字供应30U/需求信息15U 图文自助机器人 @haihuagx_bot 文字自助机器人 @haihuabbot 海华公告 @haihua_gg 海华一群 @hhchtrx 海华二群 @haihua_danbao 海华三群 @hhtrxxxx 海华供需 @haihuagongx 海华曝光 @haihuabaoguan 海华兑换 @haihuaTRXbo 海华新闻 @xinwen_Ne
Created18 June 2025 — measured — dated from the channel’s first post
First recorded17 September 2026
Last confirmed live15 November 2026
Measurements held32
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/chuhaigongx

Topic

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 5 October 2026 and assigned it the closest of 31 fixed categories, at 81% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@chuhaigongx/1478 · this entry16 Sept 2026, 04:31 UTC@haihuagong/279516 Sept 2026, 04:31 UTC1.00under a minute
@chuhaigongx/1489 · this entry21 Sept 2026, 10:16 UTC@haihuagong/282321 Sept 2026, 10:16 UTC1.00under a minute
@chuhaigongx/1497 · this entry2 Oct 2026, 09:48 UTC@haihuagong/28532 Oct 2026, 09:48 UTC1.00under a minute
@chuhaigongx/1498 · this entry3 Oct 2026, 05:30 UTC@haihuagong/28603 Oct 2026, 05:30 UTC1.00under a minute
@chuhaigongx/1504 · this entry7 Oct 2026, 17:13 UTC@haihuagong/28807 Oct 2026, 17:13 UTC1.00under a minute
@chuhaigongx/1522 · this entry24 Oct 2026, 06:32 UTC@haihuagong/296824 Oct 2026, 06:32 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@haihuagong40 (8/8 hand-verifiable sample passed)0.98under a minutethis entry (40–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 41 comparable posts for this entry, running 15 September 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @chuhaigongx — 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 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. 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.

Growth

3,60425,61814,61117 September 2026 — 3,645 subscribers18 September 2026 — 3,638 subscribers27 September 2026 — 3,604 subscribers5 October 2026 — 15,683 subscribers9 October 2026 — 15,668 subscribers13 October 2026 — 15,652 subscribers14 October 2026 — 15,639 subscribers15 October 2026 — 15,631 subscribers16 October 2026 — 15,626 subscribers17 October 2026 — 15,622 subscribers18 October 2026 — 15,618 subscribers20 October 2026 — 25,618 subscribers21 October 2026 — 25,616 subscribers23 October 2026 — 25,615 subscribers24 October 2026 — 25,609 subscribers25 October 2026 — 25,600 subscribers26 October 2026 — 25,597 subscribers27 October 2026 — 25,594 subscribers28 October 2026 — 25,593 subscribers30 October 2026 — 25,591 subscribers31 October 2026 — 25,585 subscribers1 November 2026 — 25,564 subscribers2 November 2026 — 25,544 subscribers3 November 2026 — 25,535 subscribers4 November 2026 — 25,333 subscribers5 November 2026 — 25,173 subscribers6 November 2026 — 24,958 subscribers7 November 2026 — 24,786 subscribers8 November 2026 — 24,645 subscribers9 November 2026 — 24,330 subscribers11 November 2026 — 23,906 subscribers15 November 2026 — 23,420 subscribers23,42017 September 202615 November 2026
32 measurements spanning 59 days, net +19,775. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 302–28,920 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
15 Nov 2026, 01:0523,420-486
11 Nov 2026, 19:4723,906-424
9 Nov 2026, 22:4624,330-315
8 Nov 2026, 10:5924,645-141
7 Nov 2026, 07:1024,786-172
6 Nov 2026, 05:1924,958-215
5 Nov 2026, 05:1525,173-160
4 Nov 2026, 08:0425,333-202
3 Nov 2026, 11:0925,535-9
2 Nov 2026, 12:1025,544-20
1 Nov 2026, 11:4525,564-21
31 Oct 2026, 08:1925,585-6
30 Oct 2026, 11:4925,591-2
28 Oct 2026, 12:4025,593-1
27 Oct 2026, 09:4725,594-3
26 Oct 2026, 11:1125,597-3
25 Oct 2026, 11:5025,600-9
24 Oct 2026, 08:3125,609-6
23 Oct 2026, 05:1825,615-1
21 Oct 2026, 01:4625,616first reading

Engagement

46 posts held, back to 18 June 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.32%
avg views ÷ 23,420 subscribers
Avg views / post
2,180
23 posts measured
Reaction rate
0.081%
reactions ÷ views · ER floor
Posts in window
23
of 46 held

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 1 of 23 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held46 (18 June 2025 – 14 November 2026)
Views total50,192
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 21: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.

What this channel posts

Photos
47
Links
6

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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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 1 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 1 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 18 June 2025 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 23 posts held from the last 30 days (8.70%) 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).

14 Nov 2026, 08:45 UTC634 viewsread 17 November 2026
Photo

🟢 供給 #64 · 供应信息 🔥 胖哥新出数据 💰 價格:面議 • 印度车辆违章记录 • 新加坡招聘信息 • 九方 / 牛股王数据 • 出美股、接定点渗透 • 接美区BC首充打A 📞 聯絡:@Simon777M 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

14 Nov 2026, 08:41 UTC632 viewsread 17 November 2026
Photo

🟢 供給 #63 · 供应信息 apple数据 · 创建2020·安全无绝对 主营全球数据|辅助盘口拿到真实数据 💰 價格:面議 服务范围:提取·渗透·脱裤·包售后 【银行理财】【稳定职业】【纳税】 【企业高管】【在职办公】【车房】 【航空】【旅游】【酒店】【高消】 【交友】【婚恋】【购物】【白领】 【求职】【购物】【宝妈】【美妆】 【股民】【投资】【B2B】【珠宝】 【奢侈】【保险】【医生】【业主】 【币安】【欧易】【领英// 亚马逊】 📞 聯絡:@apple_date 🔗 頻道:@apple_shuju 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

11 Nov 2026, 10:36 UTC642 viewsread 17 November 2026
Photo

🔴 需求 #62 · 需求信息 需要WS全参混合,劫持各种老号、高混、普混、群发号 💰 價格:面議 一手机房源头来,中介勿扰,量大不罚站可包养 📞 聯絡:@wangss22 @jh68669 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

4 Nov 2026, 14:42 UTC794 viewsread 17 November 2026
Photo

🟢 供給 #61 · 供应信息 手机有苹果,云控有波罗,波罗云控嘎嘎好用 马可波罗WS/TG/LINE/RCS/手机短信双向群发系统,好产品无需多言,出海至今0差评 💰 價格:面議 所有产品都在频道展示,关注频道不迷路 📞 聯絡:@MK_kefu 🔗 頻道:@MK_yunkong 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

31 Oct 2026, 13:33 UTC≈1,980 viewsread 17 November 2026
Photo

🟢 供給 #59 · 供应信息 🍊 黄果短剧 AI 🎬 原创 AI 成人短剧第一品牌 🔥 看剧就上黄果短剧! 🎥 黄果短剧官网 AI短剧 · 原创短剧 · 精彩内容在线观看 黄果短剧持续更新 AI 短剧、原创短剧、漫剧及热门剧情内容,提供最新上架、热门排行榜、专题推荐及高清在线播放,带来沉浸式追剧体验! 💰 價格:面議 ✨ 四大核心特色 🎬 AI 原创|独家内容 🔥 成人向|刺激精彩 ⚡ 更新快|每日上新 💎 超清画质|极致体验 👑 海量原创 · AI 成人短剧 🎞️ 精彩剧情,持续更新 🍿 海量内容,随心观看 🚀 高清播放,畅享精彩 官网 https://vip.towebz.work 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

30 Oct 2026, 04:15 UTC≈1,340 viewsread 17 November 2026
Photo

🟢 供給 #58 · 供应信息 🚀 海华 TikTok 双向回复系统|正式上线通知 🔥 全球可打|双向回复|员工坐席|精准筛选 📢 系统正式上线! 支持多种业务场景: ✅ 兼职项目 ✅ 交友项目 ✅ SE 项目 ✅ 其他各类推广项目 💰 價格:面議 🌐 全球国家均可发送,不限制地区! 💎 一、开户费用及坐席管理 💵 开户费用:1000 RMB / 月 不限制员工坐席账户数量 支持按需分配员工接待坐席 支持多员工协同接待与管理 可备注客户资料,方便后续跟进 💎 二、双向消息收费模式 ✉️ 首条消息发送成功才计费! ✅ 首条发送成功收费 ✅ 客户后续回复免费 ✅ 支持双向互动沟通 💵 详细发送价格及开户激活码,请咨询客服。 💎 三、精准筛选|减少无效引流 📍 建议首条消息以简单打招呼为主。 客户回复后,可根据以下条件进行筛选: 🔹 年龄 🔹 国家 / 地区 🔹 有无意向 🔹 客户资料及跟进备注 🎯 减少盲目引流,提高客户筛选效…

28 Oct 2026, 14:11 UTC≈1,240 views1 reactionsread 17 November 2026
Photo

🟢 供給 #57 · 供应信息 🚀 大力IM|全球机房直发 🌍 全球机房资源|日发千万级 💰 價格:面議 💰 全网最低价 · 实际送达计费 ⚡ 海量发送|高效稳定 ✅ 支持开通独立后台 📞 聯絡:@daliworking998 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

❤1

27 Oct 2026, 18:22 UTC≈1,370 viewsread 17 November 2026
Photo

🟢 供給 #56 · 供应信息 海华TK强私V1版本正式上线! 内容简单粗暴,主打高效落地! 💰 價格:面議 一、平台上线福利 为回馈长期合作的各位老板,现推出以下政策: 端口免费使用,只需购买账号 二、账号价格及发送规则 账号暂定价格:10 RMB / 个 100 个账号起订 100个账号保底发送 30,000 条 按保底量核算,单条成本约 0.00033 RMB 实际发送量以后台记录为准 不足保底数量的处理方式: 如发送量低于 30,000 条,可提供任务截图,由客服后台核实后补齐相应余量。 📞 聯絡:@huameiok @huageok 🔗 頻道:@haihuabc 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

27 Oct 2026, 09:32 UTC≈1,340 viewsread 17 November 2026
Photo

🟢 供給 #55 · 供应信息 apple数据 · 创建2020·安全无绝对 主营全球数据|辅助盘口拿到真实数据 💰 價格:面議 服务范围:提取·渗透·脱裤·包售后 【银行理财】【稳定职业】【纳税】 【企业高管】【在职办公】【车房】 【航空】【旅游】【酒店】【高消】 【交友】【婚恋】【购物】【白领】 【求职】【购物】【宝妈】【美妆】 【股民】【投资】【B2B】【珠宝】 【奢侈】【保险】【医生】【业主】 【币安】【欧易】【领英// 亚马逊】 📞 聯絡:@apple_date 🔗 頻道:@apple_shuju 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

26 Oct 2026, 19:36 UTC≈1,340 viewsread 17 November 2026
Photo

🟢 供給 #54 · 供应信息 马可波罗WS/TG/LINE/RCS/短信双向群发系统【都是包号包控,按首条发送成功条数计费,回复都是免费!均可开后台,免费翻译,上料即发】兼职、股票、交友、维权、资金盘、高仿、黑五类等都可以接,冰点价格! 💰 價格:面議 1、WS双向坐席回复打粉云控,包含鎂国全球可接,例如:镁国、印度、巴基斯坦、尼日利亚、孟加拉、法国皆有本国号,都有量可接! 2、AG云控-TG 双向坐席回复打粉云控,全球可接,国家无限制,目前鎂国、加拿大、印度、印尼、越南、巴西、土耳其、意大利、马来、墨西哥、乌兹别克斯坦、哥伦比亚、埃及等本国号发送,其他国家优先欧混号发送,可免费定制头像和昵称打,上料即发! 3、LINE 双向坐席回复打粉云控,上量即发【韩国、泰国本国号发送】 4、短信双向坐席回复打粉云控,镁国、加拿大、英国、法国都有量可接! 5、FB,INS自选号和大小黑全球有量 6、TG直登号,会员号全球有量! 7、LI…

26 Oct 2026, 19:07 UTC≈2,490 viewsread 17 November 2026
Photo

🟢 供給 #53 · 供应信息 🍊 黄果短剧 AI 🎬 原创 AI 成人短剧第一品牌 🔥 看剧就上黄果短剧! 🎥 黄果短剧官网 AI短剧 · 原创短剧 · 精彩内容在线观看 黄果短剧持续更新 AI 短剧、原创短剧、漫剧及热门剧情内容,提供最新上架、热门排行榜、专题推荐及高清在线播放,带来沉浸式追剧体验! 💰 價格:面議 ✨ 四大核心特色 🎬 AI 原创|独家内容 🔥 成人向|刺激精彩 ⚡ 更新快|每日上新 💎 超清画质|极致体验 👑 海量原创 · AI 成人短剧 🎞️ 精彩剧情,持续更新 🍿 海量内容,随心观看 🚀 高清播放,畅享精彩 📞 聯絡:🔗 https://mg2.ss9dfs.com 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

26 Oct 2026, 18:30 UTC≈2,550 viewsread 17 November 2026
Photo

🔴 需求 #49 · 需求信息 需要WS全参混合,劫持各种老号、高混、普混、群发号 💰 價格:面議 一手机房源头来,中介勿扰,量大不罚站可包养 📞 聯絡:@wangss22 @jh68669 👉 透過 @haihuagx_bot 刊登,/post 我也要貼

Showing the 12 most recent of 46 posts we hold for @chuhaigongx. 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.

Posts edited after publishing

@chuhaigongx 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.

First edit seen
2 November 2026
Most recent edit
2 November 2026

Mentions

Named by 1 registered channel — 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.

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.

Cite this entry

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.

“海华出海-供需资源发布/供应30U/需求15U” (@chuhaigongx), 23,420 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/chuhaigongx.

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.