AR Parabolic SAR Strategy (1h) - Backtest Results
Price Action & Trades
Recent Trade History (Live Proof)
| Entry Date | Exit Date | Type | Entry Price | Exit Price | Profit/Loss Ratio |
|---|---|---|---|---|---|
| Jan 26, 15:00 | Jan 27, 09:00 | Long | $3.3600 | $3.3200 | -1.19% |
| Jan 26, 00:00 | Jan 26, 11:00 | Long | $3.3300 | $3.3300 | 0% |
| Jan 23, 17:00 | Jan 24, 08:00 | Long | $3.6300 | $3.5200 | -3.03% |
| Jan 23, 05:00 | Jan 23, 15:00 | Long | $3.6100 | $3.5100 | -2.77% |
| Jan 21, 20:00 | Jan 22, 11:00 | Long | $3.6600 | $3.5600 | -2.73% |
| Jan 21, 02:00 | Jan 21, 12:00 | Long | $3.7100 | $3.5700 | -3.77% |
| Jan 19, 19:00 | Jan 20, 14:00 | Long | $3.8600 | $3.6400 | -5.7% |
| Jan 18, 10:00 | Jan 18, 23:00 | Long | $4.0600 | $3.9800 | -1.97% |
| Jan 16, 23:00 | Jan 17, 18:00 | Long | $4.0500 | $4.0800 | +0.74% |
| Jan 16, 02:00 | Jan 16, 15:00 | Long | $3.9300 | $3.9400 | +0.25% |
Equity Curve
AI Deep AnalysisPowered by algorithmic insights
Low win rate (32.56%) is common for breakout strategies on volatile assets like AR. Focus on risk per trade.
Low profit factor (1.02) indicates potential parameter optimization is needed for AR.
With 86 signals generated, this is a high-activity setup. Expect multiple opportunities per week.
Time-of-day filtering may improve results: analyze when AR shows strongest Parabolic SAR response.
This Parabolic SAR setup on AR shows increased effectiveness during moderate volatility regimes.
Volatility-adjusted sizing: reduce position size when AR ATR exceeds 150% of average.
Performance Metrics
See Live Signal
Real-time technical analysis
View the current Parabolic SAR signal for AR with live market data, AI analysis, and trading recommendations.
About The Parabolic SAR Strategy
Backtest Methodology
Key Takeaways
- Position sizing: 1-2% per trade suggested.
- Stop-loss levels align with AR volatility.
- Drawdown tolerance required for 32.56% win rate.
Was this analysis helpful?
Your feedback helps us improve our backtest reports and provide better insights.
Have specific suggestions? Contact us