![Telegram profile photo for RG Analitics 🟢 [PRIVATE CHANNEL🔒]](https://cdn.tgregister.com/av/30/301c858e95a7eb0fc25daac9f9be3af02132dfc5522bda2c4285c7044245f06a.jpg)
Channel
@RG_Analitics
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
72subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001372048212 |
|---|---|
| Type | Channel |
| Username | @RG_Analitics |
| Description | 🔒 THINKING, FAST AND SLOW 🔒 Filtering the Global Crypto Analytics (stock) Analyze, Think, Compare = Take profit! We respond in the chat @invest_club |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/RG_Analitics |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 22:46 | 72 | no change |
| 7 Aug 2026, 06:59 | 72 | first reading |
20 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 1 pageof Telegram’s post history, 20 posts per page.
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 9 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 9 August 2026) |
| Views total | 42 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 22:46 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.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Bitcoin is experiencing its longest capitulation phase since the FTX collapse in 2022, according to Glassnode. 👉 Heavy selling and investor losses suggest the market is going through a major de-risking period. Historically, extended capitulation can eventually create the conditions for a stronger recovery, but confirmation of a bottom is still needed. 📉
TREE analysis: The price is currently trading within a falling wedge pattern and is approaching a breakout. A falling wedge is a bullish formation that typically breaks out in the upward direction. We will consider opening long positions once the price moves above the $0.038 level. Be sure to monitor the breakout closely.
Bitcoin has been rejected again from the resistance area and is unable to break above it. The weekend is here, and the volume is low. We may see a continuation of sideways movement until global markets open.
#PRA A mysterious whale (possibly a miner) has deposited 6,494 $BTC($420.5M) to #Binance over the past 3 weeks. https://arkm.com/explorer/address/bc1qsylwjhesm58uw9vsp7vwgadq5fqna4e3e8qnpd @RG_Analitics Подписаться....
BTC options are now pricing a modest volatility premium, with implied volatility around 10% above realized volatility. 👉 After weeks of realized volatility staying higher, traders are now paying more for uncertainty again. However, the premium remains well below stressed levels, suggesting the options market is cautious but not fearful. 📊
#BITCOIN DAILY TF UPDATE: #BITCOIN has slowly retraced the entire week, moving up and up, still following the range with nothing happening. Nothing can be anticipated here; we need to wait for the price to move in either direction or for clarity.
Last week Bitcoin outran the equity indices, absorbing an oil shock that left stocks flat and finishing ahead of both. That relative strength has faded. Bitcoin spent this week sliding while US and European stocks sat still, and the break came on Monday: from that session onward it has not been level with stocks again. Oil gave last week's spike back and ended the week the weakest of the four. One week of relative w…
#SNX gave a break of the consolidation and formed the small range there too. Its a sign for short-selling but market is trying to sustaining at the bottom of the range. If it break the small range too (Blue Box) then get into the short positions too.
Bitcoin network activity surged after the Coldcard firmware exploit, with active addresses rising to 0.98 million per day, the highest level since December 2024. 👉 This spike reflects fear-driven on-chain activity, as users moved funds and migrated wallets to improve security. The increase is an operational security response, not a sign of changing market sentiment or investor conviction. 🔒₿
Bitcoin is still below the resistance line and has yet to break it. The market has not made a clear move. It’s better to wait for a definitive direction before entering new positions.
#BTC again experienced a short-term rejection from the resistance area, and a move lower may be imminent. However, anticipating this too early would be premature; wait for the candlestick confirmation on the Daily TF.
Bitcoin's options market appears bearish, but not because traders are rushing to hedge downside risk. 👉 Instead, upside implied volatility has fallen to a record low of 23%, showing that traders are not pricing in a strong rally. This reflects weak bullish expectations rather than heightened fear of further downside. 📉
Showing the 12 most recent of 20 posts we hold for @RG_Analitics. 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 — 1,208,813 of 1,563,849entries 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.
Named by 1 registered channel — 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“RG Analitics 🟢 [PRIVATE CHANNEL🔒]” (@RG_Analitics), 72 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/RG_Analitics.
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.