Data as of .
EO vs EOSU: which held to its multiple?
Over the days both have traded, EO finished 8.0 points from its stated multiple and EOSU 8.9.
Performance, window by window
| Window | Total return | Multiple would give | Difference | |||
|---|---|---|---|---|---|---|
| EO | EOSU | EO | EOSU | EO | EOSU | |
| 1 month | −21.7% | −22.6% | −13.7% | −13.7% | −8.0 pts | −8.9 pts |
| 3 months | not published | −69.8% | not published | −69.6% | not published | −0.2 pts |
| 6 months | not published | −76.4% | not published | −61.6% | not published | −14.8 pts |
| Since launch | −64.0% | −98.8% | −65.6% | −154.3% | +1.7 pts | +55.5 pts |
| EO Corgi EOSE 2x Daily ETF Aims to return twice the daily move of EOSE | EOSU T-REX 2X LONG EOSE DAILY TARGET ETF Aims to return twice the daily move of EOSE | |
|---|---|---|
| Issuer | Corgi | T-REX |
| Sets out to return | +2x | +2x |
| On | EOSE | EOSE |
| Segment | company | company |
| Fund returned, 3 months | −21.7% | −69.8% |
| Underlying returned, 3 months | −6.8% | −34.8% |
| What the stated multiple implies, 3 months | −13.7% | −69.6% |
| Difference from stated, 3 months | −8.0 pts | −0.2 pts |
| Fund returned, 1 year or since launch | −64.0% | −98.8% |
| Difference from stated, over that window | +1.7 pts | +55.5 pts |
| Underlying volatility | 111% | 107% |
| Difference over the days both have traded | −8.0 pts | −8.9 pts |
| Expense ratio | not published | 1.50% |
| Launched | Jun 30, 2026 | Jan 14, 2026 |
EO in plain words
One month to Sep 11, 2026: EO returned −21.7% where its own daily promise gave −20.8%, 0.8 points short. Read the multiple against the whole window instead and +2 times EOSE's −6.8% implies −13.7%, which makes EO look 8.0 points short. 7.2 of that is daily compounding, which happens to any +2 times fund over the same path, and the rest is the fund. EO aims to return +2 times EOSE's move each day, then resets. Over one day it does that. Over longer, the daily results compound, so the total is not +2 times the period's move: in a market that falls and comes back it is reliably less, and in a steady run it can be more. EOSE moved at 111% annualized over that window. That is what decides how far the two figures separate: the same fund on a calm underlying and a violent one is a different product.
EOSU in plain words
Three months to Sep 11, 2026: EOSU returned −69.8% where its own daily promise gave −67.6%, 2.2 points short. Read the multiple against the whole window instead and +2 times EOSE's −34.8% implies −69.6%, which makes EOSU look 0.2 points short. 2.0 of that is daily compounding, which happens to any +2 times fund over the same path, and the rest is the fund. EOSU aims to return +2 times EOSE's move each day, then resets. EOSE moved at 107% annualized over that window.
Questions people ask
- Which came closer to its stated multiple, EO or EOSU?
- Over the window to Sep 11, 2026, EO finished 8.0 points from what its multiple implies and EOSU finished 0.2 points from its own, so EOSU came closer. Neither figure predicts the next window: it depends on how much the underlying moves about.
- Are EO and EOSU levered on the same thing?
- Yes. Both are levered on EOSE, EO at +2 times and EOSU at +2 times the daily move.
- Which one decays faster, EO or EOSU?
- Decay follows how much the underlying moves about. Over this window EO’s moved at 111% annualized and EOSU’s at 107%, so EO has the rougher ride and, at the same multiple, loses more to compounding.
- Can I hold EO or EOSU for a year?
- Both reset every day, so the multiple in the name applies to a single day and the daily results compound. Over a year the total is not the multiple times the year’s move, and in a market that falls and comes back it is reliably less. ETFIQ makes no recommendation either way.
Where these figures came from
ETFIQ links to the documents behind every figure. It is not affiliated with any issuer, and a link is not an endorsement.
Cite this page. ETFIQ, EO against EOSU, data as of Sep 11, 2026. https://etfiq.com/compare/leverage/EO-EOSU Free to use with attribution; the underlying files are at Open data.