Telegram RegisterThe public register of Telegram

Channel

泰国头条爆料(Bole新闻)

@thnews

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,181subscribers

-18 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002240391941
TypeChannel
Usernames@bolethailand @thnews
Description#泰国爆料 #泰国头条 @thnews #泰国新闻 泰国头条爆料频道,新闻爆料都看Bole新闻! 投稿爆料找工作: @Bole90Com_Bot Bole新闻官方网址: www.bole90.com 🇵🇭菲律宾爆料频道:https://t.me/phnews 🇻🇳越南爆料频道:https://t.me/vnnews 东南亚华人交流群:https://t.me/boleguanfang 东南亚求职&招聘:https://t.me/bolezhaopin
CreatedBetween 1 May 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/thnews

Topic

National news — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 78% 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.

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

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@thnews/40597 · this entry7 Aug 2026, 09:00 UTC@phnews/654657 Aug 2026, 09:00 UTC1.00under a minute
@thnews/40605 · this entry7 Aug 2026, 10:00 UTC@phnews/654737 Aug 2026, 10:00 UTC1.00under a minute
@thnews/40610 · this entry7 Aug 2026, 11:00 UTC@phnews/654797 Aug 2026, 11:00 UTC1.00under a minute
@thnews/40617 · this entry7 Aug 2026, 13:00 UTC@phnews/654877 Aug 2026, 13:00 UTC1.00under a minute
@phnews/654957 Aug 2026, 15:00 UTC@thnews/40623 · this entry7 Aug 2026, 15:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@phnews5 (5/5 hand-verifiable sample passed)1.00under a minute@phnews (50)

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. 5 of the 5 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 18 comparable posts for this entry, running 7 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.

  • 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).

Across the whole group of 2, the earliest publisher we hold is @phnews. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Also posting the same content

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.

Growth

7,1817,1997,1907 August 2026 — 7,199 subscribers7 August 2026 — 7,199 subscribers7 August 2026 — 7,199 subscribers10 August 2026 — 7,183 subscribers11 August 2026 — 7,181 subscribers7 August 202611 August 2026
5 measurements spanning 3 days, net -18. 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 7,178–7,202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:237,181-2
10 Aug 2026, 13:237,183-16
7 Aug 2026, 14:467,199no change
7 Aug 2026, 12:477,199no change
7 Aug 2026, 12:337,199first reading

Engagement

102 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
65.8%
avg views ÷ 7,181 subscribers
Avg views / post
4,720
83 posts measured
Reaction rate
0.04%
reactions ÷ views · ER floor
Posts in window
102
of 102 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 48 of 83 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 12 August 2026
Posts held102 (7 August 202612 August 2026)
Views total392,160
Reactions total90
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:18 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
22,800
Videos
4,720
Links
15,600

Lifetime counters from Telegram’s own channel header, read 12 August 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.

Video runtime
9m 12s
Average length
32s

Measured directly from 17 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.

Reaction mix

90 reactions across 48 posts, in 9 distinct kinds. The most used accounts for 31.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2831.1%
👏2022.2%
👎1314.4%
1112.2%
🔥66.67%
🤔55.56%
🥰55.56%
😁11.11%
🫡11.11%

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 48 of the 102 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 90reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 102 most recent posts we hold, published 7 August 2026 to 12 August 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

12 Aug 2026, 02:00 UTC≈1,760 viewsread 12 August 2026
Photo

#泰媒报道 芭提雅两名中国游客骑摩托险撞行人,拒绝检查后撞上政府车辆⚠️⚠️⚠️ 泰国芭提雅8月11日晚发生一起涉及两名中国游客的交通事件。两人骑摩托车经过斑马线时,#不仅未佩戴头盔,#还险些撞到正在过街的行人。警方拦查后,双方发生争执,其中一人试图骑车离开,最终撞上一辆政府车辆。 事发当晚约8时30分,芭提雅市警察局交通警员正在警局外协助行人过街,发现两名中国游客驾驶黑色GPX摩托车经过斑马线,两人均未戴头盔。 警方随即将车辆拦下,要求驾驶员出示驾驶证并接受检查。不过,现场随后发生争执,涉事人员情绪激动,其中一人试图骑车离开。 摩托车在离开过程中撞上附近一辆政府车辆,造成两辆车不同程度受损。警方随后将涉事驾驶员带回警局调查。 目前案件仍在处理中,涉及未佩戴头盔、疑似无证驾驶以及造成政府车辆损坏等问题,具体责任和处罚结果有待警方进一步调查。 ps:大胆啊😂😂 ——————————————— 🔔【投稿爆料】

12 Aug 2026, 01:32 UTC≈2,620 viewsread 12 August 2026
Video

