TEX has the best week for hitters; SD 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 10 and August 16, 2026 the league splits 24 teams play 6 / 6 teams play 7, and opponents range from allowing 3.77 runs a game to 5.30, 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 |
|---|---|---|---|
| TEX | 7 | 5.23 | LAA x4, ATH x3 |
| LAA | 7 | 4.70 | TEX x4, KC x3 |
| BOS | 7 | 4.61 | TOR x4, PIT x3 |
| SF | 6 | 5.30 | HOU x3, COL x3 |
| TB | 6 | 5.23 | ATH x3, BAL x3 |
| LAD | 7 | 4.32 | MIL x4, KC x3 |
| AZ | 6 | 4.81 | COL x3, ATL x3 |
| MIA | 6 | 4.80 | PIT x3, CIN 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 |
|---|---|---|---|
| LAA | 7 | 4.14 | TEX x4, KC x3 |
| TEX | 7 | 4.20 | LAA x4, ATH x3 |
| BOS | 7 | 4.40 | TOR x4, PIT x3 |
| TOR | 7 | 4.48 | BOS x4, NYY x3 |
| LAD | 7 | 4.60 | MIL x4, KC x3 |
| MIL | 7 | 4.68 | LAD x4, SD x3 |
| NYY | 6 | 3.91 | SEA x3, TOR x3 |
| DET | 6 | 3.97 | CLE x3, CWS x3 |
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 |
|---|---|---|---|
| SD | 6 | 3.98 | MIL x3, CLE x3 |
| PIT | 6 | 4.01 | MIA x3, BOS x3 |
| CLE | 6 | 4.07 | DET x3, SD x3 |
| DET | 6 | 4.20 | CLE x3, CWS x3 |
| ATH | 6 | 4.23 | TB x3, TEX x3 |
Texas is the only team on this board where both sides of the ledger point the same way. Seven games against pitching staffs that have allowed 5.23 runs a game is the best hitting slate here by a comfortable margin, and the same seven games come against lineups scoring 4.20, which is the second-friendliest number for pitchers on the list. That combination is rare because it usually cannot happen: a week stacked with bad pitching staffs normally means a week stacked with good offenses. Start every Ranger you own. The streaming case extends further down the roster than it normally would, and the fifth outfielder you would ordinarily bench is playing seven times.
The genuinely arguable one is Milwaukee. Seven games is a full extra turn of the lineup over the six-game clubs, but 4.04 runs allowed by the opposition is the second-stingiest slate on the board, and those same opponents are scoring 4.68, which is on the wrong side of average for your pitchers. So the extra game is real and the quality is not. My read: the game count wins for hitters and loses for pitchers. An extra start's worth of plate appearances is roughly a sixteen percent bump in counting-stat exposure, and that beats the gap between a 4.04 slate and a 4.60 one for anyone you were starting anyway. The mechanism matters, though. Volume helps you in runs, RBI, home runs and steals. It does nothing for you in batting average against arms that are suppressing everybody. If your team is chasing average and not counting stats, the seven games are close to worthless and you should treat Milwaukee as a neutral week.
The strongest case against me is San Francisco, and it is a good one. Six games against staffs allowing 5.30 runs a game is the softest pitching any hitter here will see, better on a rate basis than what Texas draws. If you are choosing between a Giant and a Brewer of similar quality for one lineup spot, take the Giant, because you are trading one game for a full run and a quarter of opponent softness per game. What I would not do is extend that to a two-start pitcher decision. San Francisco's opponents are scoring 4.72, the second-worst mark on the board for pitchers, so the same schedule that lights up your bats will light up theirs.
Detroit is the pitching answer and nobody will argue with it: opponents scoring 3.97 across six games is the quietest offense any staff on this list faces. But six games usually means one two-start arm at most, so the practical benefit is narrower than the number suggests. Cleveland at 4.40 and Pittsburgh at 4.44 are ordinary weeks dressed up as something. Ignore them.
The clearest sit is on the other end. San Diego hitters face staffs allowing 3.98 runs a game across only six games, the worst rate and the low game count together, and there is no volume to rescue it. Bench the marginal Padre bat. That is the one call on this table I would make without a second thought.
What would prove me wrong on Milwaukee is straightforward: if a rainout turns the seven into a six inside the first three days, the entire argument for starting a below-replacement Brewer bat collapses, and you are left holding a hard slate with no compensation. Check the game count is still seven before Thursday. Cost of being wrong is one week of a bench bat's production, which is survivable. Cost of being wrong on Texas is not, because there is no better week available to trade into.
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.