How to Find Your Best and Worst Trading Days in Your Own Data

Your worst trading day is not necessarily Monday, Friday, or the day of your biggest loss. It is the weekday that remains weak after you hold the account, strategy version, timezone, session mix, and evidence window constant. A calendar can reveal the candidate in seconds; the decision still requires reconciled counts and comparable trades.

Trader’s Second Brain has processed 600K+ imported trades cumulatively. That is meaningful product scale, but it is not the denominator for your Monday-versus-Friday result. Your analysis must name its own period, filters, eligible trades, excluded records, trading dates, currency or R basis, and evidence cutoff.

Define “best” and “worst” before ranking days

One leaderboard cannot answer every decision. A weekday can produce the highest total profit only because it has the most trades. Another can have the best average result but only three eligible observations. A third can show a high win rate while its few losses are much larger than its wins.

Decide the reader job first. If the goal is reducing damage, start with net result and average per trade. If the goal is finding schedule concentration, start with trade share and active dates. Never quietly switch metrics because a different one makes the story cleaner.

1. Freeze the analysis scope

A useful scope names six things:

1. Account: one account, or a declared set with compatible money treatment.
2. Period: exact start and end dates plus the evidence cutoff.
3. Strategy version: do not blend materially different rules without labeling the split.
4. Timezone: weekday follows the chosen trading timezone, not whichever device viewed the report.
5. Unit: closed trade, position, or another explicit unit; do not mix them.
6. Money basis: one comparable currency, normalized R, or an explicitly unavailable monetary comparison.

The timezone rule matters near midnight. The same UTC timestamp can belong to Monday for one trading desk and Tuesday for another. TSB resolves a trade date into a weekday for the selected evidence context; if the date is unavailable, that record cannot enter a weekday bucket.

2. Reconcile the denominator before reading a pattern

Suppose the selected account and period contain 420 imported records. Twelve lack a usable close date, eight are still open, and five duplicate rows are quarantined. The weekday analysis has 395 eligible closed trades—not 420 and not TSB’s cumulative 600K+ processed-trade scale.

This is a constructed arithmetic example, not a claim about a customer or the aggregate TSB corpus. Its only job is to demonstrate that 420 − 12 − 8 − 5 = 395. If monetary fields are incomplete, the win/loss denominator and the P&L denominator may be different; show both instead of treating missing money as zero.

3. Build a weekday table that can be audited

For each weekday, report the eligible trade count, distinct trading dates, wins, losses, breakeven trades, net result, and average result per trade. The rows must reconcile to the eligible total. The example below uses fictional R results so the mechanics are visible without inventing population data.

The totals close: 82 + 76 + 85 + 79 + 73 = 395; 192 + 186 + 17 = 395; and the five weekday results sum to +14.9R. Friday is the candidate in this fictional window. The table does not prove that Friday caused the loss, that all Fridays are bad, or that skipping Friday would have added exactly 7.9R to the historical result.

4. Inspect what is hiding inside the weekday

A day label is usually a container for other differences. Before changing a schedule, split the candidate row by:

• session: a weak Friday may be one weak time window rather than the full day;
• setup: the trader may use a different setup mix on that day;
• instrument: one market may dominate the losing row;
• cost coverage: commissions or funding may be missing unevenly;
• event exposure: scheduled releases may change the opportunity set;
• position size: one oversized loss can dominate a small bucket.

The session-performance workflow is the natural second cut. If the day and session slices overlap, do not add their historical losses as if they were separate populations. Open the exact records and measure the intersection.

5. Separate a fast signal from a decision threshold

TSB’s First Read can surface a weekday-drag candidate only after the group contains at least five trades across three distinct dates and the comparison group contains at least five trades. It compares the weekday’s average result with other eligible days and requires a meaningful negative gap before presenting the candidate.

Those are operational guardrails against turning one bad date into a headline. They are not a universal statistical guarantee. Five trades do not validate a permanent schedule change; 30 trades do not automatically validate one either. Required evidence depends on variance, effect size, repeated testing, and the cost of a wrong decision. The sample-size guide explains why there is no magic count.

Use a small group as a review trigger. For a durable rule, ask whether the effect remains visible across distinct dates, later windows, and comparable strategy conditions. If you checked many weekdays, sessions, instruments, and setups before choosing the winner, disclose that exploration instead of presenting the selected row as a predeclared test.

6. Test one bounded change on later trades

Do not delete the weekday and rewrite history. Freeze the original evidence set, inspect the records, choose one reversible rule, and define the recheck before collecting more trades.

1. Observation: “Friday averaged -0.108R across 73 eligible trades on 22 dates in the selected demo.”
2. Candidate explanation: “The negative row may be concentrated in one session.”
3. Rule: “For the next four comparable Fridays, skip new entries in that session; leave setups and risk rules unchanged.”
4. Recheck: compare later eligible trades with the frozen definition; include exclusions and exact membership.
5. Decision: keep, narrow, or reverse the rule based on the new evidence—not on whether the first week felt better.

The before/after filtering guide shows how to preserve the baseline instead of crediting every later change to one filter. This is observational workflow, not a promise that subtracting a historical losing bucket reproduces the remaining equity curve.

How TSB turns the question into reviewable evidence

TSB is our product. Its observed-trading layer can group eligible records by weekday, setup, session, instrument, and side; report count and outcome mix; use a compatible monetary basis when available; and omit records that lack the required capability. First Read can surface a bounded weekday-drag candidate, while the backtester can apply a weekday filter to a frozen trade set.

The system does not infer fatigue, revenge, low liquidity, or any other cause from a weekday row. It does not claim that the cumulative 600K+ imports are the cohort behind a personal result. It also cannot rescue missing or inconsistent source records; the right output is reduced coverage or Not verified, not a fabricated zero.

After the calculation, use the trade-review workflow to add context that deterministic fields cannot provide. For a faster visual review of clusters and outliers, continue with the calendar review.

Weekday analysis checklist

• One account or an explicitly compatible account set.
• Exact period, timezone, strategy version, unit, and cutoff.
• Imported, excluded, and eligible counts reconcile.
• Every weekday row shows trades and distinct trading dates.
• Win/loss/BE totals and monetary or R totals reconcile.
• Session, setup, instrument, cost, event, and size overlap checked.
• One bounded rule with a later comparable recheck.

If the rows do not reconcile, the answer is not “Friday is bad.” The answer is “the current evidence set is not ready for that claim.”