Telegram RegisterThe public register of Telegram
Telegram profile photo for Ekiden Official Channel

Channel

Ekiden Official Channel

@ekiden_official

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

13,420subscribers

-1,108 since we began measuring on 19 September 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003928392235
TypeChannel
Username@ekiden_official
CreatedBetween 1 April 2026 and 27 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live10 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/ekiden_official

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

13,42014,52813,97419 September 2026 — 14,528 subscribers19 September 2026 — 14,528 subscribers24 September 2026 — 14,384 subscribers3 October 2026 — 14,139 subscribers8 October 2026 — 13,999 subscribers12 October 2026 — 13,983 subscribers14 October 2026 — 13,977 subscribers15 October 2026 — 13,974 subscribers16 October 2026 — 13,958 subscribers17 October 2026 — 13,938 subscribers18 October 2026 — 13,911 subscribers19 October 2026 — 13,864 subscribers20 October 2026 — 13,812 subscribers21 October 2026 — 13,725 subscribers22 October 2026 — 13,684 subscribers23 October 2026 — 13,678 subscribers24 October 2026 — 13,667 subscribers25 October 2026 — 13,654 subscribers26 October 2026 — 13,651 subscribers27 October 2026 — 13,640 subscribers28 October 2026 — 13,628 subscribers29 October 2026 — 13,626 subscribers30 October 2026 — 13,625 subscribers31 October 2026 — 13,614 subscribers1 November 2026 — 13,607 subscribers2 November 2026 — 13,606 subscribers3 November 2026 — 13,597 subscribers4 November 2026 — 13,594 subscribers5 November 2026 — 13,575 subscribers6 November 2026 — 13,566 subscribers7 November 2026 — 13,445 subscribers8 November 2026 — 13,434 subscribers10 November 2026 — 13,420 subscribers19 September 202610 November 2026
33 measurements spanning 52 days, net -1,108. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,254–14,694 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
10 Nov 2026, 01:0813,420-14
8 Nov 2026, 17:0013,434-11
7 Nov 2026, 08:0813,445-121
6 Nov 2026, 10:4913,566-9
5 Nov 2026, 13:5113,575-19
4 Nov 2026, 17:1013,594-3
3 Nov 2026, 19:5513,597-9
2 Nov 2026, 20:3713,606-1
1 Nov 2026, 23:4913,607-7
31 Oct 2026, 21:1613,614-11
30 Oct 2026, 18:2913,625-1
29 Oct 2026, 14:5513,626-2
28 Oct 2026, 12:5513,628-12
27 Oct 2026, 15:4613,640-11
26 Oct 2026, 13:1913,651-3
25 Oct 2026, 12:1613,654-13
24 Oct 2026, 13:1613,667-11
23 Oct 2026, 13:0413,678-6
22 Oct 2026, 13:4713,684-41
21 Oct 2026, 06:5113,725first reading

Engagement

30 posts held, back to 27 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 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.47%
avg views ÷ 13,420 subscribers
Avg views / post
332
5 posts measured
Reaction rate
0.482%
reactions ÷ views · ER floor
Posts in window
5
of 30 held

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. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 October 2026
Posts held30 (27 August 2026 – 27 October 2026)
Views total1,659
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 18:56 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.

What this channel posts

Video runtime
1m 07s
Average length
1m 07s

Measured directly from 1 video 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.

Reaction mix

703 reactions across 28 posts, in 20 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤26738.0%
🔥19327.5%
👍618.68%
👏365.12%
⚡334.69%
💯212.99%
❤‍🔥192.70%
🏆162.28%
🍾131.85%
🫡101.42%
👌70.996%
🤝50.711%
👀40.569%
🤩40.569%
🦄40.569%
🎉30.427%
🆒20.284%
🐳20.284%
😱20.284%
🤗10.142%

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 28 of the 30 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 703 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 27 August 2026 to 27 October 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

27 Oct 2026, 15:23 UTC265 viewsread 9 November 2026
Video

Ekiden is an order book-based derivatives exchange, so every trade starts with liquidity already sitting on the book or an order coming in to take it. If your order rests on the book and adds liquidity, you’re the maker. If your order matches against existing liquidity and executes immediately, you’re the taker. From there, the flow is straightforward: Order → Matching Engine → Execution → Settlement on Canton T…

23 Oct 2026, 19:24 UTC357 views2 reactionsread 9 November 2026
Photo

Ekiden is fully operational again. The upgrade is complete, all exchange functions are available, and trading has resumed. Ekiden is now running on new infrastructure, and early performance is already exceeding our expectations. Faster execution, stronger infrastructure, and a better foundation for what comes next. Have a good weekend. We’ll keep building. Mainnet | Support | X

🔥2

21 Oct 2026, 09:28 UTC357 viewsread 9 November 2026
Photo

