BOS has the best week for hitters; NYY the toughest.
Two things decide a week and neither is on a rankings page: how many games a team plays, and who they play. Between August 6 and August 12, 2026 the league splits 1 teams play 5 / 16 teams play 6 / 13 teams play 7, and opponents range from allowing 3.96 runs a game to 5.36, a spread worth more than most waiver moves.
Most games against the pitching that gives up the most. This is the column to use for streaming bats and for deciding which of two similar players to start all week.
| Team | Games | Opp runs allowed/gm | Opponents |
|---|---|---|---|
| BOS | 7 | 5.07 | ATH x3, TOR x3, CWS |
| BAL | 7 | 4.75 | TEX x3, MIN x3, LAA |
| AZ | 7 | 4.73 | LAD x3, COL x3, SD |
| MIL | 7 | 4.68 | MIN x3, SD x3, PIT |
| CIN | 6 | 5.36 | WSH x3, CWS x2, ATH |
| PHI | 7 | 4.56 | TOR x3, STL x3, WSH |
| LAA | 7 | 4.43 | MIA x3, TEX x3, BAL |
| MIN | 7 | 4.40 | MIL x3, BAL x3, KC |
The opposite question, and it needs the opposite column: most games against the offenses that score the least. A team can have a fine week for its bats and a poor one for its arms, which is why these are two tables and not one strength-of-schedule number.
| Team | Games | Opp runs scored/gm | Opponents |
|---|---|---|---|
| BOS | 7 | 4.12 | ATH x3, TOR x3, CWS |
| LAA | 7 | 4.29 | MIA x3, TEX x3, BAL |
| PHI | 7 | 4.29 | TOR x3, STL x3, WSH |
| ATL | 7 | 4.32 | NYY x3, NYM x3, MIA |
| BAL | 7 | 4.37 | TEX x3, MIN x3, LAA |
| ATH | 7 | 4.38 | BOS x3, TB x3, CIN |
| TOR | 7 | 4.48 | PHI x3, BOS x3, CHC |
| MIL | 7 | 4.55 | MIN x3, SD x3, PIT |
Fewest games, toughest opposition. If you have a marginal player here, this is the week to use the roster spot on someone else.
| Team | Games | Opp runs allowed/gm | Opponents |
|---|---|---|---|
| NYY | 5 | 3.96 | ATL x3, SEA x2 |
| SEA | 6 | 4.01 | TB x3, NYY x2, DET |
| CLE | 6 | 4.12 | CWS x3, DET x2, NYM |
| CWS | 6 | 4.25 | CLE x3, CIN x2, BOS |
| PIT | 6 | 4.32 | NYM x3, MIA x2, MIL |
Boston is the one team on this list where the schedule argues for both halves of your roster at once. Seven games, opponents who allow 5.07 runs a game, opponents who score 4.12. That combination does not usually exist. Normally a soft-pitching slate means you are facing bad pitching staffs attached to good offenses, and the two effects cancel. Here they compound. If you have a Red Sox bat on your bench for matchup reasons, next week is the week you stop benching it, and if you have a back-end Boston arm you were going to skip, start him.
The genuinely arguable case is Cincinnati against Boston, and it is arguable because the two inputs point opposite ways. Cincinnati's opponents allow 5.36 runs a game, the softest pitching any team on this board sees. But it is six games, not seven. Multiply it out and Boston's week is worth roughly 35 opponent runs allowed against Cincinnati's 32, so the extra game more than eats the quality edge. The counterargument is real: opponent runs allowed is a season-long team rate, and it says nothing about which four or five starters you actually draw. A six-game week that happens to miss two aces is better than a seven-game week that catches them. If you can see the probable matchups and Cincinnati's slate is stacked with fifth starters and bullpen games, flip the order. Absent that information, take the game.
The Yankees are the sit, and it is not close. Five games is the smallest count here, and the opponents allow 3.96 runs a game, the stingiest number on the board. You are getting two fewer games than a Boston hitter against pitching that is meaningfully better. That is the worst hitting week available, and there is no compensating pitching angle either, since Yankees arms face offenses scoring 4.53, on the wrong side of average for this group. So the fringe Yankee bat, the platoon guy, the second catcher, comes out of the lineup. The cost of being wrong is small: five games of a marginal player is not where seasons are won, and the number would have to be badly misleading for a five-game week to beat a seven-game week anywhere.
For pitching, the interesting name is the White Sox. Six games against offenses scoring 4.08 runs a game, the lowest mark here, and their hitters draw pitching allowing 4.25, which is poor. That is a clean split: start the Chicago arm, bench the Chicago bat. Los Angeles offers something similar on the pitching side, six games against offenses scoring 4.17, with the bonus that their hitters face staffs allowing 5.07. Seattle and Cleveland look pitcher-friendly on the surface because their opponents' scoring rates sit at 4.52 and 4.38, but those are ordinary numbers, and six games of ordinary is not a reason to move anyone.
What would show this read is wrong is straightforward. Rainouts and doubleheaders are the whole ballgame, because game count is doing more work in these calls than opponent quality is. If Boston loses one to weather, the Cincinnati comparison inverts immediately. And if the teams you are targeting line up their best starters against the soft-pitching opponents, the opponent rate you are leaning on stops describing your week.
Two actions, then. Start everything Boston for seven games. Sit the marginal Yankee and do not talk yourself back into him on five.
Game count leads and opponent quality breaks the tie, in that order. The difference between five games and seven is nearly a third of a week's production from the same player, which is a bigger effect than any realistic difference in who is pitching.
Hitters and pitchers get separate tables because they are asking opposite questions. Your bats want opponents who allow runs; your arms want opponents who do not score them, and one number cannot say both.
Opponent quality is full-season runs per game, not a recent hot streak. Ten games of a pitching staff is noise, and the question here is which schedule to prefer rather than which team is playing well this week.
Curated picks where the model has the highest decision conviction. Updated every render.
Run rankings to populate Market Edge.
Run rankings first.
Mark a player as drafted to get a recommendation.
Studies and awards - the research-side surfaces of the managr platform.
Live snapshot of the projection system.
Backtest, parsimony, ablation, and benchmark - one synthesized report. Output renders in Validation.
Final Value = Raw Projection × MasterConfidence × TeamContext. Each layer answers one question - no overlap.
Recency weighting: prior seasons contribute by recency (more recent = more weight) and sample size (more PA = more weight).
Shrinkage: observed rates regress toward position-specific population means by an amount inversely proportional to sample size. Catches small-sample outliers.
Quality-of-contact adjustments: xwOBA, barrel rate, and bat-tracking metrics replace luck-driven outcome stats with skill-driven ones.
PT modeling: projected PA is anchored to workload tier (full-time, regular, platoon, backup catcher) using historical role distributions.
Monte Carlo: N simulated seasons per player using projected mean + uncertainty, producing P10 / P50 / P90 distribution and bust%.
Confidence layers: four orthogonal multipliers: Roster (depth chart), Role (PT certainty), Sample (career PA), Market (consensus alignment). The Audit tab shows all four for every player.
VAR: Value Above Replacement at the player's primary position. Replacement levels are floored per position so SS scarcity doesn't artificially inflate stable middle infielders.
Tune component weights against historical seasons. Stored in session.
-
-
-
Walk-forward backtests, calibration quality, and benchmark comparisons. Run walk-forward first - most tools depend on its pair pool.
Projects every historical batter-season from prior data only. Reports RMSE, MAE, Spearman ρ, hit rates. Populates the pair pool other validators use.
Walk-forward over historical seasons. Reports RMSE, MAE, Spearman ρ, top-N hit rates.
Distribution, uncertainty, per-archetype performance, calibrated tiers, draft sim.
Load any rival projection or ADP source. Auto-detects player_name + rank / adp / projected.
Where the model finds value the market is missing.
Curated picks from current rankings.
Where the model has measurable advantage.
The safety layer. Realism, false-confidence, forensics - what to remove.
The most important governance tools. Output renders in Validation.
Per-era ablation, error clusters, bias, correlations, removals. Each tells you what to remove. Run walk-forward first.
The smallest model that retains predictive power. Every feature beats the burden of proof.
Live pipeline status and data freshness.
-
Last known status of each underlying data source.
Source status will appear once data has been refreshed.
Issues from the most recent data refresh, if any.
-
MVP, Cy Young, Rookie of the Year - historical winners with their stats, plus model-predicted current-season winners.
Predictions from the current 2026 projection model. Top candidates per award based on projected fantasy points + advanced-stat underlying. League assignment from current team.
Coaching rosters for every MLB team plus a multi-year Fantasy Points Above Average ranking of every MLB coach.
Findings article + all-time top-100 performer leaderboard from every World Baseball Classic (2006-2026).
A growing collection of fantasy baseball studies. Each card opens a detail page with the methodology, the data sources, and (where the data exists today) live computed findings.
Active player injuries, refreshed from upstream sources.
| Player | Team | Pos | Status | Explanation | Replacement |
|---|
Enter players for each side, one per line. Values use your scoring weights and injury-adjusted projections.
| Player | Pos | ProjPts | Status |
|---|
| Player | Pos | ProjPts | Status |
|---|
Every signal, formula, and data source the model uses for player evaluation - organized by product.
Configure your draft session. This stays on this device only.