15 measurements spanning 16 days, net -357. 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 18,044β18,509 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 14:02
18,098
-30
21 Aug 2026, 02:27
18,128
-12
20 Aug 2026, 01:41
18,140
-18
18 Aug 2026, 23:26
18,158
-14
17 Aug 2026, 23:07
18,172
-34
16 Aug 2026, 21:13
18,206
-45
15 Aug 2026, 15:15
18,251
-44
14 Aug 2026, 00:58
18,295
-19
12 Aug 2026, 21:28
18,314
-21
11 Aug 2026, 20:39
18,335
-44
10 Aug 2026, 19:13
18,379
-9
9 Aug 2026, 16:02
18,388
-21
8 Aug 2026, 17:37
18,409
-37
7 Aug 2026, 14:23
18,446
-9
7 Aug 2026, 02:02
18,455
first reading
Engagement
146 posts held, back to 5 August 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 33 pagesof Telegramβs post history, 20 posts per page.
ERR Β· 30 days
4.22%
avg views Γ· 18,098 subscribers
Avg views / post
765
144 posts measured
Reaction rate
0.585%
reactions Γ· views Β· ER floor
Posts in window
146
of 146 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 89 of 144 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 21 August 2026
Posts held
146 (5 August 2026 β 21 August 2026)
Views total
110,099
Reactions total
421
Forwards / comments
not exposed by the public surface β not measured, not estimated
Readings taken
22 Aug 2026, 10:07 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
421 reactions across 88 posts, in 14 distinct kinds. The most used accounts for 58.2% of them.
Every reaction kind recorded on the sample, most used first
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 89 of the 146 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 421reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 146 most recent posts we hold, published 5 August 2026 to 21 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.
Telegram Stars
Stars received
3
across the posts below
Posts paid on
3
of 144 we hold a reading for Β· 2%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars β bought with money β on a post by @GemsofRa. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 146 most recent posts we hold for this entry, published 5 August 2026 to 21 August 2026. Star counts above 1,000 reach us in Telegramβs short form and carry the same three-significant-figure rounding as everything else on this page.
Sometimes words fall short. It is very difficult to convince people because they are set in their ways. But I swear to you, I am trying so hard here on the main channel to help you make money. I admit that things have been disappointing lately, but believe meβsometimes, when you put too much effort and care into something, things just don't go right.
The last thing I would ever want to do is screw you over. Just looβ¦
Quick update about the BANGER call.
Yes, I called it as a BANGER. Because of their deployer connected to 28 mil ATH project somehow. It reached around 1.8x since my call, and I was expecting much more too. The outcome is disappointing.
The team decided to shut the project down. That's not something I control, and it's not something anyone can predict with certainty.
Iβll never pretend every call is a winner. Some β¦
You can't make money out of fear. If you're buying a token, you have to believe in it first. Iβve already done the believing for you. But do your own research, too; if you find the information I have, youβll be convinced. Itβs still very early days.
Iβm not telling you whether to buy or not.
For years, my only goal has been to help people make money. That has never changed.
Weβre going to send Optimus to the moon.
Waiting is over. I couldn't grab it via BID, because I was expecting a lot lower at launch, so It was useless to use BID to ape at 300k.
Let's go from here! π
πΈ $OPTIMUS - 317k
https://dexscreener.com/bsc/0x2471cb44fd4bdd769183d2a059b029657d38eaf2
0x2da34177376b906f75cc111f620bb0b2423c7777
Normally I don't talk about how great devs' past projects were, and I don't tell people to buy every new project with such shilling. In fact, I've been avoiding shilling almost entirely lately.
But I can't say the same about this one.
The team is elite. This isn't a one-dev project.β¦
Called the Ethereum long at $1,867 a few days ago and said weβd see an unseen pump that would push it clean through $2,000.
Today it ripped all the way to $2,450 and is sitting at $2,371 right now.
A lot of you who ran high leverage on that call just printed serious money. Congrats β you actually listened.
Technically it was straightforward: ETH had been coiling for weeks under that heavy resistance zone, funding β¦
Did you fill your BID account btw? https://t.me/BidClubBot?start=r_RHY7UWW
Expeting to have that alpha BASE banger play today. I'll ape there and you will be notified instantly.
Showing the 12 most recent of 146 posts we hold for @GemsofRa. 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 β 40,269 of 1,583,249entries 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
Named by 10 registered channels β every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched β that handle may belong to someone else now, and crediting todayβs namer to yesterdayβs owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegramβs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseβs query is independent of having been queried itself.
Maestro Hub @MaestroBotsHub Β· 170,901 Telegram ranks this channel #6 of 84 here β alongside 83 others β read 12 August 2026
Maestro Bot Updates @MaestroSniperUpdates Β· 192,196 Telegram ranks this channel #8 of 82 here β alongside 81 others β read 12 August 2026
World Liberty Financial @defiant1s Β· 83,497 Telegram ranks this channel #26 of 81 here β alongside 80 others β read 18 August 2026
Pow's Gem Calls @PowsGemCalls Β· 113,245 Telegram ranks this channel #26 of 83 here β alongside 82 others β read 14 August 2026
CRYPTO NEWS @cryptocurrency_media Β· 67,888 Telegram ranks this channel #30 of 81 here β alongside 80 others β read 21 August 2026
MadApes Calls @mad_apes_call Β· 81,914 Telegram ranks this channel #34 of 85 here β alongside 84 others β read 18 August 2026
Gambles π² MadApes @mad_apes_gambles Β· 100,589 Telegram ranks this channel #38 of 84 here β alongside 83 others β read 15 August 2026
SOL TRENDING @trendingssol Β· 143,410 Telegram ranks this channel #48 of 72 here β alongside 71 others β read 13 August 2026
Cielo Announcements @cieloannouncements Β· 59,943 Telegram ranks this channel #60 of 77 here β alongside 76 others β read 19 August 2026
Crypto King Call @Crypto_KingCall Β· 98,837 Telegram ranks this channel #70 of 91 here β alongside 90 others β read 15 August 2026
Watcher Guru @WatcherGuru Β· 627,413 Telegram ranks this channel #82 of 94 here β alongside 93 others β read 8 August 2026
This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegramβs list for THAT channel, not this one β see how this is measured.
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 22 August 2026 β this
entry's latest reading, not the date you are reading this.
βGems of Ra ππβπ¨β (@GemsofRa), 18,098 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/GemsofRa.
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.