Reminder: Ekiden Update is Today The exchange update begins today, October 21 at 8:00 AM EDT and is expected to run until approximately 8:00 PM EDT. During the upgrade, deposits, withdrawals, trading, and other exchange functions will be temporarily unavailable. Your account data and trading progress will remain safe. We’ll confirm once the upgrade is complete and the exchange is fully operational again.

20 Oct 2026, 12:54 UTC369 views2 reactionsread 9 November 2026
Photo

⚠️ Important Exchange Update We’re preparing a major Ekiden upgrade that will affect core exchange infrastructure, including both Funding Accounts and Trading Accounts. The upgrade will begin tomorrow, October 21 at 8:00 AM EDT and is expected to run until approximately 8:00 PM EDT. Before the update begins, all users need to: • Close all open positions • Cancel all open orders • Withdraw all assets from Funding a…

🔥2

19 Oct 2026, 15:27 UTC311 views1 reactionsread 9 November 2026
Photo

For professional traders using the Ekiden API, error handling is part of execution. We’ve expanded the API docs with a full reference for gateway HTTP errors, matching engine codes for order placement, modification and cancellation, and every common error codes The docs also cover retry and backoff logic, plus how to verify the final status of batch requests. If you’re trading on Ekiden through the API, this is wo…

❤1

6 Oct 2026, 23:03 UTC577 views33 reactionsread 9 November 2026
Photo

Incident Notice — October 6 Earlier today, a deployment caused an issue with the recovery of the funding index after exchange update As a result, funding was incorrectly applied across several markets. This caused abnormal account balance changes and led to the liquidation of a number of (and gains for the others) accounts before the issue was identified. The issue was caused by a backwards-compatibility problem in…

❤19🔥6👍5👏3

2 Oct 2026, 10:12 UTC639 views40 reactionsread 9 November 2026
Photo

20 days — $5M+ in volume Twenty days into Ekiden Mainnet, cumulative trading volume has reached $5,865,560. All of it has happened inside closed Mainnet, with access still invite-only. A solid first 20 days. On to the next milestone. Mainnet | Support | X

🔥16❤‍🔥11❤10👏3

1 Oct 2026, 13:29 UTC633 views41 reactionsread 9 November 2026
Photo

Gold & Silver are now live on Ekiden We’re launching our first commodity markets on Canton: XAU/USDCx - Gold XAG/USDCx - Silver These markets introduce a new asset class to Ekiden, with dedicated risk parameters built around their specific trading schedule 24/5 and market structure. ⏰ Trading hours · ET (New York) 🟢Mon–Thu: 00:00–17:00 / 18:00–24:00 🟢Fri: 00:00 – 17:00 🟢Sun: 18:00 – 24:00 And throughout the Close…

❤17👍14🔥10

30 Sept 2026, 18:52 UTC523 views35 reactionsread 9 November 2026
Photo

September changed a lot for Ekiden. Closed mainnet went live on Canton. $1M+ in organic volume in the first week. $5M+ within the first 20 days. New leverage, lower fees, referrals, wallet progress, new markets, integrations and a much stronger trading stack. We packed the full September product recap into one article. If you want to see what actually shipped, what moved the numbers, and what comes next for Eki…

❤18🔥8⚡5👏3🐳1

21 Sept 2026, 15:56 UTC688 views28 reactionsread 9 November 2026
Photo

Confidentiality is becoming a big narrative in crypto right now. For Ekiden, it has been part of the product from day one. Trading activity is confidential by default, account abstraction separates funding from execution, and Canton provides need-to-know settlement at the network layer. We broke down why this narrative is taking off now, how confidentiality actually works in trading, and why it matters for derivati…

❤15👍9🔥3👏1

18 Sept 2026, 17:46 UTC668 views27 reactionsread 9 November 2026
Photo

More flexibility for your trading strategies We’ve updated leverage limits across Ekiden markets, giving you more control over position size and the margin you commit to each trade. Here are the new limits: $BTC, $ETH and $HYPE up to 20x $CC up to 10x Choose the leverage that fits your strategy and risk tolerance. Keep an eye on your liquidation price as you adjust leverage. 🔍Explore the markets Mainnet | Suppor…

❤12👍7🔥5🍾1👏1🦄1

17 Sept 2026, 17:52 UTC614 views24 reactionsread 9 November 2026
Photo

Your network fees are on us, for now During Ekiden’s closed mainnet, we’re covering the Canton Network base fee for every user — making the base fee 0 across all Ekiden markets. On top of that, we’re lowering trading fees. In total, you get: 🟢 Maker — 0.02% 🟢 Taker — 0.035% 🟢 Base fee 0 — subsidized by Ekiden Previously, this trading fee tier required $10M in a rolling 30-day volume. Now this fee tier applies to …

❤8🔥8🤩4🏆2🍾1👍1

Showing the 12 most recent of 30 posts we hold for @ekiden_official. 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.

Mentions

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.

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Ekiden Official Channel” (@ekiden_official), 13,420 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/ekiden_official.

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.