Telegram RegisterThe public register of Telegram

Channel

Infinity FR 兄弟战绩

@kingpalacefr

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

4,681subscribers

+10 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-1001887247542
TypeChannel
Username@kingpalacefr
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/kingpalacefr

Topic

Adult — 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 98% 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kingpalacefr/1023 · this entry22 Jul 2026, 11:30 UTC@infinityfr/1194322 Jul 2026, 11:30 UTC1.00under a minute
@kingpalacefr/1024 · this entry25 Jul 2026, 14:57 UTC@infinityfr/1194425 Jul 2026, 14:57 UTC1.00under a minute
@infinityfr/1194526 Jul 2026, 07:44 UTC@kingpalacefr/1025 · this entry26 Jul 2026, 07:45 UTC1.0072 seconds
@infinityfr/1194931 Jul 2026, 10:46 UTC@kingpalacefr/1027 · this entry31 Jul 2026, 10:46 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@infinityfr8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (53)

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. 1 of the 3 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 20 comparable posts for this entry, running 22 June 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 @kingpalacefr — which is this entry. That is a statement about our reading window, not a claim of authorship.

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

4,6714,6814,6767 August 2026 — 4,671 subscribers7 August 2026 — 4,671 subscribers7 August 2026 — 4,677 subscribers10 August 2026 — 4,681 subscribers7 August 202610 August 2026
4 measurements spanning 3 days, net +10. 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 4,670–4,683 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:414,681+4
7 Aug 2026, 18:384,677+6
7 Aug 2026, 08:314,671no change
7 Aug 2026, 08:284,671first reading

Engagement

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

ERR · 30 days
42.1%
avg views ÷ 4,681 subscribers
Avg views / post
1,970
9 posts measured
Reaction rate
0.067%
reactions ÷ views · ER floor
Posts in window
11
of 20 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 7 of 9 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 7 August 2026
Posts held20 (22 June 20267 August 2026)
Views total17,755
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:37 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
572
Videos
1
Links
577

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

22 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 95.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2195.5%
🥰14.55%

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

Measured over the 20 most recent posts we hold, published 22 June 2026 to 7 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

7 Aug 2026, 07:07 UTC760 views1 reactionsread 12 August 2026
Photo

#INFINITY #蕉赖 #PGRM #文长慎入 【LCLYCITY首发】童颜巨乳Tida 首先要感谢Infinity和TG福利群派的福利 让我又有优惠去屌嗨,感恩 在走廊给妹子打了一下屁股! 进到房又给妹子打多一下 床已经铺好了 我们放下东西就去洗澡 妹子洗时就一直用沐浴露撸弟弟 撸到半硬了就把我冲干净 然后帮我舔奶, 我就玩奶 一个手刚刚好 妹子舔完两边奶就蹲下帮我水中箫 然后再给我漱口水 就让我出去等她 我觉得有点冷就把抽风机关了 更完整内容在以下链接: https://lclycity.site/forum.php?mod=viewthread&tid=241821&extra= 尊重原创,转发请注明出处。 INFINITY 蕉赖美女下水服务 你值得一试的美女下水服务 本店提供东南亚美女, 服务素质有保证, 绝不偷工减料, 伴君度过欢乐时刻。 Telegram 频道: @kingpalacefr 营业时间 :

1

6 Aug 2026, 06:49 UTC865 viewsread 12 August 2026
Photo

听过很多关于这位 seasoned WL 的好 review,不过一直都没有特别想见她。可能是因为这间店女生不算多,如果第一个不 ngam,也没有什么 backup option。当天吃完午餐后,我 message captain 拿地址,book 好 Tida 就直接过去。到店付完钱,没多久 Tida 就出来了。她穿着一件超贴身的黑色短晚装,短到几乎盖不住屁股。Damn... 本人跟照片至少有90%像,完全不用 filter 去加分,她本身已经够漂亮了。 我跟着她从后面走进房。一进房,她就先开口问我:"Pernah jumpa ka kita?"。然后一边问,一边直接摸我下面。Woah... 这女生真的很 thirsty,而且那个眼神一直看着我,超性感 😂。我也开玩笑回她一句,然后两个人边脱衣服边 TCSS,顺便认识一下彼此。 之后一起进 shower。近距离看,她那个 foxy face 真的很漂亮。天然 C 或 D c

31 Jul 2026, 10:46 UTC≈1,270 views1 reactionsread 12 August 2026
Photo

