BOS has the best week for hitters; CLE 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 7 and August 13, 2026 the league splits 22 teams play 6 / 8 teams play 7, and opponents range from allowing 3.88 runs a game to 5.24, 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 | 4.96 | TOR x4, ATH x3 |
| TEX | 7 | 4.79 | LAA x4, BAL x3 |
| LAD | 7 | 4.70 | AZ x3, KC x3, MIL |
| MIL | 7 | 4.53 | MIN x3, SD x3, LAD |
| PHI | 7 | 4.50 | TOR x3, STL x3, MIN |
| CIN | 6 | 5.24 | WSH x3, CWS x3 |
| CHC | 6 | 5.13 | KC x3, WSH x3 |
| LAA | 7 | 4.39 | TEX x4, MIA x3 |
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.08 | TOR x4, ATH x3 |
| PHI | 7 | 4.19 | TOR x3, STL x3, MIN |
| LAA | 7 | 4.22 | TEX x4, MIA x3 |
| TEX | 7 | 4.29 | LAA x4, BAL x3 |
| LAD | 7 | 4.34 | AZ x3, KC x3, MIL |
| TOR | 7 | 4.42 | BOS x4, PHI x3 |
| MIL | 7 | 4.53 | MIN x3, SD x3, LAD |
| MIN | 7 | 4.68 | MIL x3, BAL x3, PHI |
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 |
|---|---|---|---|
| CLE | 6 | 3.88 | CWS x3, DET x3 |
| ATH | 6 | 3.93 | BOS x3, TB x3 |
| SEA | 6 | 3.97 | TB x3, NYY x3 |
| NYY | 6 | 3.98 | ATL x3, SEA x3 |
| KC | 6 | 4.06 | CHC x3, LAD x3 |
Boston is the whole table. Seven games against pitching staffs allowing 4.96 runs per game is the only place next week where volume and opponent quality point the same direction, and the gap is wider than it looks. Seven times 4.96 gets you to roughly 34.7 runs of expected environment across the week. Cincinnati, whose 5.24 is the single softest per-game slate on the board, only gets six cracks at it: about 31.4. The team with the better opponent loses by three runs of scoring context because of one extra game. That is the point worth internalizing before you touch a lineup. Game count is not a tiebreaker here, it is the primary term.
The mechanism behind that is boring and it is why people misplay it. Opponent run environment moves in a band of maybe a run and a quarter from best to worst, from 5.24 down to 3.88. Game count moves by a sixth, seventeen percent, in one step. A sixth of your counting stats is worth more than a fifteen percent shift in the quality of the arms you face, and counting stats are what home runs, RBI, runs and steals actually are. So the Cubs bat at 5.13 all week and still finish behind Texas at 4.79, because Texas plays seven.
The case against leaning this hard on Boston: 4.96 is a season-long opponent rate, not a probable-pitcher list. A seven-game week that happens to line up two aces and a swingman is not the week the average implies, and nothing in this data tells you which arms are actually scheduled. If you have a Red Sox platoon bat who could sit twice, the seven games are five and the edge evaporates. That is the real risk, not the opponent. The falsifier is simple and it arrives fast: check the announced starters. If the week opens against two arms you would bench a hitter against on any other slate, the 4.96 was a mirage and you go back to the Reds or Cubs bat with the softer per-game draw.
On the pitching side the same team is the answer, which does not happen often. Boston's opponents score 4.08 per game, second-lowest on the board behind nobody who plays seven, and the Red Sox play seven. That is the combination you want: two starts from a mid-rotation arm against offenses producing four runs a game. Philadelphia is the close second, seven games at 4.19, and I would treat those two as interchangeable. Anaheim gives you seven at 4.22 and is the sneaky one, because nobody is excited about that staff and the schedule does not care.
Where this actually changes a call is Cleveland and Oakland. Six games each, and their hitters face staffs allowing 3.88 and 3.93, the two hardest slates listed. Run it out and a Cleveland bat is looking at roughly 23 runs of context for the week against Boston's 35. That is a fifty percent difference in scoring environment. Sit the marginal Guardians outfielder. The cost of being wrong is one hot six-game stretch you missed, which is survivable; the cost of being right is that you avoided the worst combination of slate and volume on the board.
Minnesota is the one I would not fight about either way. Seven games is real, but 4.28 is a bottom-third draw, and the week lands around 30 runs of context, right on top of six-game Chicago. Hold, do not chase.
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.