Channel
@sharmaroyalcrypto
On this record: Topic · Growth · Engagement · Posts · Cite this entry
38subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001464501912 |
|---|---|
| Type | Channel |
| Username | @sharmaroyalcrypto |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 10 October 2026 |
| On Telegram | t.me/sharmaroyalcrypto |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 66% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 09:59 | 38 | -1 |
| 10 Aug 2026, 19:46 | 39 | no change |
| 6 Aug 2026, 23:55 | 39 | first reading |
20 posts held, back to 8 January 2024 — 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 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 20 posts for this entry, the most recent from 13 March 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Sign up for a Bybit account and claim exclusive rewards from the Bybit referral program! Plus, claim up to 6,045 USDT bonus at https://www.bybit.com/invite?ref=OE4QNQ.
Sl 16.700
Long Tia/usdt with 3x
40500 se down gya to long term short rally aa jayega near to border line
https://youtu.be/mOUA6rgVJoI?si=MRYP2YOz-aqiiRHb
Buy comp/usdt 57.73 tgt 64,68,72 stop loss 55
Short sui/usdt in current price and use sl 1.34 its give more profit u can book as ur wallet risk
Some investment in TiA/usdt is it's 💎 gem coin u can collect and add in ur protifolio
Btc yadi 40500 se down huaa to big cresh start ho skta hai long term me
Btc 43k near ya 42500 pe crash stop ho Jane ke bad new fresh buying range Banta hai or 41k se down Jane ke bad buying opportunity nhi rhega
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @sharmaroyalcrypto. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Royalcryptofire” (@sharmaroyalcrypto), 38 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/sharmaroyalcrypto.
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.