Learn how to test trading performance by weekday, distinguish persistent effects from noise, and decide whether a day-of-week filter belongs in your strategy.
Quick Answer
A day-of-week trading analysis compares a strategy’s results across weekdays using trade count, expectancy, average win and loss, drawdown, and trading costs. Do not remove a weekday merely because its historical net result is negative. First check sample size, market regime, execution quality, outliers, and out-of-sample stability. A weekday filter is credible only when the effect is economically meaningful, has a plausible explanation, and survives testing on data that was not used to discover it.
Key Takeaways
- Assign every trade to a weekday consistently, usually by entry timestamp and exchange timezone.
- Compare expectancy and risk, not just total P&L or win rate.
- Treat weak results from a small group of trades as a hypothesis rather than a trading rule.
- Separate strategy behavior from discretionary rule violations and execution mistakes.
- Validate any weekday filter out of sample with realistic fees, spread, and slippage.
- Prefer simple, stable filters over rules tailored to one unusually strong or weak period.
What Day-of-Week Trading Analysis Measures
Day-of-week analysis asks whether the same strategy behaves differently on Monday, Tuesday, Wednesday, Thursday, or Friday.
The goal is not to discover a universally superior trading day. No weekday is inherently better across every market, timeframe, and strategy. The useful question is narrower:
Does this specific strategy, traded under these rules, show a persistent and usable difference by weekday?
For each day, calculate at least:
- Number of trades
- Net P&L after trading costs
- Average result per trade
- Expectancy in currency or R-multiples
- Win rate
- Average winner and average loser
- Profit factor
- Maximum drawdown
- Largest loss
- Exposure or time in market
Expectancy is especially useful because it combines win frequency with payoff size:
Expectancy = (Win rate × Average win) − (Loss rate × Average loss)
Suppose Mondays have a 60% win rate but small winners and large losses. Fridays may win only 45% of the time while producing larger winners. Win rate alone could lead to the wrong conclusion.
Total P&L is also insufficient. A day with twice as many trades naturally has more opportunity to generate gains or losses. Average result per trade and expectancy make weekday groups more comparable.
Step-by-Step Day-of-Week Trading Analysis Workflow
1. Define how trades are assigned to weekdays
Choose the timestamp, session, and timezone before analyzing results.
For an intraday strategy, assigning a trade by its entry day is usually straightforward. For overnight strategies, decide whether the relevant day is the signal day, entry day, or exit day. Entry day is often the cleanest choice because that is when the strategy commits risk.
Use the exchange timezone rather than your device’s local timezone. Crypto strategies require an explicit session boundary because the market operates continuously.
Do not change this convention after seeing the results.
2. Freeze the baseline strategy
Write down the complete strategy before testing weekday filters:
- Market and timeframe
- Entry and exit conditions
- Position-sizing method
- Stop and target logic
- Maximum holding period
- Session restrictions
- Fees, spread, and slippage assumptions
If the underlying rules keep changing, you cannot tell whether a performance difference came from the weekday or from a different strategy version.
3. Build a weekday breakdown
Group baseline trades by entry weekday and calculate the same metrics for every group. Always display the number of trades beside each metric.
Review normalized and aggregate results. Useful normalized measures include expectancy per trade, return on initial risk, and average adverse excursion. Aggregate measures include net P&L, drawdown, and total costs.
If position size changed during the sample, consider using R-multiples or percentage returns. Raw currency results can make later periods appear more important solely because more capital was deployed.
4. Check whether execution explains the difference
A weak weekday may reflect trader behavior rather than strategy logic.
Compare planned trades with actual trades. Look for weekday differences in:
- Entry timing
- Position size
- Stop placement
- Trades taken outside the setup
- Missed valid signals
- Early exits
- Number of trades taken after a loss
If valid Monday signals behave normally in a mechanical backtest but live Monday trades perform poorly, removing Monday may hide an execution problem. A tighter process rule or temporary size reduction could be a more relevant intervention.
5. Evaluate uncertainty and sample coverage
A weekday receives only a fraction of a strategy’s trading opportunities. Splitting an already limited sample into separate groups can create unstable results.
Do not rely on a universal minimum trade count. Instead ask:
- Are there enough trades to estimate expectancy with useful precision?
- Does the group cover calm, volatile, rising, falling, and range-bound conditions relevant to the strategy?
- Is the result dominated by one month or one outlier?
- Are trades clustered around a small number of events?
- Does the result persist when the test period changes slightly?
Confidence intervals, bootstrapping, or trade-sequence resampling can help reveal uncertainty. Even without advanced statistical methods, comparing multiple subperiods is better than trusting one full-period average.
6. Test a limited set of sensible alternatives
Start with the unfiltered baseline. Then test simple variants such as:
- Exclude one weak weekday
- Reduce risk on that weekday
- Require stronger entry confirmation
- Restrict trading to a narrower session
- Keep the day but cap the number of entries
Every additional variation increases the chance of finding an attractive historical result by luck. Limit the number of hypotheses and document them before testing.
7. Validate the proposed rule out of sample
Use one period to identify the weekday hypothesis and a later, untouched period to test it.
For example, if Wednesday appears weak in the development sample, freeze the “no Wednesday entries” rule before evaluating the validation period. Compare the filtered strategy with the original baseline using identical assumptions.
A useful filter should improve the chosen objective without creating unacceptable trade-offs. It might reduce drawdown but remove too many favorable trades. Whether that is desirable depends on the strategy’s goals and constraints.
Walk-forward analysis provides a stronger test when enough data exists. It repeatedly develops the rule on earlier data and evaluates it on the next unseen segment.
Configuring a backtest in Kvants Studio.
Worked Example: Testing a Weak Friday
Consider a hypothetical intraday strategy with 500 historical trades. Its Friday group contains 92 trades and shows an expectancy of −0.08R, while the other weekdays are positive.
Removing Friday improves full-sample expectancy from 0.12R to 0.17R and lowers maximum drawdown. That looks promising, but it does not yet justify a permanent filter.
Further analysis finds that two unusually large Friday losses account for much of the difference. Excluding those trades for diagnostic purposes—not to rewrite the record—moves Friday expectancy close to zero. The weakness is also concentrated in the first third of the sample; later Fridays are modestly positive.
The trader tests three predefined variants on an untouched period:
- Keep the baseline unchanged.
- Remove all Friday entries.
- Keep Friday but reduce risk to half size.
In the validation period, the Friday exclusion reduces drawdown slightly but also removes several winning trades. Half size produces a similar reduction in volatility without eliminating the opportunity entirely.
The conclusion is not that half size will produce better future results. It is that the available evidence supports a cautious risk adjustment more strongly than a complete Friday ban. Continued paper trading and monitoring would still be appropriate.
A backtest's equity curve and trade-by-trade log.
Common Failure Modes
Treating the worst historical day as predictive
One weekday must rank last even when all differences are random. A ranking creates a hypothesis; it does not validate one.
Optimizing five separate strategies
Changing entries, stops, targets, and risk for every weekday creates many degrees of freedom. The result may fit historical noise while becoming difficult to execute and audit.
Ignoring trading costs
A weekday may generate more trades, lower liquidity, or worse fills. Test net results with cost assumptions that reflect the instrument, session, and order type.
Mixing strategy and discipline problems
Overtrading after an early loss or entering before confirmation on Friday is not necessarily a weekday effect. Separate valid signals from rule violations before modifying the strategy.
Using inconsistent session boundaries
Timezone errors can place late-night trades on the wrong day. This is particularly important for crypto and instruments with extended or overnight sessions.
Removing a day without checking opportunity cost
Eliminating a weak weekday can reduce losses, but it can also remove diversification and occasional large winners. Compare the complete return distribution rather than only the average.
Turning a Weekday Hypothesis Into a Testable Rule
An observation such as “Fridays feel difficult” is not testable until it becomes explicit logic.
A basic rule might be:
Allow entry when weekday is not Friday.
A more cautious alternative could be:
When weekday is Friday, use 50% of normal risk.
The rule must also specify the timezone, session boundary, treatment of positions opened earlier, and whether exits remain active on the restricted day.
Kvants Studio can turn a plain-English trading idea into editable, auditable strategy logic. You can express a weekday condition, inspect the resulting rules, and compare the filtered version with the original strategy. Backtests run on NautilusTrader’s event-driven engine, allowing the test to account for order sequencing and position state.
Parameter sweeps can compare a small set of predefined weekday or risk variants. Walk-forward and crisis-stress validation can then examine whether the result survives beyond the discovery period. The rule can also be exported as Pine Script v6 or moved into a controlled paper workflow. The Kvants documentation provides guidance on strategy definition and export.
Kvants is a research tool rather than a substitute for judgment. A cleaner historical result after excluding Friday does not prove that Friday will remain weak.
A strategy laid out end to end in the Kvants editor.
Frequently Asked Questions
What is the best day of the week to trade?
There is no universal best day. Results depend on the market, strategy, timeframe, session, costs, and sample period. Test weekdays within your own fully specified strategy rather than applying a market-wide rule.
Should I stop trading my worst weekday?
Not immediately. Check sample size, outliers, market regimes, execution quality, and out-of-sample performance first. Reducing risk or adding a process control may be more appropriate than eliminating the day.
Should trades be grouped by entry day or exit day?
Entry day is usually the most defensible choice because it identifies when risk was initiated. Overnight strategies may also analyze signal and exit days, but the primary convention should be chosen before reviewing results.
Is win rate enough for weekday analysis?
No. Include expectancy, average win and loss, costs, drawdown, and trade count. A high-win-rate weekday can still have negative expectancy if its occasional losses are disproportionately large.
How often should weekday performance be reviewed?
Use a schedule that matches the strategy’s frequency. High-frequency strategies accumulate evidence faster than strategies producing only a few monthly trades. Avoid changing rules after every short-term fluctuation.
Risk Note
This article is educational and is not investment advice. Trading involves risk, and weekday patterns can change or disappear as market conditions evolve. Backtested performance does not guarantee future results. Use realistic costs, validate rules on unseen data, and consider paper testing before risking capital.