#INFINITY #蕉赖 #PGRM #文长慎入 [6月丰收季节感谢帖]善解人意的小只马Sunny 今天在家无聊就顺道过去 Infinity 放松一下。出发前先到 Telegram 看了看当天的排班,发现可选的小姐不多,而 Lily 前阵子才刚回头,所以这次决定换个口味试试 Sunny。店长也顺口推荐她,说她的互动不错,女友感也很好,于是就直接预约。 ​到店后先确认预约资料,店长很快就安排 Sunny 出来接待。她一见面就带着笑容,给人的第一印象亲切自然,没有距离感。随后便带我进房准备,整个流程熟练流畅,让人感觉很放松。 ​简单聊天后才知道,她的华语说得相当不错,沟通没有障碍。她的妆对我的口味来说稍微浓了一点,不过真人看起来还是不错,身材匀称,属于小只马类型,不会太瘦也不会太丰满,整体舒服耐看。脱衣冲凉的时候,气氛就已经很融洽了。 更完整内容在以下链接: https://lclycity.site/forum.php?mo

1

28 Jul 2026, 15:44 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

26 Jul 2026, 07:45 UTC≈1,970 views3 reactionsread 12 August 2026
Photo

某一天 我又jio某大神 “infinity还有位换奖 你要一起过去吗” 某大神很steady bom bibi 又on我了 我就问店长lily有位吗 comfirm时间后 我充满期待的等约定时间到 到了目的地 给了热茶钱 就跟店长谈天一下 毕竟应该有两个月没过来了 然后就看到lily准备好出来了 某大神还没到 我也不忍心看着lily等我 我就先带着lily进去了 进到房间 我就跟她打招呼 还有简单沟通一下 因为她的语言不是特别好 但是她也会很努力表达 中文不会就用英文 英文不会就讲她的语言 最后body language 通常她讲她的语言+body language 我都大概明白她想表达什么了 所以对我来说沟通无压力 然后进了房间 我们就各自脱衣服 准备去洗澡了 洗澡就普通 漱口水 洗重要部位 前面背后都有洗肥皂 还会一次guci我 我guci回她 她还会打我的屁股 出来擦干身体后我就在床上等她 先是简单聊天 然后学一点泰

3

25 Jul 2026, 14:57 UTC≈1,580 views0 reactionsread 12 August 2026
Photo

#INFINITY #蕉赖 #PGRM #文长慎入 [LCLYCITY首发] 偶遇昔日女友感女神Lily,原装大胸狂野热吻 首先想感谢LCLY和店家发放福利。让我有机会寻芳问柳,求的无非是一份身心的放松与那一抹难得的女友感。 前段时间得知之前在其他场子体验极佳的Lily来到了KL区,心中那股念念不忘的悸动再次被勾起,决定去找她回味一番。联系上客服后,对方回复相当神速,不仅客气而且非常有耐心,很快就帮我安排好了时间。 到了现场,Lily第一眼看到我,嘴角便自然地扬起了微笑,她认出我了!那种被记住的感觉真的非常棒。她十分热情地牵着我的手走入房内。说实话,她的真人虽然没有宣传照片上那么惊艳,但十分耐看且带点可爱,加上一身原装大胸的好身材,完全就是我的菜。 刚进房我就有些迫不及待,直接从背部给了她一个熊抱,将她推倒在床上。 更完整内容在以下链接: https://lclycity.site/forum.php?mod=viewthr

22 Jul 2026, 11:30 UTC≈2,000 views1 reactionsread 12 August 2026
Photo

月尾还有一点闲钱,就跑了过来infinity这里,这次就预约了想找一段时间的Lily,然后就过去找了店长吹水一下,然后就看到Lily穿着一身黑色短裙,这么一看身材好像比较普通,没有照片里那么突出(结果一脱了裙子马上知道什么叫做有料),就看到她weixiao着带我进去房间。 进去了房间,准备和她整理床单的时候,看到床上有个发夹,就问看是不是她的,她笑着问我是不是要用,还假装过来帮我夹头发。玩闹了一下后,就一起整理好床,然后转身去脱了衣服挂好,然后一转身就看到她脱光了后,显露出她那穿衣显瘦,脱光有料的身材,苗条的身形配上一双在她身上显得足够大的双乳,lanjiao都开始硬硬底。 接着就准备去冲凉,Lily先拿了漱口水给我漱口,她自己也接着漱口,不过她就含着漱口水比较久,我就在她帮我冲凉的时候,做弄她让她把漱口水吐出来,她就假装要打我,其实就是去捏我的奶头一下。给她洗好了,还被她故意挠我痒,玩闹了一轮,出去擦干身体时就顺便关了抽风

1

17 Jul 2026, 13:40 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

17 Jul 2026, 10:30 UTC≈3,870 views1 reactionsread 12 August 2026
Photo

