Telegram RegisterThe public register of Telegram

Channel

Прокси tg | настройка

@proxy_telegramt

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

11,768subscribers

+382 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002105869070
TypeChannel
Username@proxy_telegramt
DescriptionПостоянные обновления прокси✅ Подпишись чтобы не потерять Прислать прокси: @funymode
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/proxy_telegramt

Topic

Other / unclassifiable — 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 56% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@proxy_telegramt/94 · this entry14 Jun 2026, 06:31 UTC@adrconf/30014 Jun 2026, 06:53 UTC0.9323 minutes
@proxy_telegramt/110 · this entry1 Aug 2026, 07:07 UTC@adrconf/3065 Aug 2026, 11:02 UTC0.924 days
@proxy_telegramt/103 · this entry8 Jul 2026, 16:46 UTC@adrconf/3028 Jul 2026, 18:28 UTC0.881.7 hours
@proxy_telegramt/91 · this entry10 Jun 2026, 11:49 UTC@adrconf/29611 Jun 2026, 05:49 UTC0.8718 hours
@proxy_telegramt/93 · this entry12 Jun 2026, 07:49 UTC@adrconf/29913 Jun 2026, 11:33 UTC0.8728 hours
@proxy_telegramt/100 · this entry20 Jun 2026, 06:00 UTC@adrconf/30121 Jun 2026, 15:02 UTC0.8433 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@adrconf7 (7/7 hand-verifiable sample passed)0.8726 hoursthis entry (70)

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

Views per post sit far above this size band

13,000 average views per post against 11,768 subscribers — an engagement rate of 110.7%. Across the 55,140 registered channels in the same cohort — 10,000–31,619 subscribers — the middle half sit between 4.19% and 20.1%, with a median of 9.77%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured9 of 9 published in the window (0 exact, 9 rounded by Telegram)
Views totalled117,220
Mature posts only121.2% over 8 posts read at least 24h after publication
Subscribers11,768 measured 12 August 2026
Cohortb10000 · 55,140 channels · p10 1.60% · p25 4.19% · p50 9.77% · p75 20.1% · p90 36.0%
Position in cohort99.465th percentile · 11.3× the cohort median
Uncertainty±0.06% of the figure, from Telegram’s rounding

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_source · err_high, last confirmed 12 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

11,38611,76811,5777 August 2026 — 11,386 subscribers8 August 2026 — 11,430 subscribers9 August 2026 — 11,519 subscribers10 August 2026 — 11,569 subscribers11 August 2026 — 11,667 subscribers12 August 2026 — 11,768 subscribers7 August 202612 August 2026
6 measurements spanning 5 days, net +382. 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 11,329–11,825 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:5311,768+101
11 Aug 2026, 10:4611,667+98
10 Aug 2026, 09:3511,569+50
9 Aug 2026, 12:3411,519+89
8 Aug 2026, 12:4311,430+44
7 Aug 2026, 19:1711,386first reading

Engagement

23 posts held, back to 10 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 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
113.7%
avg views ÷ 11,768 subscribers
Avg views / post
13,400
9 posts measured
Reaction rate
0.641%
reactions ÷ views · ER floor
Posts in window
9
of 23 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held23 (10 June 202612 August 2026)
Views total120,400
Reactions total772
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:55 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
1
Videos
1
Links
96

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

1,781 reactions across 23 posts, in 20 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,13363.6%
👍22512.6%
🤝1267.07%
🔥935.22%
🙏482.70%
👏402.25%
🙊321.80%
🥰181.01%
🍓100.561%
❤‍🔥80.449%
👀70.393%
💘70.393%
🕊70.393%
🤷‍♂70.393%
🤪50.281%
👎40.225%
👌30.168%
😎30.168%
🫡30.168%
💋20.112%

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

Measured over the 23 most recent posts we hold, published 10 June 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.

Telegram Stars

