Jupiter (JUP)
0.00
0.56
-99.9%
Stage 2 (Uptrend)
Bullish factors: price > 50d, price > 200d, 50d rising, RSI healthy (52.1), rising 1m & 3m
Bearish factors: death cross, far below high, strong bear trend (ADX 58.4), distribution (OBV down, vol ratio 0.23)
Low: 0.00
Now: 0.00
Technical Snapshot
| RSI (14) | 52.1 | ADX (14) | 58.4 |
| 50d MA | 0.00 | 200d MA | 0.00 |
| Price vs 50d | ▲ Above | Price vs 200d | ▲ Above |
| Support | 0.00 | Resistance | 0.00 |
| ATR Volatility | 51.49%/day | Trend | BUY |
Crypto Performance Comparison
| Asset | 1 Month | 3 Months | 6 Months | 1 Year |
| JUP | +27.0% | +32.1% | +2066.8% | -50.8% |
| BTC | +25.3% | +26.1% | +0.3% | -10.2% |
| ETH | +29.7% | +38.9% | +3.0% | -17.2% |
| SOL | +33.7% | +22.4% | +15.8% | -19.2% |
Trend-Following Backtest
2-year simulation of 15,000 using 50d/200d MA crossover + RSI filter. Buy when price > 50d MA (rising) + RSI 40-75. Sell on death cross or RSI > 82.
Strategy vs Buy & Hold
| Asset | Strategy | Buy & Hold | Max DD | Trades | Win Rate |
| JUP | -100.0% | -44.7% | -100.0% | 50 | 34% |
DCA vs Lump Sum (JUP)
If you had deployed 15,000 using different timing strategies over the past year.
| Strategy | Return | Value Today |
| Lump Sum (1y ago) | -50.8% | 5,121 |
| DCA — 4 buys | -0.9% | 14,862 |
| DCA — 6 buys | +383.7% | 72,558 |
| DCA — 12 buys | +401.2% | 75,173 |
JUP Deployment Plan — 15,000 Portfolio
Analysis by Tomas Novak (Momentum / Swing Trader). If you’re managing a 15,000 crypto allocation, here’s the plan:
| Position size | 3,750 (25% of portfolio) |
| Stop loss | -0.00 (-111.3%) |
| Target 1 | 0.00 (-100.0%) |
| Target 2 | 0.00 (-100.0%) |
| Entry quality | Pullback |
| Max concurrent positions | 4 |
Cash reserve: keep 25% buffer. Deploy in 2 tranches. Portfolio style: Momentum / Swing Trader.
Backtest Trade Log
| Date | Action | Price | P&L |
| 2026-07-18 | BUY | 0.00 | |
| 2026-07-19 | SELL | 0.00 | -95.7% |
| 2026-08-23 | BUY | 0.00 | |
| 2026-08-24 | SELL | 0.00 | +2.3% |
| 2026-08-25 | BUY | 0.00 | |
| 2026-08-26 | SELL | 0.00 | +1.7% |
| 2026-08-27 | BUY | 0.00 | |
| 2026-08-28 | SELL | 0.00 | -6.2% |
| 2026-08-29 | BUY | 0.00 | |
| 2026-08-30 | SELL | 0.00 | +1.3% |
| 2026-08-31 | BUY | 0.00 | |
| END | SELL | 0.00 | -4.1% |
Trend-following methodology: 50d/200d MA crossover + RSI filter + ADX regime gate
Data via Yahoo Finance / CoinGecko · Not financial advice. For educational purposes only.
backtest turned 15k into literally 0. a -100% return attached to a BUY call is the most honest disclaimer i have ever seen
the 6m column shows +2066% right under a 0.00 price. feed is broken, the backtest ran on garbage numbers
the 15k to 0 backtest was the feed logging 0.00 as the actual price. zeros in, zeros out. engine needs a sanity filter on inputs fr
exactly. the same broken feed prints three DCA rows at +383% and +401%. if the zeros are garbage those returns are garbage too, cant cherry pick which output you trust
ADX 58.4 labeled strong bear trend yet the signal is BUY because price is above both MAs. this engine argues with itself
death cross and obv distribution listed right there in the bearish column and the signal is still BUY lol. trend following systems are something else
The ADX at 58.4 is doing the heavy lifting here. Strong trend regime overrides the crossover lag, that is the whole point of the gate.
Agreed the ADX 58.4 carries the call, but labeling it strong bear while price holds above both the 50d and 200d tells me the regime labels lag the actual tape.
lmao 5 bull factors vs 4 bear factors, net BUY, and the actual ticker says 0.00. a coin flip has better data hygiene than this card
+32.1% vs BTC at +2% while sitting under the 52w high of 0.56 with a -99.9% drawdown behind it. jup either recovers or goes to zero, no in between
w take, the vol ratio at 0.23 spooked me too but RSI 52 has room to run
that +2066% 6m column sitting next to a 0.00 price is either the squeeze of the decade or the yahoo feed is cooked again. my money is on the feed
Someone explain how the 12-buy DCA row lands on +401% when every price in the trade log reads 0.00. Same feed, two opposite conclusions, both published.