#Bole文化 #起床搬砖 #东南亚正能量 时间是个庸医但是包治百病 🌈 ——————————————— 🔔【投稿爆料】 💴【商务合作】 🚀【泰国新闻】 💌【泰国论坛】 🌈【每日热点】 📣【一键关注】 🔥🔥🔥广告赞助商户🔥🔥🔥 1️⃣九博国际:玩U投上九博 百万担保 大额无忧 2⃣KM包网:全程一站式服务,只需1万做盘总! 3️⃣佳运支付:EBPAY全球领先 4️⃣🇹🇭泰國小萬通🇹🇭萬事皆可通。 5️⃣香港🇭🇰《诺威达移民》📣最快20天🚀帮你拿新护照,全球身份规划专家团队规划.安全|省心省力🔔 6️⃣50.com钱包:开户即享0费率,🇨🇳50.com钱包开启世界杯护航模式!

11 Aug 2026, 15:12 UTC≈8,440 viewsread 12 August 2026
Video

#泰国新闻 #今日热点 #热点新闻 : 今日泰国热点新闻汇总‼️‼️‼️ 1、泰缅边境突袭!19岁中国男子与5名外籍人员被抓 https://bole90.com/portalview-253205.html 2、演唱会散场后爆冲突!曼谷BTS站多人围殴画面曝光 https://bole90.com/portalview-253155.html 3、买房还是“藏房”?泰警突查华欣豪宅,4名中国人被抓 https://bole90.com/portalview-253121.html 4、逃离柬埔寨后转战老挝开赌网!41名泰国人被一锅端 http://bole90.com/portalview-253172.html 5、泰国警方启动全国扫枪行动,严查非法枪械与炸弹 http://bole90.com/portalview-253152.html ——————————————— 🔔【投稿爆料】 💴【商务合作

11 Aug 2026, 15:00 UTC≈8,540 viewsread 12 August 2026
Photo

⭐️U体育 🔤🔤🔤🔤🔤🔤 博系全新平台强势上线🌍 🔥😀😀😀😀😀😀😀😀😀😀 🎾博系唯一独家【1️⃣个有效会员可以享受佣金政策的平台】🎾 【U体育合营代理】5⃣月活动❤ 免费加盟代理: 😀 5⃣5⃣🔣净输赢分红 😀 介绍代理长期分红8⃣🔣 😀 新增奖励最高2⃣9⃣9⃣9⃣9⃣8⃣ 😀 无缝升级VIP等级免费平移 😀 会员首存彩金➕日存彩金 U存U提|不黑不卡|公平公正|不限制盈利玩家|出款又快又稳|最稳平台|最快出款|最靠谱招商|U体育助力您实现财富自由 😃😀😃频道: @uty888 😄😃😄😃招商: @uty999 😄😃😄😃官网: uty.cc / uty4.com 🤝诚邀个人代理,团队代理,SEO,劫持,网站站长,飞机群主,电销团队,主播,博主合作洽谈,只要你有流量即可变现,全网最高!

11 Aug 2026, 14:12 UTC≈7,730 views1 reactionsread 12 August 2026
Video

#boleDJ #每日一嗨 #东南亚深情 : 东南亚每日🔡🔡☄☄☄ 🌷如倒影水中的鲜花,只可看看未能摘⛅ ——————————————— 🔔【投稿爆料】 💴【商务合作】 🚀【泰国新闻】 💌【泰国论坛】 🌈【每日热点】 📣【一键关注】 🔥🔥🔥广告赞助商户🔥🔥🔥 1️⃣九博国际:玩U投上九博 百万担保 大额无忧 2⃣KM包网:全程一站式服务,只需1万做盘总! 3️⃣佳运支付:EBPAY全球领先 4️⃣🇹🇭泰國小萬通🇹🇭萬事皆可通。 5️⃣香港🇭🇰《诺威达移民》📣最快20天🚀帮你拿新护照,全球身份规划专家团队规划.安全|省心省力🔔 6️⃣50.com钱包:开户即享0费率,🇨🇳50.com钱包开启世界杯护航模式!

👏1

11 Aug 2026, 13:42 UTC≈5,510 views1 reactionsread 12 August 2026
Photo

#泰国木材走私 🔥🔥湄公河突袭截船!泰国海军缴获1115根木材,红木价值超684万泰铢 泰国穆达汉府近日传出一起木材走私案,湄公河巡逻队突袭一艘可疑钢制船只,当场抓获2名嫌疑人。 警方在船上查获1115根原木,其中977根被鉴定为泰国紫檀,体积约13.68立方米,估值 #超过684万泰铢,另有138根木材种类尚待确认。 据了解,8月8日晚,泰国海军巡逻队在穆达汉府湄公河沿岸发现 #可疑船只,随即展开检查并将涉案人员及木材扣押。 目前,所有木材已移交当地警方进一步调查,案件将依据森林法和海关法处理。 泰方表示,将继续加强湄公河巡逻,严打木材、毒品及其他非法货物跨境走私。 ——————————————— 🔔【投稿爆料】 💴【商务合作】 🚀【泰国新闻】 💌【泰国论坛】 🌈【每日热点】 📣【一键关注】 🔥🔥🔥广告赞助商户🔥🔥🔥 1️⃣九博国际:玩U投上九博 百万担保 大额无忧 2⃣KM

👏1

11 Aug 2026, 13:22 UTC≈6,660 views1 reactionsread 12 August 2026
Photo

