Channel
@blumcrypto
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
14,188,780subscribers
-1,692,299 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002039438207 |
|---|---|
| Type | Channel |
| Username | @blumcrypto |
| Description | Your easy, fun crypto trading app for buying and trading any crypto on the market. 📱 App: @Blum 🤖 Trading Bot: @BlumCryptoTradingBot 🆘 Help: @BlumSupport 💬 Chat: @BlumCrypto_Chat |
| Created | 17 January 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/blumcrypto |
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 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.
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 1 other registered channel. They sit inside a group of 7 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 |
|---|---|---|---|
| @blumcrypto_memepad/937 Dec 2024, 20:03 UTC | @blumcrypto/517 · this entry7 Dec 2024, 20:04 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @blumcrypto_memepad | 104 (8/8 hand-verifiable sample passed) | 1.00 | 4 minutes | this entry (66–38) |
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 6 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 980 comparable posts for this entry, running 20 February 2024 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.
Across the whole group of 7, the earliest publisher we hold is @blumcrypto_memepad. That is a statement about our reading window, not a claim of authorship.
On 2 of the 10 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.0038 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /135317 Sept 2026, 08:59 UTC | 12 hours | 62,500 → 73,400at least +10,800 | 177 → 186at most +10 | +41.4 |
| /135417 Sept 2026, 12:39 UTC | 12 hours | 63,800 → 82,500at least +18,600 | 424 → 433at most +10 | +71.4 |
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 keys clone_mutual · view_reaction_decoupling, last confirmed 1 October 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 6 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 16:39 | 14,188,780 | -171,221 |
| 19 Sept 2026, 04:18 | 14,360,001 | -76,503 |
| 16 Sept 2026, 17:16 | 14,436,504 | -61,130 |
| 14 Sept 2026, 19:41 | 14,497,634 | -53,876 |
| 13 Sept 2026, 04:56 | 14,551,510 | -68,507 |
| 11 Sept 2026, 09:38 | 14,620,017 | -80,849 |
| 8 Sept 2026, 17:18 | 14,700,866 | -127,482 |
| 5 Sept 2026, 09:42 | 14,828,348 | -69,410 |
| 3 Sept 2026, 16:15 | 14,897,758 | -42,904 |
| 2 Sept 2026, 08:53 | 14,940,662 | -38,111 |
| 1 Sept 2026, 11:55 | 14,978,773 | -47,593 |
| 31 Aug 2026, 09:13 | 15,026,366 | -37,520 |
| 30 Aug 2026, 12:38 | 15,063,886 | -33,257 |
| 29 Aug 2026, 13:52 | 15,097,143 | -34,325 |
| 28 Aug 2026, 15:44 | 15,131,468 | -34,084 |
| 27 Aug 2026, 17:07 | 15,165,552 | -17,078 |
| 26 Aug 2026, 16:24 | 15,182,630 | -36,305 |
| 25 Aug 2026, 14:48 | 15,218,935 | -28,301 |
| 24 Aug 2026, 17:38 | 15,247,236 | -70,636 |
| 23 Aug 2026, 00:24 | 15,317,872 | first reading |
1,180 posts held, back to 17 January 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,171 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 29 September 2026 |
|---|---|
| Posts held | 1,180 (17 January 2024 – 29 September 2026) |
| Views total | 1,317,700 |
| Reactions total | 4,159 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Oct 2026, 05:25 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. 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 10 of this channel’s own posts over the last 30 days: across 10 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2 days of being posted; a typical post has already reached 26.8% of its 24-hour view count within the first hour, and 62.4% within the first six; the median 24-hour reach across those posts is 35,950 views — 0.253% of this channel’s own subscriber count (90th percentile 39,000).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /135829 Sept 2026, 10:02 UTC | 4643 minutes – 43 hours old | 42,200 views ~198 reactions | 60 minutes: 9,198 interp. → 3.0 hours: 15,800 → 6.0 hours: 21,600 → 12 hours: 27,900 → 24 hours: 34,200still climbing at last reading | 34,200measured | 5.8 hours |
| /135728 Sept 2026, 13:40 UTC | 679 minutes – 3 days old | 55,200 views ~205 reactions | 60 minutes: 10,517 interp. → 3.0 hours: 18,200 → 6.0 hours: 24,000 → 12 hours: 28,200 → 24 hours: 40,800 → 2 days: 51,000still climbing at last reading | 40,800measured | 11 hours |
| /135625 Sept 2026, 07:33 UTC | 14411 minutes – 6 days old | 90,300 views ~288 reactions | 60 minutes: 9,150 → 3.0 hours: 15,626 interp. → 6.0 hours: 21,500 → 12 hours: 28,600 → 24 hours: 33,900 → 2 days: 43,700still climbing at last reading | 33,900measured | 2 days |
| /135417 Sept 2026, 12:39 UTC | 7125 minutes – 7 days old | 98,600 views ~463 reactions | 60 minutes: 9,920 → 3.0 hours: 16,671 interp. → 6.0 hours: 22,500 → 12 hours: 27,200 → 24 hours: 34,900 → 2 days: 44,300 → 7 days: 98,000still climbing at last reading | 34,900measured | 3 days |
| /135317 Sept 2026, 08:59 UTC | 7516 minutes – 7 days old | 84,400 views ~199 reactions | 60 minutes: 9,520 → 3.0 hours: 16,500 → 6.0 hours: 25,000 → 12 hours: 32,300 → 24 hours: 37,800 → 2 days: 46,100 → 7 days: 81,300still climbing at last reading | 37,800measured | 33 hours |
| /135215 Sept 2026, 08:14 UTC | 12436 minutes – 9 days old | 96,500 views ~339 reactions | 60 minutes: 9,530 interp. → 3.0 hours: 16,309 interp. → 6.0 hours: 21,700 → 12 hours: 29,700 → 24 hours: 35,600 → 2 days: 45,900 → 7 days: 78,400still climbing at last reading | 35,600measured | 2 days |
| /135112 Sept 2026, 09:02 UTC | 1673 minutes – 7 days old | 103,000 views ~462 reactions | 60 minutes: 8,970 → 3.0 hours: 15,401 interp. → 6.0 hours: 21,300 → 12 hours: 28,700 → 24 hours: 34,800 → 2 days: 46,200 → 7 days: 103,000still climbing at last reading | 34,800measured | 2 days |
| /135010 Sept 2026, 05:57 UTC | 17455 minutes – 7 days old | 98,400 views ~392 reactions | 60 minutes: 8,899 interp. → 3.0 hours: 16,100 → 6.0 hours: 22,400 → 12 hours: 30,300 → 24 hours: 36,300 → 2 days: 46,800 → 7 days: 98,200still climbing at last reading | 36,300measured | 2 days |
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.
16,560 reactions across 37 posts, in 4 distinct kinds. The most used accounts for 48.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8,099 | 48.9% | |
| custom 5350746136544037083 | 4,778 | 28.9% | |
| 🔥 | 2,102 | 12.7% | |
| 🥰 | 1,581 | 9.55% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 958 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 19,401,250 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 5 July 2024 to 29 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 @blumcrypto. 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 5 July 2024 to 29 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.
🧩 Can You Guess The Token? It started with meme energy. It has a very recognizable four-legged mascot. And somewhere along the way, it grew into a whole Web3 ecosystem. Definitely not just a cute face anymore 👀 🔍 Reveal the answer
❤106custom 535074613654403708364🔥27🥰1
📆 Last Monday Of September. Another month almost down. Three days still left for something completely unnecessary to happen. 👀 September was always full of surprises 👉 Catch the end-of-month action
❤115custom 535074613654403708351🔥24🥰15
🌤 Weekend’s Around The Corner — Here’s Your Forecast Sleep: maybe. Plans: questionable. Charts: definitely open. Memepad: somehow involved. Looks like a normal weekend to us 😭
❤156custom 535074613654403708374🥰30🔥28
🔥 Things Are Getting Hot Again. The Hot section has a fresh batch of tokens fighting for your attention 👀 No need for a list this time. 👉 Open Memepad and see what made the cut
❤220custom 535074613654403708371🥰34🔥26
Dear community, including participants of the Early (Notcoin) and Blum Quest programs, we have some news. And yes — it’s about wallets again 🙈 We know that many of you appreciate XDAO not only for the product, but also for our sense of humor. So today, we have a small continuation of a familiar topic: we’ll need one more wallet — this time on Arbitrum. But don’t panic just yet — it’s not as scary as it sounds 😎 🔵 W…
❤227custom 5350746136544037083134🔥69🥰67
🏦 Yesterday: FOMC. 🌱 Meanwhile On Memepad: Fed decisions? Interest rates? Dot plots? Some token creator with a frog as its logo: “Cool. Anyway… let me see how's my token doing on Memepad” 👨🍳
custom 535074613654403708392❤80🔥31🥰29
🔮 Your Crypto Horoscope For This Week ♈ Aries – buys before reading the ticker. ♉ Taurus – still waiting for a better entry. ♊ Gemini – bullish and bearish at the same time. ♋ Cancer – emotionally attached to the bag. ♌ Leo – tells the group chat after it pumps. The rest? Probably somewhere on Memepad 👀
❤199custom 535074613654403708372🥰51🔥44
🧩 Can You Guess What’s Behind This Chart? Not a meme. Not a cartoon character. This one actually starts on the factory floor. Not exactly your average token origin story 👀 🔍 Reveal the answer
❤257🔥92custom 535074613654403708387🥰74
Some Tokens Have Utility. Some Have Lore. Some Just Have A Funny Picture. And somehow, all three can end up on Memepad. The hard part is pretending you only came to check one 😭 👉 See all on Memepad
❤178custom 5350746136544037083145🔥66🥰49
🫡 Back From Our Touch-Grass Session. Grass – touched. Sleep – acquired. Charts – probably did something while we were gone. Anyway, Memepad was waiting for us 👀 😎 Time to catch up
custom 5350746136544037083150❤134🔥51🥰37
🍂 New Season. Same Degens. The leaves are about to turn red. Hopefully our charts have other plans 👀 Either way, Memepad season never really ends. 👉 See what’s cooking on Memepad
❤316custom 5350746136544037083164🔥119🥰103
🧩 Guess The Token He’s got questionable inventions. A complicated relationship with a certain semi-aquatic animal. And enough backstory to explain absolutely everything. Looks like his plans extend beyond the Tri-State Area 👀 🔎 Know who we’re talking about?
❤369custom 5350746136544037083148🔥120🥰108
Showing the 12 most recent of 1,180 posts we hold for @blumcrypto. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 117 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 185 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 23 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.
@blumcrypto named 15 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.
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 7 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 4,120 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.
26 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Blum: All Crypto – One App” (@blumcrypto), 14,188,780 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/blumcrypto.
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.