D-Apollo now supports all new accounts and the new deriv updates Happy trading guys🙂
❤8🔥2👍1🥰1

Channel
@deriv_apollo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
6,672subscribers
-125 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001772097748 |
|---|---|
| Type | Channel |
| Username | @deriv_apollo |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/deriv_apollo |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 |
|---|---|---|
| 14 Sept 2026, 12:00 | 6,672 | -13 |
| 11 Sept 2026, 06:40 | 6,685 | -22 |
| 6 Sept 2026, 17:16 | 6,707 | -4 |
| 2 Sept 2026, 03:24 | 6,711 | -9 |
| 30 Aug 2026, 05:38 | 6,720 | -14 |
| 27 Aug 2026, 10:13 | 6,734 | -9 |
| 24 Aug 2026, 13:46 | 6,743 | -19 |
| 20 Aug 2026, 22:37 | 6,762 | -1 |
| 17 Aug 2026, 20:39 | 6,763 | -8 |
| 14 Aug 2026, 22:28 | 6,771 | -13 |
| 11 Aug 2026, 10:16 | 6,784 | -12 |
| 7 Aug 2026, 23:42 | 6,796 | -1 |
| 7 Aug 2026, 13:02 | 6,797 | no change |
| 7 Aug 2026, 12:48 | 6,797 | first reading |
20 posts held, back to 16 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages 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 25 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 15 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
89 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 58.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 58.4% | |
| 👍 | 20 | 22.5% | |
| 🔥 | 13 | 14.6% | |
| 👎 | 2 | 2.25% | |
| 👏 | 1 | 1.12% | |
| 🥰 | 1 | 1.12% |
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 89 reactions 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 16 December 2025 to 25 June 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.
D-Apollo now supports all new accounts and the new deriv updates Happy trading guys🙂
❤8🔥2👍1🥰1
The matches strategy is here. Watch carefully and try to replicate for best results. I'll make another follow up video on the same. Trade cautiously, capital at risk. App.d-apollo.com
❤5
Many have suggested matches, so that's the strategy we will cover tomorrow so get ready.
👍5
What strategy would you like next?
❤3
Smooth operator! This was under 8 Using the deep scan bot. 50$ made from the session💸
❤4
The power of the edging tool. Made 47$ in minutes. To solve the martingale issue as we adress it, keep it on manual mode, so that you control the amount and entries you make. Stake manually! Remember, you only loose if 4 or 5 appears. Enjoy the profits! app.d-apollo.com
🔥6❤1👏1
THE EDGING TOOL IS HERE! ⭐️How does it work? ✅Buys two contracts at the same time( over 5 and under 4) ✅You are always guaranteed to loose one contract, but you have 80% chance of winning the other contract. Follow the video carefully and follow the steps to make the most out of it.
❤5👍1
Ready for the edging tool video? A tool that buys 2 contracts at the same time. How does it work? Get ready for the video
❤3
Under 5 market using the deep scanner. Always target atleast 50%+ success rate on the market. It's a fair market so you expect some losses as well. I managed to make 18$ from the session.
❤2👍1
Over 4 market. Watch and learn how to tackle this high risk market. Always have patience and constantly scan the market for best experience. NOTE: Not recommended for people with small capital.
❤1👍1
Under 6 market using the entry scanner. Made 5 runs got only one loss, and 35$ made. So far we're killing the market with the deep scanner. App.d-apollo.com
❤1👍1
Deep scanner in action OVER 3 MARKET has never been easier. We made 5 runs only 1 loss and made 12$ NOTE: Remember to switch number of ticks to 100 when scanning the market on over 3. Make at least 5 runs, and scan the market once more. Do that and you'll make consistent profits. All tools available on app.d-apollo.com
❤4
Showing the 12 most recent of 20 posts we hold for @deriv_apollo. 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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“DerivApollo” (@deriv_apollo), 6,672 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/deriv_apollo.
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.