Deleted previous post, token is intended to fud another token that I support. The last thing I want to do is fud my bags, or my friends bags.
๐9๐2โคโ๐ฅ1

Channel
@OracleGems
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
181subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1001390216241 |
|---|---|
| Type | Channel |
| Username | @OracleGems |
| Description | Fortune Favours The Bold. Contact: @ZeOracle ๐งโโ๏ธ |
| Created | Between 1 March 2018 and 30 June 2021โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/OracleGems |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 08:17 | 181 | no change |
| 7 Aug 2026, 05:22 | 181 | first reading |
20 posts held, back to 26 June 2022 โ 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 24 September 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramโs own channel header, read 7 August 2026 โ not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโs rounding threshold, so these counts are exact.
96 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 40.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ | 39 | 40.6% | |
| ๐ฅ | 39 | 40.6% | |
| โค | 10 | 10.4% | |
| ๐ | 5 | 5.21% | |
| โคโ๐ฅ | 3 | 3.13% |
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 18 of the 20 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 96reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 20 most recent posts we hold, published 26 June 2022 to 24 September 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Deleted previous post, token is intended to fud another token that I support. The last thing I want to do is fud my bags, or my friends bags.
๐9๐2โคโ๐ฅ1
$ZEIRISHI ๐ฅ Smooth launch looks like there were no bots, wait for lock & renounce to be safe. Unique king of the hill tokenomics. https://dexscreener.com/ethereum/0x27a61F5e615128f954BcDe45EA9B22e8bd6f57A3
๐7โคโ๐ฅ1
Up close to 3x on fat liquidity if you bought here btw. https://www.dextools.io/app/ether/pair-explorer/0x7d537b39bc38322db86517ef6cba29f252568680
๐ฅ4โคโ๐ฅ1
$TEMPEST ๐ฅ Have been eyeing this copper for a few days and itโs been a pretty steady looking chart, mediums look professional, and the larp is pretty good. So figured I would get a bag, on this dip. I havenโt missed on copper yet, bought $HATI, $WIND, $RTK, and $KOO, so I hope I donโt miss here either. https://medium.com/@tempestofficial https://copperlaunch.com/pools/0x96E9f43d6074b957582e8a5E5Cb9Fa62D2bEEa6D
๐ฅ3๐1
$SHINU ๐ฅ Have been eyeing this for a few days. Dev is extremely based and has the recipe to push a token. Looking for an entry, because I believe it will run harder. 0 tax community token. https://t.me/SHINUportal https://shinu.app/ https://www.dextools.io/app/ether/pair-explorer/0xaf37c86f4fac3512de41739a822b08011a7981c0
๐3๐2๐ฅ2
Officially 100x ๐ค
๐ฅ6๐2
BurnShkreli Buy! ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ Spent: $1,488.32 (1.0 WETH) Got: 1,467,114 BSI Buyer Position: New! Price: 0.001014 (0.0000006816 WETH) MCap: $1,014,457 TX | Chart | Buyer | Uniswap
๐2
Resurrection Erc ๐ฅ 11k MC Bought this, may be some mystery connected. Letโs see if it runs. https://twitter.com/Resurrectionerc https://t.me/+DnVeb54JTkhjMDc5 https://www.dextools.io/app/ether/pair-explorer/0x67ca21ff16153b5da113c08548308a53d13698d1
๐2๐ฅ2
Super based dev has revived this from the lows. Hit 450k mc today! Second 40x+ call on the channel๐ค
๐ฅ8
BurnShkreli Buy! ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ Spent: $14,544.70 (10.89 WETH) Got: 53,034,000 BSI Buyer Position: New! Price: 0.0002743 (0.0000002053 WETH) MCap: $274,252 TX | Chart | Buyer | Uniswap
Inversed Inu ๐ฅ Taking a gamble here, safu dev. https://t.me/inuinversed https://www.dextools.io/app/ether/pair-explorer/0x5d03806f1b99ed427ab318250d397540c3611a7a
๐5
Has peaked at around 130k MC so around a 7-8x if you bought call or waited for 20k dip. A lot of based chads getting behind the project and market is pumping. Lets see if we can get some more Xs. ๐
๐2
Showing the 12 most recent of 20 posts we hold for @OracleGems. 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.
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.
@OracleGems named 2 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.
References a handle that is not a live channel โ we have no record it ever was one.
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 7 August 2026 โ this entry's latest reading, not the date you are reading this.
โOracle Gems ๐ฎโ (@OracleGems), 181 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/OracleGems.
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.