VOLATILITY 90 1S INDEX RUNNING MASSIVELY IN PROFITS 📊📊📊📊

Channel
DERIV CHAMPION🏆🏆
@Deriv_champions
On this record: Topic · Growth · Engagement · Posts · Cite this entry
299subscribers
-102 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001201105596 |
|---|---|
| Type | Channel |
| Username | @Deriv_champions |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/Deriv_champions |
Topic
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 15:37 | 299 | -17 |
| 1 Oct 2026, 21:00 | 316 | -27 |
| 17 Sept 2026, 17:40 | 343 | -9 |
| 10 Sept 2026, 08:38 | 352 | -5 |
| 1 Sept 2026, 02:18 | 357 | -13 |
| 24 Aug 2026, 11:08 | 370 | -11 |
| 16 Aug 2026, 19:24 | 381 | -20 |
| 8 Aug 2026, 05:48 | 401 | no change |
| 7 Aug 2026, 17:55 | 401 | first reading |
Engagement
20 posts held, back to 17 January 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 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 29 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
VOLATILITY 90 1S INDEX SELL NOW APPLY PROPER RISK MANAGEMENT
HELLO 👋
TP2 Hit +100 Pips Profit Running☄️☄️ ☄️☄️ENJOY YOUR PROFIT🤩☄️ Close half position and set BE now
TP1 Hit +70 Pips Profit Running☄️☄️ ☄️☄️ENJOY YOUR PROFIT🤩☄️ Close half position and set BE now
GOLD SELL NOW 4785_4788 TP 4780 TP 4775 TP 4770 OPEN SL 4794
VOLATILITY 50 1S INDEX RUNNING MASSIVELY IN PROFITS 📊📊📊📊
VOLATILITY 50 1S INDEX RUNNING MASSIVELY IN PROFITS 📊📊📊📊
VOLATILITY 50 1S INDEX RUNNING MASSIVELY IN PROFITS 📊📊📊📊
VOLATILITY 50 1S INDEX RUNNING MASSIVELY IN PROFITS 📊📊📊📊
VOLATILITY 50 1S INDEX BUY NOW APPLY PROPER RISK MANAGEMENT
Assalamualaikum
Showing the 12 most recent of 20 posts we hold for @Deriv_champions. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“DERIV CHAMPION🏆🏆” (@Deriv_champions), 299 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/Deriv_champions.
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.