Home Blog
Am I overtrading? Three tests from your own statement
"Too many trades" means nothing in the abstract. The real question is whether your expectancy per trade falls as your own trade count rises — and that is measurable directly from a statement you probably already have.
A definition worth using
Overtrading is trading past the point where each additional trade still adds expected value. It is not a number of trades — twenty trades a day can be entirely fine for one style and five can already be too many for another. It's a shape in the data: expectancy that holds steady, or one that visibly declines as the count for a given day climbs.
Test 1 — expectancy against daily trade count
Group your trading days by how many trades happened on each one — 1–2, 3–5, 6–10, 11+ — and compute average R per trade within each bucket. A clearly hypothetical result, invented to show the shape a declining pattern actually looks like:
| Trades that day | Average R per trade |
|---|---|
| 1–2 | +0.22R |
| 3–5 | +0.15R |
| 6–10 | −0.04R |
| 11+ | −0.31R |
A result like this one is the fingerprint: quality per trade dropping steadily as volume rises on the same day. A flat result across every bucket — average R holding roughly steady regardless of how many trades a given day had — would mean something different: you're probably fine, and the number of trades on a given day isn't the variable driving your results either way.
Why volume alone hides the pattern
A raw count of trades per day tells you nothing about quality on its own — someone doing three genuinely excellent trades a day and someone doing three mediocre ones both show "3" in a simple tally. Bucketing by count and then averaging R within each bucket is what actually exposes the pattern, because it asks a different question: not "how many trades," but "does quality change as quantity changes for this specific trader." Two traders with identical average trade counts can have completely opposite answers to that question, one improving slightly as the day gets busier, the other falling apart in exactly the shape the hypothetical table above shows.
Test 2 — hold time
Compare the holding-time distribution of your winners against your losers, and separately, of trades opened within roughly 30 minutes of a prior loss against everything else. A cluster of unusually short holds specifically among trades that followed a recent loss is a distinct fingerprint of its own, worth checking regardless of what Test 1 shows, since it can appear even in a day that didn't have an unusually high total trade count.
Test 3 — session drift
Split R by trading session and by hour on your broker's own server clock — not your local time, since every timestamp on a MetaTrader statement is recorded in the broker's server time. Most traders have one or two hours genuinely doing the work and a longer tail of other hours slowly giving some of it back. See the market-hours hub and trading sessions for how to map your own server timestamps onto real session boundaries before drawing conclusions from this test.
Reading the three together
A declining Test 1 alone suggests a volume problem on high-count days specifically. A Test 2 cluster without a Test 1 decline suggests the issue is timing after a loss rather than sheer count. A Test 3 tail without either of the other two suggests the problem is which hours you trade, not how many trades or how quickly after a loss. None of the three proves the others, and a small bucket in any of them — a handful of days, a handful of trades — can easily be sample-size noise rather than a real pattern; treat a result built from very few data points as a lead worth watching, not a conclusion.
What none of the three tests prove on their own
A single week's version of any of these three tests is thin evidence. A bad Test 1 bucket built from three unlucky days in a single week says far less than the same shape holding up across two full months. The tests are diagnostic tools for spotting a candidate pattern worth investigating further, not a verdict delivered after one look — run them again over a longer window before treating any single result as settled, especially the smallest buckets, where a single outlier trade can swing an average dramatically just because there's so little else in that bucket to average it against.
The mistake tags worth tracking
Eight, each mechanically checkable against a timestamp, a price or a position size on your own statement rather than a feeling: no setup, chased entry, moved stop, oversized, out-of-session, added to a loser, exited early, revenge entry. Drop vague tags like "emotional" or "bad day" — nothing about them can be verified against anything concrete after the fact, which means their meaning drifts every time they're applied and they stop being comparable to themselves over time.
Reviewing without turning it into a second job
The point of a fixed weekly review is to make this genuinely sustainable rather than a project that gets done twice with enthusiasm and then quietly abandoned. Twenty minutes, the same day each week, covering the same five steps in the same order, beats an occasional deep audit that only happens when something already feels wrong — by the time something feels wrong, the pattern usually has weeks of runway behind it already, and a fixed weekly habit catches it closer to when it started.
A 20-minute weekly review that actually gets done
- Export the week's statement, or pull up the journal if trades were logged as they happened.
- Bucket the week's days by trade count and eyeball whether Test 1's shape is showing up.
- Check hold times on any trade that followed a loss within 30 minutes.
- Split the week's R by hour and flag any session that read consistently negative, not just below average.
- Tag anything that fits one of the eight checkable mistake categories, and nothing that doesn't.
Run the three tests on your own file
The free trading journal tags it once and reads R by tag, by hour and by session automatically, so all three tests above run in minutes rather than by hand. Already have closed history? The MT5 report analyzer breaks results down the same way from a real export. Sizing a specific trade rather than reviewing a past week? The risk per trade calculator is the forward-looking half of the same discipline.
Tag it once, read R by hour and by session
Free, in your browser, from your own real trades.
Free trading journalOr try it on a demo file first: load a demo account.
Questions
How many trades a day is too many?
There's no fixed number, and this page deliberately doesn't invent one — a scalping style might run 20 genuinely good trades a day, while five trades could already be too many for a swing approach. The test that actually answers the question is whether your own expectancy per trade falls as your own daily count rises, not any headline figure.
Is scalping the same as overtrading?
No. Scalping is a style built around a high trade frequency by design, with an edge measured and expected to hold at that frequency. Overtrading is trading past the point where each additional trade still adds expected value, which can happen to a scalper too, just at a different absolute count than it would for a swing trader.
How do I know if I'm trading the wrong session?
Split R by session, or by hour on your broker's own server clock, and look for a small number of hours doing essentially all the work while a longer tail slowly gives some of it back. A session isn't automatically wrong just because it's less profitable than your best one; it's worth attention when it's reliably negative rather than merely below average.
What mistake tags should I use?
Ones that are mechanically checkable against a timestamp or a price on your own statement: no setup, chased entry, moved stop, oversized, out-of-session, added to a loser, exited early, revenge entry. Drop tags like "emotional" or "bad day" that can't be verified against anything concrete after the fact — a tag nobody can check is a tag that will drift in meaning every time you apply it.
How often should I review my journal?
Weekly is enough to catch a developing pattern before it compounds into a full month, and infrequent enough that a single bad day doesn't trigger an overreaction to noise. The 20-minute weekly review below is built around that cadence specifically.
Free trading journal ·Trading session ·Holding time ·Expectancy ·R-multiple ·Market hours hub ·Broker server time ·Risk per trade calculator ·MT5 report analyzer
No statistic about trade frequency and profitability is cited anywhere on this page — none is reliably sourced. All three test tables above are invented to show the method, and a result from a small number of days or trades proves nothing on its own. This is educational information about measuring your own trading, not financial advice. Trading carries risk of loss. Full risk disclaimer.