⚡️ Момент знищення українським перехоплювачем P1-SUN JetKiller російського реактивного дрона «герань-5». Підписатися на Times of Ukraine
❤74👍74🔥63😁14😢2

Channel
@times_ukraina
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
2,682,623subscribers
+32,906 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001431180517 |
|---|---|
| Type | Channel |
| Username | @times_ukraina |
| Description | Політичне та незалежне медіа, якому довіряють. Співпраця — @tu_marketer Надіслати новину — @tu_national_bot |
| Created | 16 March 2020 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/times_ukraina |
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 8 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 11 other registered channels. They sit inside a group of 377 channels that share the same post bodies with each other. 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 |
|---|---|---|---|
| @times_ukraina/7015 · this entry3 Mar 2022, 11:21 UTC | @truexanewsua/285973 Mar 2022, 11:23 UTC | 1.00 | 72 seconds |
| @times_ukraina/66036 · this entry26 Apr 2026, 11:43 UTC | @truexanewsua/13647526 Apr 2026, 12:43 UTC | 1.00 | 59 minutes |
| @times_ukraina/68138 · this entry13 Jun 2026, 14:51 UTC | @truexanewsua/13925713 Jun 2026, 16:33 UTC | 1.00 | 1.7 hours |
| @times_ukraina/17177 · this entry26 May 2023, 18:15 UTC | @truexanewsua/7369626 May 2023, 18:30 UTC | 0.99 | 15 minutes |
| @truexanewsua/9988916 Oct 2024, 08:00 UTC | @times_ukraina/41808 · this entry24 Oct 2024, 08:00 UTC | 0.99 | 8 days |
| @times_ukraina/56992 · this entry16 Oct 2025, 13:06 UTC | @insiderukr/10902016 Oct 2025, 13:31 UTC | 1.00 | 25 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @truexanewsua | 187 (8/8 hand-verifiable sample passed) | 0.98 | 70 minutes | this entry (125–62) |
| @insiderukr | 147 (8/8 hand-verifiable sample passed) | 0.96 | 67 minutes | @insiderukr (100–47) |
| @UaOnlii | 58 (8/8 hand-verifiable sample passed) | 0.96 | 8 minutes | this entry (33–25) |
| @voynareal | 30 (8/8 hand-verifiable sample passed) | 0.98 | 45 minutes | this entry (24–6) |
| @u_now | 12 (8/8 hand-verifiable sample passed) | 0.93 | 46 minutes | this entry (10–2) |
| @kievinfo_kyiv | 10 (8/8 hand-verifiable sample passed) | 0.97 | 76 minutes | this entry (7–3) |
| @Tryzub_ukraina | 10 (8/8 hand-verifiable sample passed) | 0.97 | 12 hours | this entry (7–3) |
| @bbbreaking | 7 (7/7 hand-verifiable sample passed) | 0.99 | 6 minutes | @bbbreaking (7–0) |
| @oko_ua | 6 (6/6 hand-verifiable sample passed) | 0.96 | 1.6 hours | this entry (5–1) |
| @kievreal1 | 6 (6/6 hand-verifiable sample passed) | 0.98 | 3.3 hours | this entry (4–2) |
| @lachentyt | 5 (5/5 hand-verifiable sample passed) | 1.00 | 67 minutes | @lachentyt (3–2) |
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 201 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 44,488 comparable posts for this entry, running 16 March 2020 to 8 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 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 8 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 376 other registered channels, 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.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 18:01 | 2,682,623 | +16,970 |
| 19 Sept 2026, 15:36 | 2,665,653 | +3,026 |
| 17 Sept 2026, 01:21 | 2,662,627 | +7,273 |
| 15 Sept 2026, 04:59 | 2,655,354 | +3,677 |
| 13 Sept 2026, 13:57 | 2,651,677 | +9,312 |
| 11 Sept 2026, 20:57 | 2,642,365 | +5,126 |
| 9 Sept 2026, 12:20 | 2,637,239 | +7,786 |
| 6 Sept 2026, 01:15 | 2,629,453 | +7,670 |
| 4 Sept 2026, 00:02 | 2,621,783 | +9,507 |
| 2 Sept 2026, 12:25 | 2,612,276 | +2,593 |
| 1 Sept 2026, 09:56 | 2,609,683 | +8,916 |
| 31 Aug 2026, 07:35 | 2,600,767 | -1,781 |
| 30 Aug 2026, 05:45 | 2,602,548 | -2,210 |
| 29 Aug 2026, 07:19 | 2,604,758 | -1,540 |
| 28 Aug 2026, 04:18 | 2,606,298 | -1,041 |
| 27 Aug 2026, 06:54 | 2,607,339 | -1,515 |
| 26 Aug 2026, 04:15 | 2,608,854 | +3,288 |
| 25 Aug 2026, 02:34 | 2,605,566 | -5,467 |
| 23 Aug 2026, 14:27 | 2,611,033 | -3,509 |
| 21 Aug 2026, 23:47 | 2,614,542 | first reading |
51,414 posts held, back to 16 March 2020 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6,844 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 1,489 of 1,491 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 September 2026 |
|---|---|
| Posts held | 51,414 (16 March 2020 – 30 September 2026) |
| Views total | 534,826,873 |
| Reactions total | 6,336,032 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 13:56 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 30 September 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.
Measured directly from 281 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 1,370 of this channel’s own posts over the last 30 days (19 of the 24-hour readings behind this are interpolated, not measured directly): across 866 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 1.9 hours of being posted; a typical post has already reached 37.6% of its 24-hour view count within the first hour, and 78.1% within the first six; the median 24-hour reach across those posts is 388,000 views — 14.5% of this channel’s own subscriber count (90th percentile 479,600).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /7406130 Sept 2026, 13:54 UTC | 12 minutes – 2 minutes old | 14,200 views ~227 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /7406030 Sept 2026, 13:32 UTC | 220 minutes – 24 minutes old | 81,700 views ~2,732 reactions | no checkpoint reading yet | not yet at 24h | 20 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /7405930 Sept 2026, 12:46 UTC | 49 minutes – 70 minutes old | 178,000 views ~2,545 reactions | 60 minutes: 159,576 interp.still climbing at last reading | not yet at 24h | 24 minutesprovisional — final view count still climbing |
| /7405830 Sept 2026, 12:33 UTC | 510 minutes – 83 minutes old | 185,000 views ~1,984 reactions | 60 minutes: 154,385 interp.still climbing at last reading | not yet at 24h | 21 minutesprovisional — final view count still climbing |
| /7405730 Sept 2026, 12:14 UTC | 610 minutes – 1.7 hours old | 205,000 views ~3,801 reactions | 60 minutes: 158,277 interp.still climbing at last reading | not yet at 24h | 29 minutesprovisional — final view count still climbing |
| /7405630 Sept 2026, 11:54 UTC | 630 minutes – 2.0 hours old | 221,000 views ~4,242 reactions | 60 minutes: 164,000still climbing at last reading | not yet at 24h | 35 minutesprovisional — final view count still climbing |
| /7405530 Sept 2026, 11:39 UTC | 711 minutes – 2.3 hours old | 223,000 views ~4,496 reactions | 60 minutes: 150,571 interp.still climbing at last reading | not yet at 24h | 39 minutesprovisional — final view count still climbing |
| /7405330 Sept 2026, 11:20 UTC | 613 minutes – 2.1 hours old | 209,000 views ~878 reactions | 60 minutes: 139,466 interp.still climbing at last reading | not yet at 24h | 40 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
4,247,803 reactions across 997 posts, in 9 distinct kinds. The most used accounts for 20.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 859,342 | 20.2% | |
| 😡 | 765,505 | 18.0% | |
| 😁 | 564,214 | 13.3% | |
| 😢 | 558,250 | 13.1% | |
| ❤ | 499,683 | 11.8% | |
| 👍 | 395,514 | 9.31% | |
| 🔥 | 250,269 | 5.89% | |
| 👎 | 182,715 | 4.30% | |
| 🤔 | 172,311 | 4.06% |
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 998 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 4,247,803 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 8 September 2026 to 30 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @times_ukraina. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 8 September 2026 to 30 September 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.
⚡️ Момент знищення українським перехоплювачем P1-SUN JetKiller російського реактивного дрона «герань-5». Підписатися на Times of Ukraine
❤74👍74🔥63😁14😢2
❗️Кабмін просить депутатів скоротити місячні канікули на один день і вийти на роботу, щоб проголосувати за закони, які необхідні для отримання західного фінансування, — «ЕП». Підписатися на Times of Ukraine
😁1,780🤬631👍173🤔52❤34👎34😢17🔥11
❗️«Шахед» зачепився за багатоповерхівку: момент падіння дрона на Оболоні у Києві, — місцеві ЗМІ. Підписатися на Times of Ukraine
🤬1,910😢370❤108🤔67😁35👍26🔥15👎14
⚡ «Шахед» упав прямо біля дитячого майданчика на Оболоні у Києві: він дивом не здетонував, — місцеві ЗМІ. Найважливіше для жителів столиці — тут: https://t.me/+biSTx7G0-oMyZmFi Підписатися на Times of Ukraine
🤬1,430😢371❤94😁51🤔13🔥9👍8👎8
⚡️Україна почала атакувати рф реактивними БПЛА: ЗСУ нарощуватимуть удари — війна стає страшнішою, — російські пропагандисти. Підписатися на Times of Ukraine
🔥2,830❤329😁261👍202🤔77👎45🤬37😢20
⚡️Українець і росіянин разом врятували Flydubai від авіакатастрофи: вони летіли пасажирами, прорвалися до кабіни та посадили літак у Саудівській Аравії, — «Israel Hayom». Оце вже сюжет. Підписатися на Times of Ukraine
😁2,670❤658👍505🤔284🔥63👎38🤬13😢11
⚡️Зеленський — на фронті: Президент прибув на Лиманський напрямок, де зараз тривають дуже активні бойові дії. Підписатися на Times of Ukraine
❤2,380😁1,090👍424👎351🤬129🤔63🔥52😢7
⏺Загроза БПЛА — у Києві та областях, де оголошено тривогу. Жовтий рівень небезпеки, — монітори. Підписатися на Times of Ukraine
🤬709😢67❤40🔥29🤔12👎9😁7👍5
🔥Спеціальна ціна дня — 2 999 ₴! Блендер Tefal INFINY FORCE 5в1 з XL чоппером зі знижкою 45% Тільки сьогодні, 30.09, ціна 2 999 ₴ замість 5 499 ₴. Поспішайте — знижка діє один день. 💚 Rozetka. Щоразу поруч! #промо
❤177👎52😁29👍13
⚡️Готуйтеся платити більше за мобільний зв’язок: «Київстар» із 8 жовтня підвищує ціни на частину тарифів через дорожче обслуговування та відновлення мережі, — пресслужба. LOVE UA Свобода і База — 250 грн, LOVE UA Світ — 310 грн, а зі «Суперсилою Економія» — 250 грн. Підписатися на Times of Ukraine
🤬2,260👎378❤150😁137😢78👍29🤔20🔥13
⏺Ще близько 10 дронів летять на Київ та область: після ударів біля ТЕЦ-5 вже є відключення світла, а атака триває, — монітори. Підписатися на Times of Ukraine
🤬2,500😢374❤123🔥72👍41👎35😁26🤔8
⚡️Ніякої бійки між українцем і росіянином не було: нападником на борту Flydubai виявився громадянин Оману, а пораненим капітаном — громадянин ОАЕ, — «Walla». Попередньо, другий пілот поранив капітана ножем і хотів спровокувати авіакатастрофу. Підписатися на Times of Ukraine
😢1,860😁482🤔364🤬289❤165👍33🔥27👎16
Showing the 12 most recent of 51,414 posts we hold for @times_ukraina. 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.
@times_ukraina edited 286 posts 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 70 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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.
Named by 47 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@times_ukraina named 113 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
63 more handles are in this same list but not shown individually here — capped at 50.
175 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Times of Ukraine: Новини | Україна” (@times_ukraina), 2,682,623 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/times_ukraina.
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.