4 measurements spanning 3 days, net -4. 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 2,302–2,308 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 19:18
2,303
-1
7 Aug 2026, 14:55
2,304
-3
7 Aug 2026, 10:31
2,307
no change
7 Aug 2026, 10:27
2,307
first reading
Engagement
20 posts held, back to 3 February 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
1.97%
avg views ÷ 2,303 subscribers
Avg views / post
45.4
5 posts measured
Reaction rate
2.44%
reactions ÷ views · ER floor
Posts in window
5
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. It is computed over the 2 of 5 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 30 July 2026
Posts held
20 (3 February 2025 – 30 July 2026)
Views total
227
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:41 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
362 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 24.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
90
24.9%
🔥
78
21.5%
💯
47
13.0%
🐳
45
12.4%
👌
41
11.3%
❤🔥
25
6.91%
🙏
22
6.08%
👏
7
1.93%
❤
5
1.38%
🏆
1
0.276%
🤔
1
0.276%
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 14 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 362reactions 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 3 February 2025 to 30 July 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.
Uniswap v4 protocol fee rollout sparks LP-earnings dispute; UNI rebounds 5–8% – Link
Following governance approval to activate protocol fees across seven chains, Uniswap founder Hayden Adams pushed back on claims that the new v4 fee structure cuts LP earnings by up to 33%, calling the criticism FUD. UNI price rebounded roughly 5-8% intraday to reclaim the $4 level.
Matters because: The fee debate could affect liqui…
One habit that’s improved how I discover opportunities is tracking what’s already gaining real onchain attention..
Which is why i’ve been using the Trending feature on the Moby app
To spot tokens with healthy volume, growing activity, and genuine momentum before they become everyone’s timeline topic.
I was also glad to see @KyberNetwork bring a similar feature to KyberSwap
And that means you don’t have to ape eve…
Paybox Revoke Checklist 📄
1. Remove PayBox from Claude
- Open Claude → Customize → Connectors
- Find the PayBox custom connector
- Click Disconnect, Remove, or the three dots → Remove
2. Remove PayBox from ChatGPT
- Open the ChatGPT account you used
- Go to Settings → Apps/Plugins
- Find PayBox → Disconnect/Delete
- Remove the custom PayBox plugin/MCP server if you added it manually
3. Revoke Google access
- Go to…
Pick up your free money.
If you've ever used ChatGPT or Claude, you're eligible to claim a reward. I've seen people receive $600+, and it takes less than 2 minutes.
1) Go to paybox.sh
2) Follow the four steps on the website (see video)
3) Connect your X account
4) Claim your reward
https://x.com/moonpay/status/2082459328208839074?s=46&t=1kCFjcyzNnAumOhaMjv36A
Heard of Arcus yet ?
One of the very first leading Dex on RobinHood chain
This will definitely cook I assure you!
Join waitlist here, more instructions on how to farm it soon
https://waitlist.arcus.xyz/s/DILLION
See you on the side that prints 🖤
I’m guessing the past few months has made quite a number of users to quit or take a break from the space
But I just wanna let y’all know that, the next cycle has already begun
And it’s simply right in our eyes, I’ve seen some, which I can tell you that it’s all about to blow up again
Want me to shed more lights on that ??
Sweet alpha incoming from @KyberNetwork 🫵
They just dropped a new incentive and trust me, this is not something you want to sleep on
547,000 $WMON sitting in a FairFlow pool right now, the previous pools like this got milked fast
Window: April 6 → April 20, still open
Liquidity providers can also earn across multiple yield sources simultaneously:
➲ LP fees
➲ EG rewards
➲ WMON incentives
That's not longer one st…
Active MCap of RWAs just surpassed $16B for the first time.
On our RWA dashboard, we differentiate between Onchain MCap (total market cap of an asset onchain) and Active MCap (the portion of those assets deployed in DeFi or distributed outside the issuer's wallets).
I’m pretty sure that you’ve watched people lose everything to a single hack!
One wrong click, one compromised hot wallet and every single thing is gone…
That’s not a happy story you would want to be telling everyone innit ?
So here’s an alternative 👇
The team at KyberSwap just partnered with SafePal to make sure you never have to be such a position
The partnership also came with :
⇢ 4,000 free X1 hardware wal…
This is exactly why I said that $70K–$71K / gray band mattered.
We got the first weekly close below the band (around $70,800), and now we’re staring at a second close below it.
If this week prints red again, that’s 5 red weekly closes in a row and we haven’t seen five straight red weeks since 2022, right before BTC dumped -38% (from $48,300 → $25,400).
Thats the market telling you momentum is still bleeding out.
…
We just opened our official Kol deal channel
Form closes in the next 24 hours
Fill up the form quickly : https://forms.gle/utXq6NFowvUo5xNs7
Join Channel and invite Kol frens : https://t.me/+b4cEGbpVoPgwYTU0
🏆1👌1🔥1
Showing the 12 most recent of 20 posts we hold for @thecirclecalls. 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.
Forward network
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.
Mentions
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@thecirclecalls named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@mira_networkmagnum named in 1 post, 8 August 2026 – 8 August 2026
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“The Circle 🔬👨🔬” (@thecirclecalls), 2,303 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/thecirclecalls.
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.
