Telegram RegisterThe public register of Telegram
Telegram profile photo for Mr_Roshi

Channel

Mr_Roshi

@Roshi_Gems_Calls

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

33subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002287001863
TypeChannel
Username@Roshi_Gems_Calls
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged3 times, most recently 12 September 2026
On Telegramt.me/Roshi_Gems_Calls

Growth

3335346 August 2026 — 33 subscribers11 August 2026 — 33 subscribers14 August 2026 — 34 subscribers20 August 2026 — 35 subscribers27 August 2026 — 33 subscribers6 August 202627 August 2026
5 measurements spanning 21 days. 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 33–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 23:2733-2
20 Aug 2026, 11:0435+1
14 Aug 2026, 00:1434+1
11 Aug 2026, 01:0233no change
6 Aug 2026, 22:0133first reading

Engagement

19 posts held, back to 23 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 02:52 UTC2 viewsread 11 August 2026
Forwarded from @Supreme_Apes_Call

Another Massive Win in the Private Alpha! 💰💰 ​Stop chasing pumps and start positioning yourself early. Secure your spot in the private alpha group today and let's win together.

8 Aug 2026, 02:52 UTC2 viewsread 11 August 2026
Forwarded from @Supreme_Apes_Call

This is what happens when you get early access to high-conviction plays inside our private alpha group. While the rest of the market is chasing pumps, our members are already positioning for the next major breakout. DM @Supreme_VIP_Signals to join the VIP group for early calls.

8 Aug 2026, 02:52 UTC2 viewsread 11 August 2026
Forwarded from @Supreme_Apes_Call

Want in on the next breakout call? Don't watch from the sidelines while our members secure life-changing multiples. Join our private alpha today and stay ahead of the market. 📌 t.me/+Eg3THGNXq9FkZDFk 👆👆👆👆

28 Jul 2026, 21:55 UTC2 viewsread 11 August 2026
Forwarded from @Supreme_Apes_Call

VIP EXCLUSIVE WIN 💎 Precision matters. We called $GROK.ME just 3 hours ago at a $95.9k market cap. ​The result? An absolute masterclass. We are currently sitting on a massive 5.9x return for our VIP members. 🔥 Consistent alpha. Consistent printing. 💪 Congratulations to everyone who trusted the call and entered early!

14 Jul 2026, 04:40 UTC3 viewsread 11 August 2026
Forwarded from @Supreme_Apes_CallPhoto

My VIPs are stacking gains across the board, and the momentum is only accelerating. 🚀 Ready to stop watching the charts and start setting the pace? Join the inner circle to get my early calls before the masses jump in. t.me/+Eg3THGNXq9FkZDFk Let’s hunt the next 1000X together. 🦍💸💰

6 Jul 2026, 07:08 UTC4 viewsread 11 August 2026
Forwarded from @Supreme_Apes_Call

The VIP circle is where the real life-changing plays happen. Secure your spot now, lock in that early access, and let’s hunt the next 1000X together. The next big move is already loading... are you in or are you out? DM me @SUPREME_VIP_SIGNALS to secure your entry. 🦍💎🔥

6 Jul 2026, 07:08 UTC4 viewsread 11 August 2026
Forwarded from @Supreme_Apes_CallPhoto

🚀 WE JUST ABSOLUTELY CRUSHED IT! 🚀 ​The market didn't stand a chance today. That last calls just hit our take profit targets with incredible speed, locking in massive gains for everyone who followed the plan. 💰 ​This is exactly why we move as a team, We analyze, we wait for the perfect entry, and we execute with precision. While the rest of the market was guessing, we were securing the bag. 🦍🦍

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

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

“Mr_Roshi” (@Roshi_Gems_Calls), 33 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Roshi_Gems_Calls.

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.