首先要感谢【熊猫网】和【Infinity】的赞助让我可以免费尝鲜,感激不尽🤝。 本来想约tida尝鲜但是被其他群友约了,在选择不多的情况下选了sunny作为今晚的女主角~ 上到店家sunny还在吃饭,稍等一会后sunny吃饱后就尾随妹子进房间,sunny非常小只皮肤很白像学生妹,而且很健谈华语沟通无障碍。 进到房sunny脱下衣服后那貌似未成年女孩的身材一览无遗,小小但坚挺的胸部,右边凹陷的奶头好像在呼唤我吧它zut出来😄洗澡时忍不住上下其手,引得sunny连喊出了yamatea😅。 上床后妹子先从我的lin头开始zut,她一边zut我的龙弟慢慢升旗顶到她肚子,妹子对着我笑了笑就开始口起了龙弟,是那种温柔且慢条斯理的上下口,这时我提议换个姿势69但妹子躺下展开双腿说你来吃~只好满足妹子的要求,埋头吃起了sunny的修毛鲍鱼,先卖力濑阴蒂继而用舌头深入洞口,这时sunny又飙起了日语yamatea~ 。。。。。。 欲知详

1

17 Jul 2026, 10:19 UTC≈3,400 viewsread 12 August 2026
Photo

她回来一段时间了还没找她叙旧,借着奖励机会找她回味她的大波波先。还是要先感谢雄猫网和infinity的bingo奖励,可以多一次机会扎大波波😍 跟豪哥哥约好时间后准时到达,来到先去上厕所,刚刚好看到tida在外面被她捏了脸一下。上完厕所来到外面基本核对一下中奖身份后坐下喝杯茶等tida准备。 她好了后出来我们寒喧一下被她抓鸟问候,进去前还会嘟嘴讨亲。看来久没找也是好的,好像比较热情一些。 来到房间聊下近况后脱衣服去冲凉,她脱掉身上的裙子时发现到她瘦了,奶也小了半个码~~哎呀瘦到不该瘦的地方,叫她快快吃肥一些长奶先。 过后冲凉洗干净漱好口后开始她的sop,先舔左右奶头过后蹲下帮我水中萧,她含着龟头不断快速吞吐和舌撩马眼,对我而言有点太刺激,所以没什么享受。 口完上来抓她来舌吻先,对我而已舌吻还更爽,过后出去抹干她用鲍鱼坐在微软的龙弟上,然后跟我分享一些她的情史。 。。。。。。 欲知详情,请点击以下链接 https://

15 Jul 2026, 06:49 UTC≈2,040 views2 reactionsread 12 August 2026
Photo

感谢熊猫网跟Infinity店家赞助,刚结束了战斗 又要赶去另一边兑换奖励,提前一晚跟负责人预约心仪的小姐。上门后跟负责人确认身份就等小姐出来 。小姐出来了 , 带我进房 ,小姐的 样子跟照片一模一样,身材我以为会微胖 ,但是没有,是瘦小的小只马。关上门小姐抱着我 ,眼睛对我放电,然后亲了过来,她嘴唇超级干的,像破皮了似的,不懂搽唇膏会改善 吗 ?然后我们就去冲凉,看清楚她的美貌,感觉像日本前Av女优,只是脸上有点痘疤但 底子 是漂亮的。 过程中有聊天,她是Medan的 ,遇过几个Indo 美女 都是Medan 来的 ,果然是印尼的怡宝。她问我多少岁,我让她猜,她猜小了,我都不好意思呢 ,到我问她她说17,信她个鬼。洗洗下她靠过来舔我乳头接着往下水中 萧,对眼口搞到我也不好意思,但是很有感觉,洗完后就到床上等她伺候我 。 她出来后就把毛巾褪去 ,露出她的蜜乳 ,然后 禽上来压着我 ,跟我舌吻个天翻地覆,虽然 舌吻的够够力但是

2

12 Jul 2026, 11:37 UTC≈3,400 views3 reactionsread 12 August 2026
Photo

这Cheras附近见了顾客就想要发泄然后想到了Infinity。上去后只剩下两个小姐就选了Sunny. Sunny刚吃饱就带我进房间然后她就跟我说很热,原来她吃了很辣是食物嘴一直发出吱吱声。 进去后她就铺床单,过后跟我说很热就很快的把衣服脱了,进浴室就洗费澡。洗完后她还是一直发出吱吱声应该辣还没退,过后就问我准备好了吗开始扑过来跟我k起来。 k了蛮久在慢慢往下舔我的奶头,然后往小弟口了起来,她口的时候好像在吃东西一样口了几口就发出声音好像吃到好吃的东西。 口的差不多就换我服务她也是先来个舌吻再往下吃奶头,手就往她的妹妹抚摸,她不抗拒就慢慢的指入,很紧!!! 。。。。。。 欲知详情,请点击以下链接 : https://panda969.site/forum/postid/38513/ 店家咨询 : https://menu.panda969.site/shop/infinity/ 请订阅以查询最新资料: https:

3

Showing the 12 most recent of 20 posts we hold for @kingpalacefr. 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 — 795,978 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.

Forward network

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.

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.

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.

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

“Infinity FR 兄弟战绩” (@kingpalacefr), 4,681 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/kingpalacefr.

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.