Telegram RegisterThe public register of Telegram

Channel

Lord Belgrave

@lordbelgrave

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

4,705subscribers

+36 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002743558741
TypeChannel
Username@lordbelgrave
CreatedBetween 1 June 2025 and 18 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/lordbelgrave

Growth

4,6694,7054,6876 August 2026 — 4,669 subscribers7 August 2026 — 4,676 subscribers10 August 2026 — 4,702 subscribers13 August 2026 — 4,705 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +36. 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 4,664–4,710 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:354,705+3
10 Aug 2026, 10:514,702+26
7 Aug 2026, 10:164,676+7
6 Aug 2026, 16:154,669first reading

Engagement

20 posts held, back to 18 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
73.5%
avg views ÷ 4,705 subscribers
Avg views / post
3,460
1 post measured
Reaction rate
6.97%
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
WindowRolling 30 days · latest post in window 1 August 2026
Posts held20 (18 September 20251 August 2026)
Views total3,460
Reactions total241
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:28 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

4,417 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 38.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,71338.8%
1,17226.5%
👍68515.5%
💯2595.86%
🤯1763.98%
🫡1343.03%
🙏932.11%
👏681.54%
🤝200.453%
150.34%
🏆150.34%
😁150.34%
🤩140.317%
🎉130.294%
👌110.249%
😎70.158%
🤗70.158%

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 4,417reactions 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 18 September 2025 to 1 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.

Recent posts

1 Aug 2026, 19:02 UTC≈3,460 views241 reactionsread 12 August 2026
Photo

Photo, posted without a caption

🔥109🤯3628🙏18👍17🫡9💯7🤝7

10 Feb 2026, 18:03 UTC≈8,760 views267 reactionsread 12 August 2026

In 2016, I worked on NDA drafts and briefing materials where banks and government stakeholders were already discussing the long term implications of quantum computing. The concern was specific and technical. Public and private key cryptography, as it underpins most blockchains today, was understood to be vulnerable once quantum capability reached a certain threshold. There were structured papers outlining attack sur

🔥12069👍59🤯8💯5😁5🫡1

20 Jan 2026, 18:08 UTC≈10,100 views256 reactionsread 12 August 2026

I’m going to be direct, because this is one of those moments people only understand in hindsight. This year at the World Economic Forum, decisions will be shaped behind closed doors that materially affect the future of finance, identity, and economic participation. These are not public panels or headline sessions. They are private working discussions. The dominant themes are not price, speculation, or market cycles

91👍66🔥49💯22🙏14🤯10👏3🫡1

10 Jan 2026, 21:06 UTC≈9,080 views263 reactionsread 12 August 2026

From first hand experience, the current U.S. administration is laying the groundwork to insure digital asset custody in a manner comparable to traditional bank deposits, with protection up to a defined limit. This is not a theory and it is not exploratory chatter. It is an active policy track. Once this framework is in place, institutional crypto custody stops being a gray area. It becomes a regulated, risk mitigate

🔥10058👍55💯20👏12🤯6🎉4🫡4

26 Dec 2025, 20:19 UTC≈8,510 views269 reactionsread 12 August 2026

At one point in my life, I was personally close to someone whose professional role was to record the official minutes of meetings involving senior executives from central banks and the largest commercial banks. These were formal sessions. Nothing casual. Every statement was intentional and every conclusion documented. Those rooms were where future financial infrastructure was shaped quietly. Through that proximity,

114🔥60👍26🫡21🙏17💯15🏆9😁5

19 Dec 2025, 19:59 UTC≈7,250 views231 reactionsread 12 August 2026

Nobody is supposed to know this. But as promised, I am sharing this with you. And I need to be precise in how I say it. From what I witnessed over the years, Ripple’s escrow was never intended to represent loose corporate ownership waiting to be sold into the market. It was engineered with intent. Locked supply. Deterministic release schedules. Multi year horizons aligned to institutional readiness rather than spec

🔥10452👍30💯23🤯11🙏6🏆3🤩2

10 Dec 2025, 17:49 UTC≈7,090 views257 reactionsread 12 August 2026

I need to choose my words carefully here. What I am about to describe comes from a meeting in Brussels between senior bankers and EU policy makers that was intended to remain highly confidential. I am sharing this with you in principle, not as a disclosure of protected documents, but because the direction of travel is now impossible to ignore. The Digital Euro is being designed for full on chain trade finance. This

🔥11475👍45🤯23

7 Dec 2025, 18:34 UTC≈5,800 views155 reactionsread 12 August 2026

Anyone who has spent time around Brussels knows that the European policy landscape has its flaws. The EU has faced several documented corruption scandals, including recent cases involving improper influence, foreign lobbying pressure, and undisclosed financial incentives. These incidents are public record and speak to a structural vulnerability within the system rather than isolated missteps. Years ago, during an of

58🔥47👍36💯4🤯43😁3

5 Dec 2025, 17:43 UTC≈5,280 views161 reactionsread 12 August 2026

In 2019 I sat in a closed meeting in London that I will never forget. It was held in a private consultation room at the Bank of England’s Threadneedle Street complex. Present were senior representatives from Barclays, Santander, Deutsche Bank, BNP Paribas, and a policy advisor from the ECB’s Directorate General for Market Infrastructure. Ripple’s institutional strategy team was also in attendance. The discussion foc

🔥8435👍26🤯9👏4🤗2😁1

29 Nov 2025, 19:01 UTC≈5,860 views216 reactionsread 12 August 2026

I still remember the moment clearly. It was a brief window during a review session in a secure room at a European headquarters in Amsterdam. Two major institutions were involved, ING and BNP Paribas. Both had internal teams working on next generation settlement architecture. I was invited to observe a portion of their analysis for alignment with our own cross border strategy. For a few minutes I was able to scan a s

🔥10056👍36👏9🤯73👌3🫡2

15 Nov 2025, 19:33 UTC≈5,830 views199 reactionsread 12 August 2026

Warren Buffett is sitting on an unprecedented cash position, waiting for assets that can absorb size, deliver efficiency, and operate in a market that is becoming increasingly digital and global. A portion of that capital will eventually migrate toward the new settlement infrastructure being built. XRP is one of the few assets that can handle institutional scale, real liquidity demands, and real utility. When the n

🔥8551👍36🤯8🫡8🤩6💯5

8 Nov 2025, 15:45 UTC≈7,070 views258 reactionsread 12 August 2026

Several years ago in London, I reviewed a confidential report circulated among senior executives from Barclays, HSBC, Standard Chartered, and Lloyds. The meeting took place in a private conference suite at The Langham, away from the usual corporate setting, with representatives and observers linked to the Bank of England’s innovation office. The core problem was not liquidity itself but friction. Value moves across

112🔥62💯35👍27🫡11👏6😎5

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

Citation-graph rank

Citation-graph rank — 234,593 of 1,345,403entries 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 10 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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Lord Belgrave” (@lordbelgrave), 4,705 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lordbelgrave.

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.