Stars received
40
across the posts below
Posts paid on
18
of 23 we hold a reading for · 78%
Most on one post
7
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @proxy_telegramt. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 23 most recent posts we hold for this entry, published 10 June 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 06:54 UTC≈4,390 views44 reactionsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=gg.fsproxy.site&port=8443&secret=eec89526f2260269efb17e34e1c05221ad67672e667370726f78792e73697465 https://t.me/proxy?server=proxy-dag.ru&port=443&secret=ee94fc2b484af6e1e1c87e6576b33c257579612e7275 https://t.me/proxy?server=redflag.yazaebalsyadelatproxy.cc&port=443&secret=ee69e899d89ec68e220ca177557322b27f726564666c61672e79617a616562616c73796164656c617470726f78792e6363 http

36👍3🤝2🥰2❤‍🔥1

11 Aug 2026, 06:50 UTC≈6,080 views60 reactions7 Starsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=lynette.myrka.digital&port=443&secret=ee54701e1686de96a44721501a7bee9e4c6c796e657474652e6d79726b612e6469676974616c https://t.me/proxy?server=185.114.156.160&port=443&secret=ee212b8d26ec678658af5cd0180f33d3047a6f6f6d2e7573 https://t.me/proxy?server=213.165.63.226&port=443&secret=eec8bcc2216d80c00b093510420635ceb0736f6e792e7275 https://t.me/proxy?server=195.133.35.199&port=44

40🔥9👍6🤝3👏2

9 Aug 2026, 05:43 UTC≈8,930 views77 reactions4 Starsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=w.bestproxy.icu&port=8443&secret=ee27b0ae91a7a96aa0c1359f5fa060d1ee772e6265737470726f78792e696375 https://t.me/proxy?server=pasha-make-tg-great-again.gemera.one&port=443&secret=ee704f1b022eff83a12dec8fb2da8f555f65682e766b2e636f6d https://t.me/proxy?server=ardesvpn1.ru&port=8443&secret=ee05cf8e164f926f4a664b2404d276a1d6617264657376706e312e7275 https://t.me/proxy?server=proxy

55👍12🙏4🤝3🫡3

7 Aug 2026, 05:17 UTC≈10,700 views89 reactionsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=api.rekushka.eu.cc&port=443&secret=ee95474049f0bfbbe2711a4caa087df00579616e6465782e7275 https://t.me/proxy?server=lynette.myrka.digital&port=443&secret=ee54701e1686de96a44721501a7bee9e4c6c796e657474652e6d79726b612e6469676974616c https://t.me/proxy?server=cdn3.bopen.bond&port=443&secret=7rS1Td8LnzuC3XtKWoiOqC13Yi5ydQ https://t.me/proxy?server=prx.migstart.ru.tspu.top&port=44

61👍13🤝11👀3💘1

1 Aug 2026, 07:07 UTC≈15,300 views120 reactions1 Starread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=t4.myrka.digital&port=443&secret=ee1111222233334444555566667777888874342e6d79726b612e6469676974616c https://t.me/proxy?server=prx.migstart.ru&port=443&secret=8080f0bb8395a884940b8d59a77c3fd0 https://t.me/proxy?server=185.86.145.78&port=443&secret=ee050c8f82b0877cccd23a08c65f062b987275747562652e7275 https://t.me/proxy?server=37.139.34.242&port=443&secret=dd2ed7517b077ef414e2

81👍29👀4👏3😎3

25 Jul 2026, 12:04 UTC≈18,400 views118 reactions1 Starread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=185.130.115.124&port=443&secret=7k6CzffEyEezPyfF2PLEBT13Yi5ydQ https://t.me/proxy?server=t4.myrka.digital&port=443&secret=ee1111222233334444555566667777888874342e6d79726b612e6469676974616c https://t.me/proxy?server=prx.migstart.ru&port=443&secret=8080f0bb8395a884940b8d59a77c3fd0 https://t.me/proxy?server=max.ru.rightarion.ru&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c5

66👍28👏10🤷‍♂7🙏7

