Detroit's offense has collapsed, but its run margin says the record is a mirage

The Tigers are 12-plus wins behind their run differential — one of the largest gaps on record — and now their offense has gone cold too, scoring just 2.8 runs a game over the last 10. Two stories, one struggling team.

Published: · Figures as of August 29, 2026

Asked: What’s happened to the Tigers?

Detroit's record trails its scoring margin, and its offense just fell off a cliff

Two separate things are happening to the Tigers (62-72, 24th of 30 in MLB, 4th in the AL Central, 9 games back of division-leading Chicago). Across the full season their run differential says they should be much closer to .500 than their record shows — and independent of that, their offense has gone cold over the last two weeks, which is why the record has kept sliding rather than closing that gap.

The season-long story: a record that undersells the run differential

Detroit has outscored opponents 593-524 this season (+0.51 runs/game), which implies a .556 win rate on a pythagorean basis (exponent 1.83, the baseball-specific refinement of Bill James's original formula). Their actual win rate is .463. That gap works out to about 12.6 wins of underperformance relative to what their scoring margins support — one of the largest gaps DataBaller's team-sustainability read has on file for them, sitting more than two standard deviations outside the normal spread (confidence 1.0, on a full 134-game sample). That model's own backtested finding is that teams this far behind their margins tend to close the gap from the record's side the rest of the way — not a guarantee, and not a claim about any single game, but the direction the model reads is "expect recovery," not further fall-back.

The last two weeks: an offense that's stopped scoring

Window Record Scored/G Allowed/G Margin/G
Season (134 G) 62-72 4.43 3.91 +0.51
Last 20 7-13 3.9 3.9 0.0
Last 10 (Aug 17-28) 2-8 2.8 4.2 -1.4
Last 5 1-4 2.6 4.2 -1.6
Detroit Tigers: Scoring by Window — runs per game
WindowScored/G (runs per game)Allowed/G (runs per game)
Season4.433.91
Last 203.93.9
Last 102.84.2
Last 52.64.2

The offense isn't just cooling against a tougher slate. Over the last 10 games, Detroit scored 2.8 runs a game — down from 4.73 over the 11 games immediately before that, and 1.52 runs below what the league produced over that same stretch (z = -1.64). Schedule-adjusted against what these specific opponents (Kansas City, Pittsburgh, Tampa Bay, the Dodgers) had allowed coming in, the Tigers still scored 1.8 runs a game below expectation — so this isn't a case of running into a run of dominant pitching staffs, it's a real drop in Detroit's own output. Run prevention, by contrast, has stayed essentially at league level (4.2 allowed vs. a 4.3 league expectation, and almost exactly at what these opponents normally score) — the pitching side of this isn't the story.

What's behind the offensive dip

Two things, both real, neither the whole explanation on its own:

Context on team strength

DataBaller's power rating has Detroit at +0.3 runs per game versus an average opponent on a neutral site (full confidence, in-season regime on 134 games) — a team that grades out modestly above average overall, with its underlying run-creation signal outpacing its run-prevention signal in the model's own components. That's consistent with the sustainability read: the components like this team more than the standings do.

Confidence: High on the season-long margin gap (full-season sample, extreme and stable across the last several days of readings). Medium on the recent-scoring story — it's a real, schedule-adjusted signal, but it rests on 10 games and several of the missing bats are already probable to return within days, which the data can't project forward.

This analysis was generated by DataBaller from licensed sports data and reflects the data available on the date above. It is not official league data. Provided as-is; data may contain errors.