#泰国出租车 #乱收费 ⛔️⛔️泰国出租车乱收费翻车!老挝乘客被多收4500泰铢,司机被罚款并吊销驾照 泰国乌汶府近日查处一起出租车乱收费事件,一名司机因向老挝乘客收取 #明显过高车费,被交通部门处罚。 据调查,司机从乌汶府前往崇麦边境口岸,全程约94公里,却按照每公里50泰铢报价,最初要求乘客 #支付4500泰铢。双方多次协商后,最终将车费降至3600泰铢。 事件曝光后,32岁司机萨查·萨拉维特被交通部门传唤,并承认相关行为。司机随后向乘客道歉,并退还多收费用。 交通部门同时对其处以2000泰铢罚款,并暂时 #吊销其驾驶执照。 警方也提醒,想从事正规出租车载客业务,必须按照规定注册并取得相应资质。 ps:又宰客🔫🔫 ——————————————— 🔔【投稿爆料】 💴【商务合作】 🚀【泰国新闻】 💌【泰国论坛】 🌈【每日热点】 📣【一键关注】 🔥🔥🔥广告赞助商户🔥🔥🔥 1️⃣

👍1

11 Aug 2026, 13:02 UTC≈4,600 viewsread 12 August 2026
Photo

#普吉岛 #中国游客 #狮子咬人 中国游客普吉被狮子咬伤⁉️⁉️泰方调查后回应:实际只是擦伤‼️‼️ 近日,一则“中国游客在普吉岛与狮子互动时被咬伤”的消息在社交平台引发关注,现场情况也随即受到泰方调查。 8月11日,普吉府游客援助中心前往涉事场所核查。工作人员确认,确实有中国游客与狮子互动后受伤,但伤势仅为表皮擦伤,并非网传的严重咬伤。 据现场方面介绍,涉事狮子是一只名叫凯撒的幼狮,园区狮子均已接种疫苗。事件实际发生在今年春节期间,由于时间较久,现场监控已经无法调取。 虽然伤情没有网传那么严重,但狮子毕竟属于大型肉食动物,近距离互动仍存在风险。泰方提醒游客参与动物互动项目时,务必听从工作人员安排,别把猛兽当宠物玩。 ps:中国人就是喜欢夸大🖕🖕 ——————————————— 🔔【投稿爆料】 💴【商务合作】 🚀【泰国新闻】 💌【泰国论坛】 🌈【每日热点】 📣【一键关注】 🔥🔥🔥

11 Aug 2026, 13:00 UTC≈6,320 viewsread 12 August 2026
Photo

🌐【ByteShield CDN】 亚洲顶尖边缘云服务品牌,助您打破跨境困局! 您的线上业务是否正面临这些难题? 🚫 CDN不稳定,流量受限,后台卡顿? 🚨 DDoS攻击不断,网站频频宕机? 🇨🇳 服务部署中国,受墙干扰、备案麻烦? 别担心,ByteShield CDN,做您云端业务的最强后盾! 🔰 全球加速·安全护航 我们提供一站式全球边缘云网络服务,无论您客户在中国、东南亚还是全球其他市场。 我们能为您解决: ✅ 高防DDoS,保障业务7×24小时在线 ✅稳定CDN加速,解决访问卡顿与丢包问题 ✅覆盖中国+东南亚+全球市场的智能节点部署 ✅免备案加速,轻松穿越复杂网络环境 让ByteShield CDN,为您的网站、平台、应用全面护航,轻松应对任何挑战! 欢迎咨询合作 @byteshield_bd

11 Aug 2026, 12:42 UTC≈4,450 viewsread 12 August 2026
Photo

#产业新闻 诈骗园区未消失‼️‼️ 华人老板转移“办公室”至宿舍楼,约3000名外籍人员仍在园区 华人老板将“诈骗办公室”转移至宿舍楼,诈骗活动并未消失——从湄索边境即可看到。在此前针对诈骗团伙展开大规模打击行动后,不少人可能认为,缅甸妙瓦底沿线的诈骗园区已经被关闭或停止运营。 但来自缅甸一侧、与泰国达府湄索边境相对的 Yulong Bay Park(玉龙湾园区) 最新消息显示,实际情况可能并非如此。 诈骗人员并没有消失,而是在“换楼”,同时改变运营方式,让整个诈骗活动更加隐蔽。 从诈骗大楼转移到“宿舍办公室” 当地消息人士透露,此前曾被用作诈骗办公室的多栋建筑已经被缅甸军方封锁,因此部分华人老板将运营地点转移到工人居住的宿舍楼内。 这些建筑大约有3至4层。据报道,部分建筑的一楼已经被改造成诈骗工作的办公区域,而楼上仍然作为住宿场所使用。 据了解,园区内的中国籍工作人员被限制自由离开宿舍楼。目前园区内对车辆也实

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

Citation-graph rank

Citation-graph rank — 599,123 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“泰国头条爆料(Bole新闻)” (@thnews), 7,181 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/thnews.

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.