3 measurements spanning 3 days, net -1. 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 1,135–1,136 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 05:16
1,135
-1
7 Aug 2026, 23:48
1,136
no change
7 Aug 2026, 13:32
1,136
first reading
Engagement
17 posts held, back to 26 June 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
29.3%
avg views ÷ 1,135 subscribers
Avg views / post
333
8 posts measured
Reaction rate
1.84%
reactions ÷ views · ER floor
Posts in window
8
of 17 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 4 August 2026
Posts held
17 (26 June 2026 – 4 August 2026)
Views total
2,661
Reactions total
49
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 23:48 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
122 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 48.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
59
48.4%
🔥
23
18.9%
💯
13
10.7%
🤩
9
7.38%
⚡
8
6.56%
👍
6
4.92%
🏆
3
2.46%
🐳
1
0.82%
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 17 of the 17 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 122reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 26 June 2026 to 4 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.
My 3 big accumulations in $ALTS.
$PUMP - inevitable, being that it still has 0 competition
$VIRTUAL - one of the most attractive AI hubs
$UNI - a more boring one, but this is where the whole onchain infra runs. Probably the safest bet for alts.
If the next run favors $ETH the way I think, I wouldn't wanna be sidelined in some of these alts.
https://x.com/0xbabaa/status/2084712759242146030?s=20
Might've silently caught the $ETH bottom by DCAing.
Spoke about it since months, and was buying piece by piece when it was really not exciting to do so.
Now seeing a start of sentiment shift...
Love this game!
$ETH will reward our patience
https://x.com/0xbabaa/status/2082570916215554328?s=20
Might be the sealing point that i will never hold again anything onchain through the summer.
Simply doesn’t make sense: things are much slower, people are away, and teams do these sorts of things much easier since you can’t keep a close eye on them.
The other lesson is taking profits: ive already learnt this lesson before, but im saying this for whoever is following along - taking even 10-20% profits on 2x / 3x / ……
This rug is insane. Even if initial investment was not big, it definitely changes the perspective of plays in $sol, and the risks that come with it.
I’m very sorry for everyone caught off guard on it. A lesson for me honestly on $sol
While I was away for the past week, $shush, one of my main plays in solana, has been buzzing.
They opened up their platform for @RobinhoodApp in record time.
I am hearing they are pitching their product to very big names in dynamic portfolio management space, and actively collecting feedback to take the platform to the next level.
These guys are very serious of taking $shush to the absolute top of automated encrypt…
Nothing has changed for my $SHUSH plans, the @RobinhoodApp meta just added some delays (and gave more chances to people wanting to be in the $SHUSH journey).
The first ever FHE privacy automated trading ecosystem, in base + sol + eth.
80% of users are net positive with their strategies.
I have a crazy idea: what if $SHUSH can offer us the same algo-trading for Robinhood chain?
Im sure there's a LOT of money to be m…
No wonder many $SOL chads never make it.
https://x.com/0xbabaa/status/2074956348354437446?s=20
Eyes wide open for the robinhood support submitted for auditing already 👀
$SHUSH keeps being one of the very few projects in #sol delivering.
They are playing in another league from your typical 500k hyped pump & dump shitters, and their integrations will show you that soon.
Play in another league, reprice in another market cap range. Thats what is due for $SHUSH.
Very good entries on the slow days for those who are observing!
https://x.com/0xbabaa/status/2073112583331270713?s=20
⚡5
Showing the 12 most recent of 17 posts we hold for @babas_table. 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.
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
4
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
4
vacant every time we have ever looked
@babas_table named 4 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@blockstrikesol named in 1 post, 8 August 2026 – 8 August 2026
@ego1stx2323 named in 1 post, 8 August 2026 – 8 August 2026
@itz_xchar0 named in 1 post, 8 August 2026 – 8 August 2026
@raindroponx 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.
“Baba's Round Table” (@babas_table), 1,135 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/babas_table.
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.