> For the complete documentation index, see [llms.txt](https://docs.walletx.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.walletx.bot/copy-trading-academy/copytrading-dos-and-donts/1.-balance-win-rate-and-roi.md).

# 1. Balance Win Rate and ROI

Win Rate shows the percentage of profitable trades vs losses, while ROI represents total return on investment. Both metrics are crucial for evaluating a wallet's performance:

### 🎯 Win Rate Analysis:

* Choose High Win Rate Wallets (65-90%)
* Best for consistent, steady gains
* Shows reliable trading strategy
* ⚠️ Avoid anything above 95% (likely manipulated)

### 📈 ROI Consideration:

* Low Win Rate but High ROI
* Some traders win big but less often
* Example: 3000% gains despite fewer wins
* Home-run trades compensate for small losses

📝**Pro Tip:** Look for wallets with balanced metrics - either high win rate with steady ROI, or lower win rate with exceptional ROI! 🎯

🧠 **Remember:** WalletX premium provides pre-vetted wallets matching these optimal criteria! 🚀


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.walletx.bot/copy-trading-academy/copytrading-dos-and-donts/1.-balance-win-rate-and-roi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.