Robinhood~GemsHunter pinned Deleted message

Channel
Robinhood~GemsHunter
@RobinhoodGemsHunter
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,744subscribers
-5 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002009360017 |
|---|---|
| Type | Channel |
| Username | @RobinhoodGemsHunter |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/RobinhoodGemsHunter |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:14 | 1,744 | -5 |
| 8 Aug 2026, 08:43 | 1,749 | no change |
| 8 Aug 2026, 07:46 | 1,749 | first reading |
Engagement
20 posts held, back to 6 May 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel name was changed to «Robinhood ~GemsHunter»
Robinhood~GemsHunter pinned a photo
🙌Ok guys everything has been set up. I'm temporarily switching this channel to🏹 $Robinhood chain to take advantage of the current bullish wave on this chain, while waiting for better volumes to return on $TON chain💎 🫡New chain but same GOAL : ‼MAKE PROFIT TOGETHER ‼ https://t.me/RobinhoodGemsHunter
You know what we did during the $TON season and you know who I am, I have always aimed to be fair and transparent with you and those who have been following me for a long time know this well, so updates will follow soon, turn on notifications, we have to print‼💸
Robinhood~GemsHunter pinned «Good volume on $ROBINHOOD chain, I'm testing for you good devs from $TON chain that're moving there, I m gonna update you soon🫡 Do not follow scammer channels,remember what they ve done, you know why I am telling you this. ~Thomas»
Good volume on $ROBINHOOD chain, I'm testing for you good devs from $TON chain that're moving there, I m gonna update you soon🫡 Do not follow scammer channels,remember what they ve done, you know why I am telling you this. ~Thomas
Robinhood~GemsHunter pinned «https://x.com/ton_blockchain/status/2066525069333913823?s=46 🫡»
https://x.com/ton_blockchain/status/2066525069333913823?s=46 🫡
Robinhood~GemsHunter pinned a photo
After the success of $DogeTON years ago, with the approval of the new name $GRAM which will take the place of $TON, the chain needs a new doge coin, hence the idea of $DogeGram was born, to celebrate the new era of the entire chain✅ Daniil Dev and his team are working on it, since $GRAM season is coming. Could be huge, based names behind it let s see🙌 👇TG👇 https://t.me/DogeGramCoin 💎Join now💎 https://t.me/TonGe…
Robinhood~GemsHunter pinned a photo
Showing the 12 most recent of 20 posts we hold for @RobinhoodGemsHunter. 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 — 607,626 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Robinhood~GemsHunter” (@RobinhoodGemsHunter), 1,744 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/RobinhoodGemsHunter.
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.