VIP Members Play in a Different League 😈
☃633👻290🦄201🎄188🎃165

Channel
@lenvies
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,562,601subscribers
-115,376 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002181004288 |
|---|---|
| Type | Channel |
| Username | @lenvies |
| Description | 🔒 Exclusive meme coin calls & early alpha. Hidden gems Whale moves High-conviction plays 👑 𝐅𝐨𝐮𝐧𝐝𝐞𝐫 — @TradersHayzon 🤝 𝐀𝐝𝐬 & 𝐏𝐚𝐫𝐭𝐧𝐞𝐫𝐬𝐡𝐢𝐩𝐬 — @HAYZON_Contacts 💎 𝐕𝐈𝐏 𝐀𝐜𝐜𝐞𝐬𝐬 — @CryptoPR_Network |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/lenvies |
Crypto & trading — 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.
On 33 of the 34 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0280 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /251812 Sept 2026, 10:22 UTC | 33 minutes | 8,220 → 13,100at least +4,780 | 427 → 427at most +1 | +134.0 |
| /251812 Sept 2026, 10:22 UTC | 30 minutes | 13,900 → 16,700at least +2,700 | 470 → 470at most +1 | +75.7 |
| /251812 Sept 2026, 10:22 UTC | 35 minutes | 18,800 → 23,100at least +4,200 | 469 → 469at most +1 | +117.7 |
| /251812 Sept 2026, 10:22 UTC | 55 minutes | 23,100 → 27,100at least +3,900 | 469 → 469at most +1 | +109.3 |
| /251812 Sept 2026, 10:22 UTC | 42 hours | 29,900 → 37,100at least +7,100 | 466 → 464at most +-1 | +199.1 |
| /252412 Sept 2026, 17:27 UTC | 30 minutes | 5,930 → 7,460at least +1,520 | 584 → 584at most +1 | +42.6 |
| /252412 Sept 2026, 17:27 UTC | 3.2 hours | 8,200 → 9,980at least +1,770 | 583 → 583at most +1 | +49.6 |
| /252412 Sept 2026, 17:27 UTC | 30 minutes | 9,980 → 11,700at least +1,620 | 583 → 583at most +1 | +45.4 |
| /252412 Sept 2026, 17:27 UTC | 35 minutes | 11,700 → 13,900at least +2,100 | 583 → 582at most +0 | +58.9 |
| /252412 Sept 2026, 17:27 UTC | 47 hours | 22,700 → 38,200at least +15,400 | 582 → 582at most +1 | +431.7 |
| /253212 Sept 2026, 18:58 UTC | 30 minutes | 5,890 → 6,790at least +890 | 647 → 647at most +1 | +25.0 |
| /253212 Sept 2026, 18:58 UTC | 30 minutes | 6,790 → 10,100at least +3,210 | 647 → 647at most +1 | +90.0 |
| /253212 Sept 2026, 18:58 UTC | 37 minutes | 10,100 → 11,900at least +1,700 | 647 → 647at most +1 | +47.7 |
| /253212 Sept 2026, 18:58 UTC | 35 minutes | 12,800 → 16,400at least +3,500 | 648 → 648at most +1 | +98.1 |
| /248629 Aug 2026, 00:14 UTC | 30 minutes | 13,100 → 24,400at least +11,200 | 977 → 1,007at most +40 | +314.0 |
| /248629 Aug 2026, 00:14 UTC | 31 minutes | 25,000 → 30,500at least +5,400 | 1,007 → 1,007at most +10 | +151.4 |
| /248629 Aug 2026, 00:14 UTC | 55 minutes | 32,600 → 39,800at least +7,100 | 1,007 → 1,007at most +10 | +199.1 |
| /248729 Aug 2026, 00:14 UTC | 30 minutes | 14,100 → 24,400at least +10,200 | 868 → 874at most +7 | +286.0 |
| /248729 Aug 2026, 00:14 UTC | 31 minutes | 25,000 → 30,800at least +5,700 | 874 → 874at most +1 | +159.8 |
| /248729 Aug 2026, 00:14 UTC | 55 minutes | 32,500 → 40,000at least +7,400 | 874 → 874at most +1 | +207.5 |
| /248829 Aug 2026, 00:18 UTC | 30 minutes | 13,100 → 24,400at least +11,200 | 2,187 → 2,215at most +38 | +314.0 |
| /248829 Aug 2026, 00:18 UTC | 31 minutes | 24,900 → 31,400at least +6,400 | 2,215 → 2,215at most +10 | +179.4 |
| /248829 Aug 2026, 00:18 UTC | 55 minutes | 33,000 → 40,500at least +7,400 | 2,215 → 2,215at most +10 | +207.5 |
| /249329 Aug 2026, 00:41 UTC | 30 minutes | 14,000 → 24,300at least +10,200 | 1,115 → 1,126at most +21 | +286.0 |
| /249329 Aug 2026, 00:41 UTC | 31 minutes | 24,900 → 30,000at least +5,000 | 1,127 → 1,127at most +10 | +140.2 |
| /249329 Aug 2026, 00:41 UTC | 55 minutes | 31,600 → 39,400at least +7,700 | 1,127 → 1,127at most +10 | +215.9 |
| /251912 Sept 2026, 10:36 UTC | 33 minutes | 5,720 → 16,200at least +10,380 | 425 → 425at most +1 | +291.0 |
| /251912 Sept 2026, 10:36 UTC | 30 minutes | 17,400 → 25,800at least +8,300 | 437 → 437at most +1 | +232.7 |
| /251912 Sept 2026, 10:36 UTC | 37 minutes | 25,800 → 30,300at least +4,400 | 437 → 437at most +1 | +123.4 |
| /252512 Sept 2026, 17:52 UTC | 2.7 hours | 5,210 → 6,040at least +820 | 799 → 799at most +1 | +23.0 |
| /252512 Sept 2026, 17:52 UTC | 30 minutes | 6,040 → 7,970at least +1,920 | 799 → 799at most +1 | +53.8 |
| /252512 Sept 2026, 17:52 UTC | 7 days | 19,300 → 29,200at least +9,800 | 796 → 796at most +1 | +274.7 |
| /253417 Sept 2026, 15:40 UTC | 36 minutes | 6,430 → 8,460at least +2,020 | 729 → 729at most +1 | +56.6 |
| /253417 Sept 2026, 15:40 UTC | 34 minutes | 8,460 → 12,600at least +4,040 | 729 → 729at most +1 | +113.3 |
| /253417 Sept 2026, 15:40 UTC | 34 minutes | 13,500 → 23,400at least +9,800 | 729 → 729at most +1 | +274.7 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 24 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:39 | 1,562,601 | -7,239 |
| 16 Sept 2026, 07:16 | 1,569,840 | -2,978 |
| 14 Sept 2026, 11:57 | 1,572,818 | -4,012 |
| 13 Sept 2026, 00:57 | 1,576,830 | -6,229 |
| 11 Sept 2026, 04:58 | 1,583,059 | -6,029 |
| 8 Sept 2026, 11:16 | 1,589,088 | -10,617 |
| 5 Sept 2026, 03:38 | 1,599,705 | -4,360 |
| 3 Sept 2026, 12:20 | 1,604,065 | -3,912 |
| 2 Sept 2026, 07:46 | 1,607,977 | -2,912 |
| 1 Sept 2026, 06:27 | 1,610,889 | -2,660 |
| 31 Aug 2026, 07:22 | 1,613,549 | -4,137 |
| 30 Aug 2026, 10:13 | 1,617,686 | -2,413 |
| 29 Aug 2026, 06:44 | 1,620,099 | -2,852 |
| 28 Aug 2026, 07:25 | 1,622,951 | -2,376 |
| 27 Aug 2026, 09:05 | 1,625,327 | -2,103 |
| 26 Aug 2026, 12:25 | 1,627,430 | -1,640 |
| 25 Aug 2026, 12:03 | 1,629,070 | -3,082 |
| 24 Aug 2026, 09:36 | 1,632,152 | -5,038 |
| 22 Aug 2026, 20:33 | 1,637,190 | -4,211 |
| 21 Aug 2026, 10:05 | 1,641,401 | first reading |
73 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 106 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.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 73 (3 August 2026 – 22 September 2026) |
| Views total | 1,280,050 |
| Reactions total | 43,909 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 03:00 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 26 September 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.
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 34 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 33 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 8.7 hours of being posted; a typical post has already reached 28.1% of its 24-hour view count within the first hour, and 95.5% within the first six; the median 24-hour reach across those posts is 15,950 views — 1.02% of this channel’s own subscriber count (90th percentile 39,970).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /254517 Sept 2026, 19:14 UTC | 6112 minutes – 7 days old | 28,600 views ~1,367 reactions | 60 minutes: 8,595 interp. → 3.0 hours: 8,910 → 6.0 hours: 8,983 interp. → 12 hours: 9,100 → 24 hours: 27,600 → 2 days: 27,800 → 7 days: 28,600views have flattened out | 27,600measured | 20 hours |
| /254417 Sept 2026, 18:52 UTC | 7934 minutes – 7 days old | 28,400 views ~1,094 reactions | 60 minutes: 6,065 interp. → 3.0 hours: 7,604 interp. → 6.0 hours: 7,670 → 12 hours: 7,750 → 24 hours: 15,900 → 2 days: 27,900 → 7 days: 28,400views have flattened out | 15,900measured | 23 hours |
| /254317 Sept 2026, 18:48 UTC | 812 minutes – 7 days old | 28,200 views ~543 reactions | 60 minutes: 5,866 interp. → 3.0 hours: 7,630 → 6.0 hours: 7,660 → 12 hours: 7,730 → 24 hours: 16,000 → 2 days: 27,800 → 7 days: 28,200views have flattened out | 16,000measured | 23 hours |
| /254217 Sept 2026, 18:47 UTC | 583 minutes – 7 days old | 20,200 views ~833 reactions | 60 minutes: 5,768 interp. → 3.0 hours: 7,650 → 6.0 hours: 7,680 → 12 hours: 7,730 → 24 hours: 19,900 → 2 days: 19,900 → 7 days: 20,200views have flattened out | 19,900measured | 21 hours |
| /253717 Sept 2026, 16:06 UTC | 5933 minutes – 7 days old | 34,100 views ~944 reactions | 60 minutes: 8,731 interp. → 3.0 hours: 10,672 interp. → 6.0 hours: 19,900 → 12 hours: 19,900 → 24 hours: 33,800 → 2 days: 33,800 → 7 days: 34,100views have flattened out | 33,800measured | 3.7 hours |
| /253617 Sept 2026, 15:48 UTC | 8216 minutes – 7 days old | 32,100 views ~1,837 reactions | 60 minutes: 5,266 interp. → 3.0 hours: 5,380 → 6.0 hours: 11,900 → 12 hours: 12,000 → 24 hours: 12,100 → 2 days: 32,000 → 7 days: 32,100still climbing at last reading | 12,100measured | 25 hours |
| /253517 Sept 2026, 15:43 UTC | 8222 minutes – 7 days old | 32,900 views ~495 reactions | 60 minutes: 6,318 interp. → 3.0 hours: 6,440 → 6.0 hours: 12,600 → 12 hours: 12,700 → 24 hours: 12,800 → 2 days: 32,700 → 7 days: 32,900still climbing at last reading | 12,800measured | 25 hours |
| /253417 Sept 2026, 15:40 UTC | 5625 minutes – 7 days old | 23,700 views ~724 reactions | 60 minutes: 6,220 → 3.0 hours: 6,424 interp. → 6.0 hours: 12,600 → 12 hours: 12,700 → 24 hours: 13,500 → 2 days: 23,500 → 7 days: 23,700still climbing at last reading | 13,500measured | 4.2 hours |
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.
75,780 reactions across 72 posts, in 5 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🦄 | 17,772 | 23.5% | |
| 🎄 | 16,989 | 22.4% | |
| ☃ | 14,340 | 18.9% | |
| 🎃 | 13,873 | 18.3% | |
| 👻 | 12,806 | 16.9% |
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 72 of the 73 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 75,780 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 73 most recent posts we hold, published 3 August 2026 to 22 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 @lenvies. 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 73 most recent posts we hold for this entry, published 3 August 2026 to 22 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.
VIP Members Play in a Different League 😈
☃633👻290🦄201🎄188🎃165
🧬 Token: $CASHTAG Dyor 📈 Entry Market Cap: 95K ⚠️ Stoploss: 80K Enhuu882mnhTtM7bGwAUG5GzgdDUcyjtL2uqQTxgpump Private Alpha VIP 🪙
☃152🎄100🦄90🎃75👻48
💪
☃364🎃171🦄116🎄79👻72
$AWARDED - 13X from Our Private Call MC: 55K —→ 700K 💵 $50 → $622$ Another winning call from Private Alpha.
🎄146☃108👻63🎃54🦄30
VIP Forward — Shared for Winning Call Proof Only 🧬 Token: $AWARDED 📈 Entry Market Cap: 55K Contract Address: 5wZDE8f5uKHbVaHAyz84Lgz7xefAkCpvcwoWYaRCrfn Private Alpha VIP 🪙
☃253🎄252👻169🎃129🦄46
VIP Member Show Profit 💸 Private Alpha.
🎃728🎄297☃188🦄100👻54
🥇
🎄542☃280🎃184🦄64👻24
$SEND - 13X from Our Private Call MC: 78K —→ 1M 💵 $50 → $671$ Another winning call from Private Alpha.
🎃265🦄111☃84🎄54👻29
VIP Forward — Shared for Winning Call Proof Only 🧬 Token: $SEND 📈 Entry Market Cap: 78K Contract Address: 2XuQnYQ1q3oTjPL9j4PfhV1AEqcZ6Hq2PzPzuxaASEND Private Alpha VIP 🪙
🎃360🦄240☃143🎄54👻36
TOP 5 PROFITS
☃360🦄263🎄195👻74🎃52
💪
👻779🦄541☃276🎃174🎄67
$WISH - 30.5X from Our Private Call MC: 39K —→ 1.2M 💵 $50 → $1392$ Another winning call from Private Alpha.
👻174🦄107🎃97☃73🎄44
Showing the 12 most recent of 73 posts we hold for @lenvies. 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.
@lenvies edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 289 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
One domain 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Private Alpha” (@lenvies), 1,562,601 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lenvies.
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.