22 Jul 2026, 10:02 UTC≈18,300 views75 reactions1 Starread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=mtp.agenyz.com&port=443&secret=ee676f6f676c652e636f6d749d157e2d https://t.me/proxy?server=tgb92cf27d.koshkaproxy.shop&port=443&secret=ee1e355000114cdb95628c1564225a404b36326334346231662e6b6f73686b6170726f78792e73686f70 https://t.me/proxy?server=proxy.privateproxy.top&port=8443&secret=dd17aca106bf110b8efac6b77a545a8be5 https://t.me/proxy?server=prx.migstart.ru&port=443&secre

46🤝13🥰6🔥5🤪5

19 Jul 2026, 05:57 UTC≈19,800 views85 reactions3 Starsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=94.139.251.17&port=443&secret=ee63142fc4d9dc3b33e26019a5ec3e3a4574726176656c2e79616e6465782e7275 https://t.me/proxy?server=cdn2.bopen.bond&port=443&secret=eeb4b54ddf0b9f3b82dd7b4a5a888ea82d77622e7275 https://t.me/proxy?server=max.ru.rightarion.ru&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c586d61782e7275 https://t.me/proxy?server=mtp.agenyz.com&port=443&secret=ee676f6f6

57👍12🤝11👏3💘2

16 Jul 2026, 06:39 UTC≈18,500 views104 reactionsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=imp.notdev.space&port=443&secret=7rXrTWoFBEbdCchCOVTSRZ9pbXAubm90ZGV2LnNwYWNl https://t.me/proxy?server=imppro.notdev.space&port=443&secret=7qqL8c31vvKE9Ao_ymZtZqlpbXBwcm8ubm90ZGV2LnNwYWNl https://t.me/proxy?server=impgo.notdev.space&port=443&secret=7qyw1d9Fd25A9qmA-Qvib9FpbXBnby5ub3RkZXYuc3BhY2U https://t.me/proxy?server=impforyou.notdev.space&port=443&secret=7lz0xzPeT7mCZ

65🔥14👏12🤝8🍓5

10 Jul 2026, 13:42 UTC≈19,000 views71 reactions3 Starsread 13 August 2026

ОБХОД БС✅ Друзья, Всем, кому нужен стабильный доступ не только к Telegram, но и к YouTube, Instagram и другим соцсетям - используйте MOBILA VPN. ✅ Обходит белые списки ✅ Отлично работает на Wi-Fi и мобильном интернете ✅ Стабильное соединение без отвалов Если устали от блокировок и тормозов - это то, что нужно. 👉 Переходи и тестируй: @Mobilavpn_bot

🙊3221👍10🔥5👌3

8 Jul 2026, 16:46 UTC≈21,500 views107 reactions3 Starsread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=37.139.34.32&port=443&secret=ee6164732e78352e72759c6509729477 https://t.me/proxy?server=ardesvpn1.ru&port=8443&secret=7gXPjhZPkm9KZkskBNJ2odZhcmRlc3ZwbjEucnU https://t.me/proxy?server=mtp2.hlebushek.com&port=443&secret=ee8263f1fdfbfa0629c67c40d208806873706574726f766963682e7275 https://t.me/proxy?server=46.173.17.103&port=443&secret=ee0dbf98440246f4b9228dd2b704256cad6f7a6f6e

67🤝15🔥12🙏9💘4

4 Jul 2026, 06:27 UTC≈21,900 views120 reactions1 Starread 13 August 2026

➕НОВЫЕ ПРОКСИ https://t.me/proxy?server=og.shieldblack.store&port=443&secret=7tR4pjU_H3NZNMh4yqYscgpwZXRyb3ZpY2gucnU https://t.me/proxy?server=bak.myrka.digital&port=8443&secret=eea3f8c1d2e4b59607182a3b4c5d6e7f8062616b2e6d79726b612e6469676974616c https://t.me/proxy?server=proxy.lodkirmm.ru&port=8443&secret=ee16309abd572d284b309ef26bd7a3f685d0b7d0ba70726f78792e6c6f646b69726d6d2e7275 https://t.me/proxy?server=51.25

85👍13🤝8🕊7🙏7

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 946,809 of 1,160,990entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Прокси tg | настройка” (@proxy_telegramt), 11,768 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/proxy_telegramt.

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.