6 measurements spanning 22 days, net -2. 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 997–1,004 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 02:04
1,001
+2
22 Aug 2026, 23:59
999
+1
14 Aug 2026, 16:48
998
-4
11 Aug 2026, 17:42
1,002
-1
8 Aug 2026, 00:34
1,003
no change
7 Aug 2026, 17:58
1,003
first reading
Engagement
20 posts held, back to 13 April 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
19.0%
avg views ÷ 1,001 subscribers
Avg views / post
190
1 post measured
Reaction rate
2.11%
reactions ÷ views · ER floor
Posts in window
1
of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 August 2026
Posts held
20 (13 April 2026 – 3 August 2026)
Views total
190
Reactions total
4
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 00:34 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.
Reaction mix
95 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 95.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
91
95.8%
custom 5963270299007849542
4
4.21%
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 isTelegram’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 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 95reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 April 2026 to 3 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
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @keyrockinsights. 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 20 most recent posts we hold for this entry, published 13 April 2026 to 3 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.
Key Insights (3 August 2026): The Hold Nobody Bought
The AI Bond Tab
The Fed held at 3.50% to 3.75% on 29 July in a 9-3 vote, its widest split in years with three dissenters pushing for a hike, and while the market pulled its rate-hike bets back from a 73% peak to 66%, the reprieve never reached risk.
Shorter-dated yields fell with those bets while the long end went the other way, the 30-year climbing to a 19-year…
Keyrock Insights (27 July 2026): Oil Revives the Hike
Bitcoin held its footing this week through an oil-driven inflation scare that lifted Treasury yields to one-year highs and revived Fed hike bets, while the mega-cap AI trade took the damage. Brent spiked above $100 midweek for the first time since May as Iran's closure of the Strait of Hormuz and Houthi strikes in the Red Sea hit both export routes at once, befor…
Key Insights (20 July 2026): Bitcoin Breaks Its Beta
Bitcoin Breaks Its Beta
Bitcoin pulled away from equities this week, closing +1.63% while the NDX 100 fell -4.13%, gold slipped -0.99% and the dollar drifted -0.32%. A soft June inflation week that should have lifted risk instead saw duration sensitive tech sell off while Bitcoin firmed. Headline CPI printed 3.5% YoY against a ~3.8% consensus and prices fell -0.4…
Key Insights (13 July 2026): Geopolitics Rewrites Relief
Hike Odds Hold
Risk assets gave back last week's relief as Middle East tensions resurfaced and hawkish Fed minutes put inflation risk back on the table. Bitcoin slipped about 1% to $63k and gold fell 2.5% after both bounced into the July 4 jobs miss, while the Nasdaq still added 1.7% as chips recovered. The dollar firmed modestly, ending the post-payrolls sof…
Key Insights (6 July 2026): Hike Odds Fade
Jobs Miss Lifts Market
June payrolls badly missed at 57,000 jobs against consensus near 110,000, and the September hike trade faded with it. Bitcoin and gold recovered together as the dollar eased, reversing last week's joint selloff into hot May PCE. FedWatch now prices roughly a 55% chance of a September hike, down from 64% before the release and near 80% last week. Wars…
Our latest report is here.
Co-published with Bitso and featuring insights from Dune, Ripple, Qivalis, Bridge, and Mirae Asset, we track local stablecoins across the four stages of their lifecycle, from centralised exchanges through to onchain pools.
Stablecoins have meant dollars, but the local ones have grown up. Non-USD supply has grown 50× since 2020 to $2.2B, and the dollar's share of fiat-to-stablecoin trading…
Key Insights (29 June 2026): No Refuge
Nowhere To Hide
The hottest inflation print in three years landed this week and the market shrugged it off. May PCE ran above 4%, but with oil already sliding back to pre-conflict levels as Hormuz reopened, the curve read it as the peak and yields fell across the board. Gold and Bitcoin both sold off into the highest inflation reading since 2023, which only fits if the geopoli…
Key Insights (22 June 2026): The Narrow Bid
SpaceX Lifts Off
A hawkish Fed split the cross-asset tape, with the Nasdaq rising 2.60% on resilient growth while Bitcoin fell 2.70%, gold dropped 3.00% and the dollar gained 1.42%, as risk equities powered through a higher-for-longer Fed and the macro hedges took the hit. SpaceX's record $75b IPO, the largest in history at a ~$1.77t valuation, captured the selective AI a…
Key Insights (15 June 2026): Parking The Bus
Risk Rallies into FOMC
Risk assets rallied through an inflation challenge this week, with the NDX up 2.34%, Bitcoin climbing 4.58% and the dollar softening as DXY fell 0.59%, while gold was flat at +0.66%. The data ran hot on the surface, but markets read the details as dovish. May CPI jumped to a three-year-high 4.2% YoY yet core was a soft 0.2%, and the genuine shock w…
Michael Saylor’s Strategy playbook doesn’t work in Europe.
Without deep convertible bond markets, perpetual preferred shares, or a unified exchange ecosystem, European Bitcoin Treasury Companies are forging a different path.
Our latest report explores how capital markets innovation, strategic M&A, and competitive attrition are creating a new generation of national Bitcoin champions.
Featuring exclusive insight fro…
Key Insights (8 June 2026): The Hawkish Repricing
Hawkish Reset
This week saw a hawkish data shock that led to a risk-off setup. BTC declined 14.20%, having broken $60K intraday for the first time since late 2024. The NDX was down 4.53%, ending a nine week run of consecutive gains, while Gold failed to provide a safe haven bid, down 4.87% on the week. DXY, up 1.11%, took the flow instead. The driver was the May NFP…
Key Insights (1 June 2025): Silence of the Vols
Hedge Basket Unwinds
The inflation-hedge trade came apart last week. A softer April PCE pulled the hawkish bid out of the long end, and the basket that had run since the April CPI shock sold at once, gold and Bitcoin falling together while equities took the duration relief. Bitcoin dropped about 5% to $73k on a ninth straight day of ETF outflows while the Nasdaq added…
🔥4
Showing the 12 most recent of 20 posts we hold for @keyrockinsights. 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.
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“Keyrock Insights 📊” (@keyrockinsights), 1,001 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/keyrockinsights.
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.