Channel
@capdax_announcements
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
90subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001252293879 |
|---|---|
| Type | Channel |
| Username | @capdax_announcements |
| Description | This is the official channel for Capdax Exchange Announcements |
| Created | Between 1 March 2018 and 27 July 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/capdax_announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 14:18 | 90 | no change |
| 6 Aug 2026, 05:55 | 90 | first reading |
20 posts held, back to 27 July 2018 — 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 4 September 2019. An engagement rate over an empty window would be a number about nothing.
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. Below Telegram’s rounding threshold, so these counts are exact.
Dear Community, Thank you all for your support and patience on the journey to get to this point. The below medium post will be our last post, and will provide all the information on where the accounts stand, and how to participate in the buy back. Please read through it thoroughly, and if you have any questions after myself and Nola will be happy to try answer. Thanks again, and we wish you all well, The Team at C…
Dear Community, As promised we would provide a July update on whether the anticipated path forward into the derivatives space could be achieved. The necessary agreements could not be made and hence we have decided that further work on this project will not be pursued. It’s been a long road to get to this point, with a difficult crypto market over the 12 months and a multitude of setbacks. This post outlines the jour…
Good day everyone 😊 Most of you were aware of the ongoing analysis of pivots mentioned during the recent update. We have made good progress which we would like to share with you today. Please read the full Medium article with further details below. As always, feel free to share any questions/feedback for discussion here, and Tristan and I will get back to you. Thanks to everyone for the continuous support and inpu…
Capdax_Announcements pinned «Dear Capdax Community As promised, we have completed our 30 day review and consultation period with our major supporters. This update is to provide the results of this review, and the path forward. As always, we at Capdax very much appreciate your support…»
Dear Capdax Community As promised, we have completed our 30 day review and consultation period with our major supporters. This update is to provide the results of this review, and the path forward. As always, we at Capdax very much appreciate your support, and look forward to your comments and feedback. 🙌 Myself and Manola @nola_cd can be reached here or via pm Please subscribe to our announcements channel t.me/c…
Dear Capdax Community. Please read the below medium article with provides a detailed update on where the project sits to date, and the future outlook. As you are all aware it has been a challenging period in the cryptosphere and Capdax have been working hard to navigate the challenges. Thank you for your continued support. https://medium.com/capdax-exchange/community-update-february-aa36f548c975
Hi Capdax Community! In December we promised you a broader communication update regarding Capdax progress and what to expect in the near future. Please read more at https://medium.com/capdax-exchange/capdax-community-update-january-2019-8309b4a3f9dd We hope this will bring clarity to most of the major topics that came up in the recent community discussions. If you have any more questions feel free to reach out to me …
Merry Christmas & Happy New Year! Here is our latest announcement, https://medium.com/@capdax/merry-christmas-happy-new-year-capdax-community-ddf63725ae6b — Information — ‼️Telegram ADMINS for this group: @EmilCapdax @Tkovero @simonaxu @CWWWW1 @DrewCM @rayeth 1 ETH represent 49334.2011 XCD (no bonus included) Crowdsale price was pegged at $934.32 USD/ETH https://capdax.com t.me/CapdaxExchange t.me/capdax_announ…
Read our latest Medium article, Capdax Launch Timings https://medium.com/@capdax/update-capdax-launch-timings-e62e2961bb5 — Information — ‼️Telegram ADMINS for this group: @EmilCapdax @Tkovero @simonaxu @dcapdax @CWWWW1 @DrewCM @rayeth 1 ETH represent 49334.2011 XCD (no bonus included) Crowdsale price was pegged at $934.32 USD/ETH https://capdax.com t.me/CapdaxExchange t.me/capdax_announcements https://medium.co…
Hi all, We’ve partnered with Cryptology and Blue Whale to reward new followers with XCD and BWX🔥🔥 Check out the campaign below and how you can participate to win a shared drop up to 10,000 USDT in XCD and BWX. 4 steps to participate: 1. Follow Cryptology (https://www.t.me/cryptology_community) + Blue Whale (https://t.me/bluewhalefdn) + Capdax Exchange (https://t.me/CapdaxExchange) 2. Make a minimum of 1 trade on…
Hi Everyone, 🔥⚡️🔥Capdax XCD will be officially listed on Cryptology Exchange (https://cryptology.com/) today! Deposits and withdrawals start now, XCD/ETH trading available from tomorrow. More details can be found here: https://medium.com/@capdax/capdax-xcd-is-listed-on-cryptology-d57a95f5bb9b — Information — ‼️Telegram ADMINS for this group: @EmilCapdax @Tkovero @simonaxu @dcapdax @CWWWW1 @DrewCM @rayeth 1 ETH …
We are approaching our Q4 launch soon and have partnered up with BitGo to ensure Capdax’ and its customers’ safety and security. Read more about our partnership with here: https://medium.com/@capdax/capdax-partners-with-bitgo-for-enhanced-exchange-security-5956af796b73 — Information — ‼️Telegram ADMINS for this group: @EmilCapdax @Tkovero @dcapdax @CWWWW1 @DrewCM @rayeth @DutchGiant 1 ETH represent 49334.2011 XCD…
Showing the 12 most recent of 20 posts we hold for @capdax_announcements. 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.
@capdax_announcements named 1 handle 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Capdax_Announcements” (@capdax_announcements), 90 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/capdax_announcements.
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.