Just to make things clear we are not a "pump" or "pump & dump" channel. We have no affiliation with any of the tokens we post, we are simply a team of traders sharing our trades for a commission nothing more nothing less. You can check every single token we've posted such as $SKYAI, $HEI, $CASHCAT, $BLESS, $KOMA and the rest just scroll through our channel.. To check any of the tokens you see us making a profit on j…

Channel
Bonus Round Gems
@Bonusrounds
On this record: Growth · Engagement · Posts · Cite this entry
196subscribers
-34 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001599974123 |
|---|---|
| Type | Channel |
| Username | @Bonusrounds |
| Created | Between 1 September 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/Bonusrounds |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 16:36 | 196 | -13 |
| 15 Aug 2026, 17:24 | 209 | -19 |
| 8 Aug 2026, 10:17 | 228 | no change |
| 8 Aug 2026, 07:41 | 228 | -2 |
| 7 Aug 2026, 11:16 | 230 | first reading |
Engagement
15 posts held, back to 31 July 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
- 4.15%
- avg views ÷ 196 subscribers
- Avg views / post
- 8.1
- 15 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 15
- of 15 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (31 July 2026 – 7 August 2026) |
| Views total | 122 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:17 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.
Recent posts
i personally made $100k profit from SKYAI 🔥
Another absolute rocket posted in the free premium last week, we’re all up 250% on $SKYAI in the past 7 days. Told you all to buy some of this on the 1st august, let’s hope you did
You guys inside the premium channel who made a profit from this send me some of your results for me to post please @bonusround1
People lie, numbers do not. Free Premium members are up 520% on $HEI in the past 3 days from the post we made telling you all to buy some.
You guys loved Cash Cat🤣 it’s made some of you guys in the free premium rich over night
like i said.. your dream life is one step away from being achievable
who else have you seen turn $50k into $2.8 million?
$CASHCAT pumped so fucking hard last month, $2.8 million profit in around two weeks
Another entry appeared on $BLESS and we took it, 126% gain to start the month in the Free Premium channel 🤝
if you decide you want to take that step, message me @bonusround1
Your dream life is one step away from being achievable.. are you going to take it?
Showing the 12 most recent of 15 posts we hold for @Bonusrounds. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Bonus Round Gems” (@Bonusrounds), 196 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/Bonusrounds.
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.